Firebase status history

Current state: operational — “All services available” per https://status.firebase.google.com (vendor's own feed (hand-written parser)), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days

2incidents, last 90 days

2incidents on record

Incidents per week, last 12 weeks:

vendor's own feed (hand-written parser) only exposes incidents that are open right now, so this history starts on 2026-09-04, the day we first watched Firebase. It fills in from here.

Get Firebase alerts in your Slack — free template RSS for Firebase

Incidents on record (2)

Started	Incident	Status	Impact	Duration
2026-09-10 06:00 UTC	Test Lab: Firebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause.	service_disruption	medium	30 h 29 min (approx.)
2026-07-01 07:00 UTC	Performance Monitoring: Visible reduction in data within Performance Monitoring dashboards and BigQuery exports.	service_disruption	medium	70 d 5 h (approx.)

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Firebase with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "firebase"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}