Firebase Outage History

Firebase Test Lab experienced delayed tests on ARM devices for 23.3 hours. The issue was classified as minor and affected the Test Lab component. The incident has been resolved after investigation into the cause of the delays.

Firebase AI Logic experienced elevated RESOURCE_EXHAUSTED error rates from both Vertex AI and Generative AI servers for 6.1 hours. The incident was classified as minor impact. No resolution details or updates were provided for this service disruption.

Firebase Test Lab experienced a major service disruption where physical device tests became delayed and stuck in pending status for 4 hours. The issue affected all users attempting to run tests on physical devices through Test Lab. Google investigated and resolved the underlying cause, restoring normal test execution functionality.

Firebase Test Lab experienced elevated inconclusive test results for 6.1 hours. The issue affected the Test Lab service, causing tests to fail to complete with definitive results. The incident was classified as minor and has been resolved.

Firebase Test Lab ARM devices experienced elevated failure rates and delays in test result delivery for 1.9 hours. The incident affected Test Lab services, causing tests to fail at higher than normal rates and results to be delayed. The issue was resolved after approximately 1.9 hours of service disruption.

Firebase Hosting experienced missing metrics and logs in Cloud Logging for 14 hours. The issue was classified as minor and affected the Hosting component's observability capabilities. The incident has been resolved, restoring normal logging and metrics collection functionality.

Firebase Hosting experienced missing metrics and logs in Cloud Logging for 6 minutes. The Hosting component was affected during this minor incident. The issue has been resolved.

Firebase experienced major service issues affecting Crashlytics, Performance Monitoring, and Release Monitoring dashboards with high error rates beginning on March 29, 2026 at 22:43 US/Pacific. Users reported that Crashlytics and Release Monitoring became completely unresponsive during the incident. The service disruption lasted 1.6 hours before being resolved by the engineering team.

Firebase Cloud Messaging experienced 404 errors for clients sending messages to URLs with trailing slashes due to a recent change. The issue affected the Cloud Messaging component for 1.6 hours. Google resolved the problem by rolling back the change, with clients able to immediately fix the issue by removing trailing slashes from their send URLs.

Firebase Cloud Messaging experienced minor intermittent latency increases that affected some users for approximately 19 days. The issue impacted the Cloud Messaging component, causing slower than normal message delivery for affected users. The incident was acknowledged with a commitment to provide resolution timeline updates.