outages.live
Live
FirebaseIncident ·

Firebase Hosting is experiencing slightly elevated 502 errors on requests for dynamic content

DegradedOfficial update
0

Firebase Hosting has slightly elevated 502 errors. The errors affect requests for dynamic content, which include rewrites to Cloud Run and Functions, and POST requests to Firebase Auth. Firebase reports that the issue is still under investigation.

State

SERVICE DISRUPTION

Started

Ongoing for

22 h 46 min

Worst impact

Degraded

Timeline

1 update
19:0000:4106:2212:0417:45
DegradedUpdate postedTimes in UTC

SERVICE DISRUPTION

22 h 46 min 100%

Updates

Times in UTC

As posted by Firebase

SERVICE DISRUPTION

Requests for dynamic content from Firebase Hosting (rewrites to Cloud Run & Functions, POST requests to Firebase Auth) are experiencing slightly elevated rates of 502 errors.

Affected components

1
Hosting

Firebase in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

42 min

This incident

32× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 h 46 min
median 42 min
90 days agoToday

Other Firebase incidents

All incidents

Firebase·Test Lab experiencing delays

Firebase Test Lab experienced delays. Firebase reported that the team is investigating. This incident is resolved and lasted 42 minutes.

Resolved

Follow Firebase

Your coding agent knows when Firebase is down, and tells you when a failure is theirs, not yours. You can also get Firebase incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "firebase" and tell me if Firebase has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=firebase
Slack
/feed subscribe https://outages.live/feed.xml?providers=firebase

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane