Firebase 中断历史

1. 2026年8月11日 UTC 13:17investigating

   We are in the progress of fixing.

2. 2026年8月11日 UTC 23:55investigating

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

3. 2026年8月12日 UTC 04:04resolved

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

1. 2026年7月31日 UTC 03:38investigating

   工程组正在调查Hosting在管理自定义域时发现的提升501"未执行"错误. 目前看来数据平面并未被执行.

2. 2026年7月31日 UTC 04:38investigating

   我们认为,我们找到了根源,并正在努力恢复我国API的这一部分。 现在,我们更加相信,数据平面没有受到影响,而且范围仅限于Hosting自定义域的管理.

3. 2026年7月31日 UTC 05:14resolved

   修复工作正在展开。 完全解析的ETA是7月31日~11:00 UTC,尽管一些用户可能在此之前已经恢复了功能.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 18:11resolved

   火灾基地崩溃分析数据被延迟

自动翻译自官方事件更新。

1. 2026年7月20日 UTC 15:39investigating

   火地试验实验室的臂部装置的执行间隔很长。 我们目前正在调查这一原因,不久将提供更多信息.

2. 2026年7月20日 UTC 16:56investigating

   Firebase测试实验室目前手臂和物理设备(Android和iOS)的执行出错率正在提高. 我们已经调查了原因,并且正在缓解这一问题.

3. 2026年7月21日 UTC 14:31resolved

   火地试验实验室的臂部装置的执行间隔很长。 我们目前正在调查这一原因,不久将提供更多信息.

自动翻译自官方事件更新。

1. 2026年7月13日 UTC 15:42investigating

   Firebase Crashlytics 数据被延迟到 2026-07-10

2. 2026年7月14日 UTC 19:25investigating

   Firebase Crashlytics 数据被延迟到 2026-07-10 和 2026-07-11

3. 2026年7月15日 UTC 17:23resolved

   Firebase Crashlytics数据目前被延迟到2026-07-12和2026-07-13. 较早日期的处理已经完成。 输出出大查询批次,流出数据保持准确.

自动翻译自官方事件更新。

1. 2026年7月4日 UTC 14:45resolved

   Performance Monitoring data is delayed

1. 2026年7月14日 UTC 20:38investigating

   我们正在调查一个系统问题。 为了保护平台稳定,我们限制了所收集数据的数量。 期望业绩监测仪表板和大查询出口中的数据明显减少.

自动翻译自官方事件更新。

1. 2026年6月15日 UTC 18:03resolved

   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. 2026年6月11日 UTC 05:20identified

   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. 2026年6月11日 UTC 06:19identified

   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. 2026年6月11日 UTC 06:36identified

   We are starting to see some recovery.

4. 2026年6月11日 UTC 07:15resolved

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

1. 2026年6月1日 UTC 21:36resolved

   Android physical tests delayed in FTL. Mitigation in progress.

1. 2026年5月21日 UTC 13:32investigating

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

2. 2026年5月21日 UTC 16:45investigating

   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. 2026年5月22日 UTC 17:55resolved

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

1. 2026年5月11日 UTC 17:27investigating

   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. 2026年5月12日 UTC 16:42resolved

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

1. 2026年4月28日 UTC 20:29investigating

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

2. 2026年4月29日 UTC 07:53resolved

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

1. 2026年4月9日 UTC 17:00identified

   We're investigating the issue and determining the cause

2. 2026年4月9日 UTC 17:12identified

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

3. 2026年4月9日 UTC 20:57resolved

   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. 2026年4月9日 UTC 18:09investigating

   No updates so far

2. 2026年4月10日 UTC 00:09resolved

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

1. 2026年4月1日 UTC 04:21investigating

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

2. 2026年4月1日 UTC 06:09resolved

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

1. 2026年3月30日 UTC 14:52resolved

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

1. 2026年3月31日 UTC 01:34investigating

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

2. 2026年3月31日 UTC 01:35investigating

   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. 2026年3月31日 UTC 15:32resolved

   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. 2026年3月20日 UTC 13:05investigating

   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. 2026年3月20日 UTC 14:40resolved

   The rollback is complete - service is fully restored.

1. 2026年3月11日 UTC 17:59investigating

   **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. 2026年4月2日 UTC 18:49resolved

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