Rewindex

ChangesDepotSome CI jobs failing to start

Depot: Major incident: Some CI jobs failing to start

Major incidentmajor (vendor)Changed Detected status.depot.dev (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Depot removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Some CI jobs failing to start
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-09-20 18:09 UTC
AddedResolved time#5
Before: not present
After: 2026-09-20 19:37 UTC
AddedUpdateinvestigating#6
Before: not present
After: We are investigating reports of some CI jobs failing to start.
AddedUpdateresolved#7
Before: not present
After: This incident has been resolved.
AddedUpdateinvestigating#8
Before: not present
After: We are seeing some lingering failures and are investigating.
AddedUpdatemonitoring#9
Before: not present
After: Service appears to be restored, we are continuing to monitor.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

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.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Sunday, September 20

1 incident change

All Depot changesDepot profileMarkdownJSON