Prefect: Github incident is impacting Prefect Cloud managed execution and Prefect Horizon operations
Prefect removed a resolved minor incident affecting Prefect Cloud managed execution and Prefect Horizon operations. The incident started at 2026-07-20 00:55 UTC and was resolved at 2026-07-20 01:36 UTC; Prefect reported recovery in error rates and latency for GitHub-related operations, despite GitHub’s incident remaining active.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Serverless
Timeline of updates
- monitoring
This is an advisory incident, please track the status of Github at https://www.githubstatus.com: https://www.githubstatus.com//.
- resolved
As of 9:25pm ET, we're seeing error rates and latency recover on Github-related operations. Although their incident is still active, the impact on Prefect Cloud is resolved.
Changes Rewindex caught on this incident
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
1219eeec75ddd416…
Rewindex captured a newer version after the last checkpoint; the next run (00:41 UTC) commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.prefect.io (opens in new tab).