Skip to content
Back to FirebaseIncident Postmortem
Firebase logo

Firebase

Tracked by PulseWatch

Auto-drafted postmortem

Firebase outage on August 14 — 3h 45m disruption

Aug 14, 01:03 AM → Aug 14, 04:48 AM · 3h 45m · medium

On August 14, 2026, Firebase experienced a service disruption. This incident was detected via user reports and lasted approximately 3 hours and 45 minutes. The issue was resolved at 04:48 UTC on August 14, 2026.

Peak reports
11
in 15 min
Total reports
62
during the incident
Duration
3h 45m
tracked by PulseWatch

Impact

Users reported experiencing issues with Firebase, primarily categorized as 'Website down'. A total of 62 user reports were received during the incident, with a peak of 11 reports within a 15-minute period. No specific regional impact was identified from the reports. This disruption was initially brought to our attention through these user reports.

Top reported issues

  • Website down62

Incident timeline

  1. Aug 14, 01:03 AM

    PulseWatch detected elevated report volume (medium severity)

  2. Aug 14, 01:15 AM

    Peak of 4 reports in 15 minutes (baseline 1.3)

  3. Aug 14, 01:18 AM

    Status updated: possible issue

  4. Aug 14, 01:23 AM

    Status updated: possible issue

  5. Aug 14, 01:28 AM

    Status updated: possible issue

  6. Aug 14, 01:33 AM

    Status updated: possible issue

  7. Aug 14, 01:38 AM

    Status updated: possible issue

  8. Aug 14, 01:43 AM

    Status updated: possible issue

  9. Aug 14, 01:48 AM

    Status updated: possible issue

  10. Aug 14, 01:53 AM

    Status updated: possible issue

  11. Aug 14, 01:58 AM

    Status updated: possible issue

  12. Aug 14, 02:03 AM

    Status updated: possible issue

  13. Aug 14, 02:08 AM

    Status updated: possible issue

  14. Aug 14, 02:13 AM

    Status updated: possible issue

  15. Aug 14, 02:18 AM

    Status updated: possible issue

  16. Aug 14, 02:37 AM

    Status updated: possible issue

  17. Aug 14, 02:41 AM

    Status updated: possible issue

  18. Aug 14, 02:51 AM

    Status updated: possible issue

  19. Aug 14, 02:56 AM

    Status updated: possible issue

  20. Aug 14, 03:06 AM

    Status updated: possible issue

  21. Aug 14, 03:11 AM

    Status updated: possible issue

  22. Aug 14, 03:21 AM

    Status updated: possible issue

  23. Aug 14, 03:26 AM

    Status updated: possible issue

  24. Aug 14, 03:36 AM

    Status updated: possible issue

  25. Aug 14, 03:41 AM

    Status updated: possible issue

  26. Aug 14, 03:51 AM

    Status updated: possible issue

  27. Aug 14, 03:56 AM

    Status updated: possible issue

  28. Aug 14, 04:06 AM

    Status updated: possible issue

  29. Aug 14, 04:11 AM

    Status updated: possible issue

  30. Aug 14, 04:22 AM

    Status updated: possible issue

  31. Aug 14, 04:26 AM

    Status updated: possible issue

  32. Aug 14, 04:36 AM

    Status updated: possible issue

  33. Aug 14, 04:42 AM

    Status updated: possible issue

  34. Aug 14, 04:48 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. Aug 14, 01:03 AM

    Firebase status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash