61 Firebase incidents · Haziran 2025 — official updates, affected components, duration and resolution details.
We are in the progress of fixing.
Mitigations have been applied, and tests should start running again. However, wait times may still be longer than normal during this recovery period.
Mitigations have been rolled out and tests should be running as normal.
Mühendislik ekibi, özel domainleri yönetmek için Hosting API'sinde görülen 501 "basit" hataları araştırıyor. Bu zamanda veri uçağının etkilendiği görünmüyor.
Kök nedeni bulduk ve API'mizin bu kısmını restore etmek için çalışıyoruz. Artık veri uçağının etkilenmediği ve bu, Hosting özel alanların yönetimi ile sınırlı olduğu konusunda daha eminyiz.
Düzeltildi. Tamamlanan karar için ETA 31 Temmuz - 11:00 UTC, ancak bazı kullanıcılar daha önce işlevselliği restore edebilir.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Firebase Crashlytics verileri gecikiyor
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Firebase Test Lab, kol cihazları için yüksek uygulama gecikmesi yaşıyor. Şu anda nedenini araştırıyoruz ve kısa sürede daha fazla bilgi sağlayacaktır.
Firebase Test Lab şu anda kol ve fiziksel cihazlar için daha fazla uygulama hataları yaşıyor (Android ve iOS). Nedeni araştırdık ve sorunu azaltıyoruz.
Firebase Test Lab, kol cihazları için yüksek uygulama gecikmesi yaşıyor. Şu anda nedenini araştırıyoruz ve kısa sürede daha fazla bilgi sağlayacaktır.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Firebase Crashlytics verileri 2026-07-10 için gecikiyor
Firebase Crashlytics verileri 2026-07-10 ve 2026-07-11 için ertelendi
Firebase Crashlytics verileri şu anda 2026-07-12 ve 2026-07-13 için ertelendi. Daha önceki tarihler için işlem tamamlandı. BigQuery toplu ihracat ve akış verileri doğru kalır.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Performance Monitoring data is delayed
Bir sistem sorunu araştırıyoruz. Platform istikrarını korumak için, toplanan verilerin hacmini sınırlıyoruz. Performans İzleme panjurları ve BigQuery ihracatı içindeki verilerde görünür bir azalma bekleyin.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
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.
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.
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.
We are starting to see some recovery.
We believe the incident was fully mitigated as of 11:40pm.
Android physical tests delayed in FTL. Mitigation in progress.
The issue was triaged and a fix has been found. We will update soon on expected end of this disruption.
The fix has mitigated the issue and we are actively rolling it out. We expect the rollout to complete within a couple of days.
The fix has been rolled out and service has returned to normal
Firebase Test Lab is experiencing higher wait times on ARM devices. We are currently investigating the cause. Next update in when something significantly changes.
Firebase Test Lab is no longer experiencing delays for tests on ARM devices. Unless something unexpected happens, this is the last update.
Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.
The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
We're investigating the issue and determining the cause
We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests
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
No updates so far
Problem appears to be mitigated and the error rates are back to normal level.
Test Lab ARM devices are experiencing elevated failures rates and delays to test results.
This issue appears to be resolved now. Error rates are back to normal.
Services are functioning normally as of 2026-03-30 09:00 PDT
Firebase Hosting is aware of missing metrics and logs from Cloud Logging.
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.
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.
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.
The rollback is complete - service is fully restored.
**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 .
This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.