CircleCI: GitHub Check Notifications Impacted During RabbitMQ Maintenance
Timeline of updates
- resolved
Between 20:20 and 20:26 UTC, following our scheduled RabbitMQ maintenance, a small number of workflows may have experienced issues with GitHub check notifications. Impact: - Some workflows showed no check run status in GitHub - Some workflows showed check runs stuck in "pending" state - User flows requiring these checks may have been blocked Resolution: This issue resolved upon completion of our maintenance. All services are now operating normally. We apologize for any inconvenience during this maintenance period. If you have builds that completed during this window with pending or missing checks, a rerun will restore the correct status.
From CircleCI’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.circleci.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by CircleCI, started 2025-11-22 01:00 UTC, resolved after 0 min, 1 update(s).
- Title
- GitHub Check Notifications Impacted During RabbitMQ Maintenance
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/scp36zp1kb59
CircleCI profileRecent CircleCI incidentsAll outages on November 22, 2025CircleCI in November 2025MarkdownJSON