Firebase Outage History

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.

Firebase Crashlytics experienced delays in exporting crash data to BigQuery, with data from March 9th onwards failing to export properly. The issue affected the Crashlytics component and persisted for approximately 21 hours. The service team investigated methods to expedite the export process to resolve the backlog.

Firebase Studio App Hosting experienced a deployment disruption that prevented users from publishing apps through the Studio interface. The incident affected App Hosting deployments specifically from Firebase Studio, while other deployment methods remained functional. Users were able to work around the issue by using the Firebase App Hosting console or Firebase CLI as alternative deployment methods.

Firebase experienced high error rates affecting the Firebase console for 1.1 hours. The incident was classified as major and required ongoing investigation. The issue has been resolved.

Firebase experienced connection errors with GitHub in the us-east5 region, causing failures in both automatic and manual deploys from GitHub repositories and preventing GitHub commit status updates. The incident lasted 1.9 hours and users could work around the issue by deploying from local source using Firebase command line tools instead of GitHub integration.

Firebase experienced connection errors with GitHub in the us-east5 region, causing automatic and manual deploys from GitHub to fail and preventing commit status updates with GitHub checks. The incident lasted 5 minutes and users could work around the issue by deploying from local source using Firebase command line tools instead.