Firebase incident

Firebase Hosting returning "maximum threads" 503 error page

Critical Resolved

Firebase experienced a critical incident on June 9, 2025 affecting Hosting and Hosting (global), lasting 6h 24m. The incident has been resolved; the full update timeline is below.

Started
Jun 09, 2025, 02:08 AM UTC
Resolved
Jun 09, 2025, 08:32 AM UTC
Duration
6h 24m
Detected by Pingoru
Jun 09, 2025, 02:08 AM UTC

Affected components

HostingHosting (global)

Update timeline

  1. investigating Jun 09, 2025, 03:51 AM UTC

    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.

  2. investigating Jun 09, 2025, 04:22 AM UTC

    We're continuing to investigate and are focusing our investigation on locations where users have been reporting details issues.

  3. investigating Jun 09, 2025, 05:21 AM UTC

    We're continuing to see issues in the Philippines and Singapore and are still investigating.

  4. investigating Jun 09, 2025, 07:06 AM UTC

    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.

  5. resolved Jun 09, 2025, 08:39 AM UTC

    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.