Mountkirk Games' gaming servers are not automatically scaling properly. Last month, they rolled out a new feature, which suddenly became very popular. A record number of users are trying to use the service, but many of them are getting 503 errors and very slow response times. What should they investigate first?

When a service experiences sudden, high demand leading to 503 errors and slow responses, and scaling issues are observed, the most immediate and impactful cause to investigate is often resource quotas. Cloud providers like Google Cloud Platform enforce quotas to prevent uncontrolled resource consumption. If a project hits its quota limit for compute instances, network throughput, or other critical resources, new instances cannot be provisioned, leading to scaling failures and service degradation. While database issues, code bugs, and load testing can all cause similar symptoms, quota limits are a fundamental platform constraint that can halt scaling entirely and are a common first check in such scenarios.