Test Lab experiencing delays
ResolvedOfficial update
0
Firebase Test Lab experienced delays. Firebase reported that the team is investigating. This incident is resolved and lasted 42 minutes.
State
Resolved
Started
Lasted
42 min
Worst impact
Degraded
Timeline
2 updates18:0018:1018:2118:3118:42
DegradedUpdate postedTimes in UTC
SERVICE DISRUPTION
42 min 100%
Updates
Times in UTCAs posted by Firebase
Resolved
SERVICE DISRUPTION
Team is investigating
Affected components
1Test Lab
Firebase in the last 90 days
Full history90 days agoToday
Incidents in 90 days
1
Days with an incident
1
Median duration
42 min
This incident
About the median
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=firebaseSlack
/feed subscribe https://outages.live/feed.xml?providers=firebaseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane