Firebase Status Dashboard
NOTE
For incidents related to Cloud Functions, Cloud Firestore and Cloud Storage, please see Cloud Service Health. For incidents related to Google Analytics, please see Ads Status Dashboard.
Incident affecting Hosting
Firebase Hosting returning "maximum threads" 503 error page
Incident began at 2025-06-08 19:08 and ended at 2025-06-09 01:32 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 9 Jun 2025 | 01:39 PDT | We've now put a couple mitigations in place to address the issue. In our testing we are now unable to replicate the issue. If you continue to see it, please reach out to Firebase Support. |
| 9 Jun 2025 | 00:06 PDT | We've attempted a mitigation around the Manila datacenter, redirecting requests elsewhere. That has had some effect, but there are other affected datacenters. We're looking to do a more complete mitigation for the root cause. |
| 8 Jun 2025 | 22:21 PDT | We're continuing to see issues in the Philippines and Singapore and are still investigating. |
| 8 Jun 2025 | 21:22 PDT | We're continuing to investigate and are focusing our investigation on locations where users have been reporting details issues. |
| 8 Jun 2025 | 20:51 PDT | Firebase Hosting is investigating reports of a 503 error page reporting "maximum threads for service reached" in the Asia and APAC regions. We're currently investigating. |
- All times are US/Pacific