Prefect Cloud Outage History
10 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Prefect Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 16, 2026 | Flow Runs Crashing on Modal Push Work PoolsThis incident has been resolved and Modal push pools are fully operational. | 22 min | Resolved |
| Oct 10, 2026 | Routine scheduled database maintenanceMaintenance is still ongoing. Apologies for the delay | 1h 21m | Resolved |
| Oct 1, 2026 | Elevated API Error RatesBetween 11:08 and 11:16 AM EDT, a subset of requests to the Prefect Cloud API returned elevated error rates. Some users may have seen failed or slow API requests and delays in background processing during this window… | -23 min | Resolved |
| Sep 30, 2026 | Elevated connection errorsThis incident has been resolved. | 1h 20m | Resolved |
| Sep 22, 2026 | Prefect Serverless service disruptionBetween about 22:49 and 00:06 UTC on 21 September, AWS could not start new EC2 and Fargate containers in the `us-east-1` region. This caused flow runs submitted in that window to crash. The issue has since been resolved… | -974 min | Resolved |
| Jul 30, 2026 | Service disruption for outbound emailThis incident has been resolved. Email-related services are fully operational. We apologize for any inconvenience and thank you for your patience. | 1h 43m | Resolved |
| Jul 24, 2026 | Service disruption for logs componentThis incident has been resolved. Logs are fully operational. The issue was caused by an edge case in autoscaling, and we've taken steps to prevent recurrence. We apologize for any inconvenience and thank you for your… | 5 min | Resolved |
| Jul 22, 2026 | Elevated errors and degraded orchestration performanceThe issue affecting the Prefect Cloud API and UI has been fully resolved and all services are operating normally, including background processing. We apologize for the disruption. | 26 min | Resolved |
| Jul 20, 2026 | Github incident is impacting Prefect Cloud managed execution and Prefect Horizon operationsAs 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. | 40 min | Resolved |
| Jul 16, 2026 | Elevated Error RatesBetween roughly 15:50 and 16:15 UTC, some requests intermittently returned errors. Execution of flows and tasks was unaffected. Service returned to normal by ~16:15 UTC. | 24h 20m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Prefect Cloud incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Prefect Cloud Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Prefect Cloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Prefect Cloud outage in this window ran 1d, against a mean recovery of 3h 47m. If you depend on Prefect Cloud in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.