Is Firebase down?
Right now
No. Firebase is operational.
No incidents reported.
Read from status.firebase.google.com · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/firebase/status.agent.json
MCP: upstream_status {"service":"firebase"}
Auth, Firestore, Hosting, Cloud Messaging and Functions.
What Firebase reports
Operational
Taken as is from Firebase's own incident feed. Incident titles and component names below are theirs.
Open status.firebase.google.comUpButler's independent probe
There is no keyless endpoint of Firebase that says anything useful, so UpButler does not probe it. To check your own Firebase account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Firebase incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Firebase Hosting projects presenting intermittent "Bandwidth Quota Exceeded" errors or failing deployments with quota errors. | minor | 33 h 36 min |
Tell your outage from Firebase's
Declare that your project depends on Firebase. When one of your monitors fails while Firebase has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- firebasecurl -s https://upbutler.com/status/firebase/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "firebase",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Firebase down right now?
- No. As of 2026-10-10 05:08 UTC, Firebase is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Firebase's own incident feed at https://status.firebase.google.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Firebase's words.
- How can my agent or app check Firebase status?
- Fetch https://upbutler.com/status/firebase/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"firebase"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Firebase's?
- Add "firebase" to the dependencies of your UpButler workspace. When one of your monitors fails while Firebase has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in databases and data
UpButler is not affiliated with Firebase. Status and incident text belong to Firebase and are read from their public status source; the probe result is UpButler's own measurement.