Istoricul incidentelor Firebase

1. 11 august 2026 la 13:17 UTCinvestigating

   We are in the progress of fixing.

2. 11 august 2026 la 23:55 UTCinvestigating

   Mitigations have been applied, and tests should start running again. However, wait times may still be longer than normal during this recovery period.

3. 12 august 2026 la 04:04 UTCresolved

   Mitigations have been rolled out and tests should be running as normal.

1. 31 iulie 2026 la 03:38 UTCinvestigating

   Echipa de ingineri investighează erori ridicate de 501 "neimplementate" observate în API-ul gazduirii atunci când gestionează domenii personalizate. În acest moment nu pare că planul de date este efectuat.

2. 31 iulie 2026 la 04:38 UTCinvestigating

   Credem că am găsit cauza principală şi lucrăm pentru a restabili această porţiune a API-ului nostru. Suntem mai încrezători acum că avionul de date nu este afectat și că acest lucru a fost limitat în domeniul de aplicare al managementului domeniilor personalizate de găzduire.

3. 31 iulie 2026 la 05:14 UTCresolved

   Fix este în curs de rulare afară. ETA pentru rezoluție completă este 31 iulie la ~11:00 UTC, deși unii utilizatori ar fi putut restaura funcționalitatea până atunci.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 18:11 UTCresolved

   Firebase Crashlytics date este întârziat

Traducere automată din actualizarea oficială a incidentului.

1. 20 iulie 2026 la 15:39 UTCinvestigating

   Firebase Test Lab se confruntă cu latență înaltă de execuție pentru dispozitive braț. În prezent investigăm cauza și vom furniza mai multe informații în scurt timp.

2. 20 iulie 2026 la 16:56 UTCinvestigating

   Firebase Test Lab se confruntă în prezent rate crescute de eroare de execuție pentru arme și dispozitive fizice (Android și iOS). Am investigat cauza şi atenuăm problema.

3. 21 iulie 2026 la 14:31 UTCresolved

   Firebase Test Lab se confruntă cu latență înaltă de execuție pentru dispozitive braț. În prezent investigăm cauza și vom furniza mai multe informații în scurt timp.

Traducere automată din actualizarea oficială a incidentului.

1. 13 iulie 2026 la 15:42 UTCinvestigating

   Firebase Crashlytics date este întârziat pentru 2026-07-10

2. 14 iulie 2026 la 19:25 UTCinvestigating

   Firebase Crashlytics date este întârziat pentru 2026-07-10 și 2026-07-11

3. 15 iulie 2026 la 17:23 UTCresolved

   Datele de la baza de foc Crashlytics sunt în prezent întârziate pentru 2026-07-12 și 2026-07-13. Prelucrarea datelor anterioare a fost finalizată. Lotul de BigQuery exportat și datele de streaming rămân exacte.

Traducere automată din actualizarea oficială a incidentului.

1. 4 iulie 2026 la 14:45 UTCresolved

   Performance Monitoring data is delayed

1. 14 iulie 2026 la 20:38 UTCinvestigating

   Investigăm o problemă de sistem. Pentru a proteja stabilitatea platformei, am limitat volumul de date colectate. Se așteaptă o reducere vizibilă a datelor în cadrul tablourilor de bord pentru monitorizarea performanțelor și al exporturilor BigQuery.

Traducere automată din actualizarea oficială a incidentului.

1. 15 iunie 2026 la 18:03 UTCresolved

   We are experiencing an issue causing elevated error rates when loading data on the Crashlytics, Release Monitoring, and Performance Monitoring dashboards, within Android Studio, and via our MCP tools. The team is actively investigating.

1. 11 iunie 2026 la 05:20 UTCidentified

   We are experiencing an issue with Firebase Cloud Messaging’s send apis in Asia beginning on Wednesday, 2026-06-10 21:50 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 23:45 PDT with current details.

2. 11 iunie 2026 la 06:19 UTCidentified

   Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-06-11 03:00 PDT. Customers may observe requests to send messages to FCM taking longer to complete. A small number may experience 5xx errors and should retry with backoff.

3. 11 iunie 2026 la 06:36 UTCidentified

   We are starting to see some recovery.

4. 11 iunie 2026 la 07:15 UTCresolved

   We believe the incident was fully mitigated as of 11:40pm.

1. 1 iunie 2026 la 21:36 UTCresolved

   Android physical tests delayed in FTL. Mitigation in progress.

1. 21 mai 2026 la 13:32 UTCinvestigating

   The issue was triaged and a fix has been found. We will update soon on expected end of this disruption.

2. 21 mai 2026 la 16:45 UTCinvestigating

   The fix has mitigated the issue and we are actively rolling it out. We expect the rollout to complete within a couple of days.

3. 22 mai 2026 la 17:55 UTCresolved

   The fix has been rolled out and service has returned to normal

1. 11 mai 2026 la 17:27 UTCinvestigating

   Firebase Test Lab is experiencing higher wait times on ARM devices. We are currently investigating the cause. Next update in when something significantly changes.

2. 12 mai 2026 la 16:42 UTCresolved

   Firebase Test Lab is no longer experiencing delays for tests on ARM devices. Unless something unexpected happens, this is the last update.

1. 28 aprilie 2026 la 20:29 UTCinvestigating

   Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.

2. 29 aprilie 2026 la 07:53 UTCresolved

   The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

1. 9 aprilie 2026 la 17:00 UTCidentified

   We're investigating the issue and determining the cause

2. 9 aprilie 2026 la 17:12 UTCidentified

   We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests

3. 9 aprilie 2026 la 20:57 UTCresolved

   We believe we've addressed the issue and stuck tests will now run. They may still be delayed as the system works through the queue

1. 9 aprilie 2026 la 18:09 UTCinvestigating

   No updates so far

2. 10 aprilie 2026 la 00:09 UTCresolved

   Problem appears to be mitigated and the error rates are back to normal level.

1. 1 aprilie 2026 la 04:21 UTCinvestigating

   Test Lab ARM devices are experiencing elevated failures rates and delays to test results.

2. 1 aprilie 2026 la 06:09 UTCresolved

   This issue appears to be resolved now. Error rates are back to normal.

1. 30 martie 2026 la 14:52 UTCresolved

   Services are functioning normally as of 2026-03-30 09:00 PDT

1. 31 martie 2026 la 01:34 UTCinvestigating

   Firebase Hosting is aware of missing metrics and logs from Cloud Logging.

2. 31 martie 2026 la 01:35 UTCinvestigating

   Firebase Hosting engineers are working on backfilling missing Cloud Logging entries from 2026-03-23 21:46 UTC to 2026-03-30 16:04 UTC. The ETA is about 11:30 UTC March 31 for that process to complete.

3. 31 martie 2026 la 15:32 UTCresolved

   The logs from the missing period should be restored. However, metrics may not have fully been restored from the time period due to technical limitations.

1. 20 martie 2026 la 13:05 UTCinvestigating

   A recent change is causing 404 errors for clients who send messages to a URL which includes a trailing slash (/v1/projects/my-project/messages:send/ vs /v1/projects/my-project/messages:send). We are in the process of rolling back this change. For clients that are impacted, removing the trailing slash from the send URL will immediately resolve the problem.

2. 20 martie 2026 la 14:40 UTCresolved

   The rollback is complete - service is fully restored.

1. 11 martie 2026 la 17:59 UTCinvestigating

   **Investigating:** We are aware of a service disruption affecting App Hosting deployments from Firebase Studio. **Impact:** Users are currently unable to publish apps with App Hosting from Firebase Studio. **Action:** Our engineers are currently working to identify the root cause and restore deployment functionality as quickly as possible. We will provide an update as soon as we can. **Workaround:** In the meantime, you can publish using the Firebase App Hosting console or the Firebase CLI. Learn more at https://firebase.google.com/docs/app-hosting/get-started .

2. 2 aprilie 2026 la 18:49 UTCresolved

   This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.