Skip to content
Back to CircleCIIncident Postmortem
CircleCI logo

CircleCI

Tracked by PulseWatch

Auto-drafted postmortem

CircleCI outage on May 4 — 1h 34m disruption

May 4, 08:13 AM → May 4, 09:47 AM · 1h 34m · critical

On May 4, 2026, CircleCI experienced a critical service disruption. This incident was detected through user reports and third-party monitoring. The issue was resolved at 09:47 UTC on May 4, 2026.

Peak reports
12
in 15 min
Total reports
68
during the incident
Duration
1h 34m
tracked by PulseWatch

Impact

Users reported experiencing issues with CircleCI services, leading to a critical disruption. A total of 68 user reports were received during the incident, with a peak of 12 reports in a 15-minute period. The most frequently reported issue types were slow or unresponsive service, accounting for 50 reports, and API-related issues, with 18 reports. No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive50
  • API issues18

Incident timeline

  1. May 4, 08:13 AM

    PulseWatch detected elevated report volume (critical severity)

  2. May 4, 08:15 AM

    Peak of 10 reports in 15 minutes (baseline 1.0)

  3. May 4, 08:23 AM

    Status updated: major issue

  4. May 4, 08:28 AM

    Status updated: major issue

  5. May 4, 08:38 AM

    Status updated: major issue

  6. May 4, 08:43 AM

    Status updated: major issue

  7. May 4, 08:53 AM

    Status updated: major issue

  8. May 4, 08:58 AM

    Status updated: major issue

  9. May 4, 09:08 AM

    Status updated: major issue

  10. May 4, 09:13 AM

    Status updated: major issue

  11. May 4, 09:23 AM

    Status updated: major issue

  12. May 4, 09:28 AM

    Status updated: major issue

  13. May 4, 09:47 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 08:13 AM

    CircleCI 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