- Status page says
- Operational since Oct 19
- Last 90 days
- 9 incidents, 1 major or critical
- Rewrites caught
- None so far
- Next deprecation
- None announced
Our copy of Chainguard’s status page starts Aug 6; hatched days are before that. Select a day to jump to its incidents.
How Chainguard reports incidents
Not enough incidents to compare Chainguard with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Chainguard has 9 and 9).
Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors
Dependencies
What Chainguard relies on and who relies on Chainguard, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.
Chainguard depends on
| Provider | Evidence | Signal |
|---|---|---|
| GitHub | blamed in 1 incident “…ge and image builds be processed successfully, though some may still experience delays as GitHub continues to drain their backlog and fully restore throughput. GitHub has deployed fixes and is making…” incident | Likely |
Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.
Changes and edits
Incidents Chainguard rewrote or removed, and notable changes to the pages we watch.
Struck in red is what Chainguard removed. Blue is what they added.
Thursday, August 6
1 incident change
- CriticalCritical incident
Pricing and pages we watch
| Page | Versions | Last changed | Last checked | History |
|---|---|---|---|---|
| Privacy policy (opens in new tab) | 1 | No changes yet | ||
| Terms of service (opens in new tab) | 1 | No changes yet |
Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
The Weekly Rewind: one short weekly email on what changed at Chainguard and the other vendors we track, including silent edits. Subscribe (opens in new tab)
Incidents
9 incidents since Aug 6, 1 of them major or critical. Maintenance is left out.
Tuesday, October 6
1 incident
- Minor, 10 daysMinor incident
Thursday, October 1
1 incident
- Minor, 1 h 1 minMinor incident
Wednesday, September 9
1 incident
- Minor, 10 minMinor incident
Tuesday, September 8
1 incident
- Minor, 24 h 2 minMinor incident
Monday, August 24
1 incident
- Minor, 2 daysMinor incident
Friday, August 14
1 incident
- Minor, 8 h 58 minMinor incident
Monday, August 10
1 incident
- Minor, 24 hMinor incident
Friday, August 7
1 incident
- Minor, 27 minMinor incident
Thursday, August 6
1 incident, 1 major or critical
- Critical, 5 h 15 minCritical incident