rewindex

ChangesFirebaseFirebase Cloud Monitoring - Low sending availability in Asia-Pacific region

Firebase: Major incident: Firebase Cloud Monitoring - Low sending availability in Asia-Pacific region

Major incidentoutage (model (Jev), 77%)Changed Detected status.firebase.google.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Firebase removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Firebase Cloud Monitoring - Low sending availability in Asia-Pacific region
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-06-11 04:50 UTC
AddedResolved time#5
Before: not present
After: 2026-06-11 06:40 UTC
AddedAffected components#6
Before: not present
After: Cloud Messaging
AddedUpdateservice_outage#7
Before: not present
After: 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.
AddedUpdateservice_outage#8
Before: not present
After: 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.
AddedUpdateservice_outage#9
Before: not present
After: We are starting to see some recovery.
AddedUpdateresolved#10
Before: not present
After: We believe the incident was fully mitigated as of 11:40pm.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Thursday, June 11

1 incident change

All Firebase changesFirebase profileMarkdownJSON