Skip to main content
down.guideby Sazabi
Firebase
DWN-c222d96dc4FirebaseResolved

RESOLVED: We are tracking a networking issue that may affect a significant part of the fleet. Devices may be unable to connect to backends that support IPv4 only (IPv6 and dual support are not affecte

Degraded Lasted 0m · started · Firebase's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
18of 100

What to do

  • Check whether you use Firebase in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-10-27 22:28 UTC and 2026-10-27 22:28 UTC may need a replay.

  • Subscribe to Firebase's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=firebase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Firebase 1

  1. resolved

    Incident began at 2026-10-22 15:54 and ended at 2026-10-24 01:00 (all times are US/Pacific ). The issue has been identified and mitigation is in process. Affected products: Test Lab

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-c222d96dc4

Is Firebase still down?

No, this incident was resolved 2026-10-27 22:28 UTC. For Firebase's live state, see https://down.guide/firebase.

How long did it last?

0m, from 2026-10-27 22:28 UTC to 2026-10-27 22:28 UTC, by the times Firebase posted.

What was affected?

Firebase named in us.

What caused it?

Firebase hasn't published a root cause. If it does, it shows here.

Where does this come from?

Firebase's official status page, https://status.firebase.google.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.

Sources

Feed