Is Prefect down?
Last checked 4m agoNo active incidents. All 12 components operational.
Prefect is operational right now. Last checked 4m ago; the most recent incident resolved 17d ago.
Real-time Prefect status, recent outages, and incident history: pulled directly from Prefect's official status page at status.prefect.io every 5 minutes. Pingoru tracks 12 Prefect services and has captured 4 incidents in the last 90 days (99.98% uptime). Get email, Slack, Discord, or webhook alerts the moment Prefect reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Orchestration
Timeline · 2 updates
- identified · Oct 16, 2026, 08:08 PM UTC
Since 18:00 UTC on October 16, most flow runs on Modal push work pools crash during infrastructure startup. Affected runs move from Pending to Crashed with the message "sandbox exited with non-zero code 137." We have tracked the issue to an upgrade in the Modal client library and working to roll back.
- resolved · Oct 16, 2026, 08:31 PM UTC
This incident has been resolved and Modal push pools are fully operational.
Latest: This incident has been resolved and Modal push pools are fully operational.
-
-
Timeline · 1 update
- resolved · Oct 01, 2026, 03:08 PM UTC
Between 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. The issue has been resolved and all services are operating normally.
Latest: Between 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 back…
-
- AutomationsObservabilityOrchestrationUI
Timeline · 2 updates
- monitoring · Sep 30, 2026, 07:32 PM UTC
Between 19:17 and 19:25 UTC, some real-time connections to the Prefect Cloud UI and event streams were interrupted, causing a brief period of elevated errors. Affected clients reconnected automatically.
- resolved · Sep 30, 2026, 08:52 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Sep 21, 2026, 10:49 PM UTC
Between 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 and Prefect Serverless is operating normally.
Latest: Between 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 cra…
-
Incident record
Since April 2026 · incident.io · 12 components checked every 5 minutesThe longest incident in the last year, Service disruption for outbound email on July 30, 2026, ran for 101 minutes. 7 maintenance windows announced in the same period.
Most affected components, last 12 months
- Automations2
- Observability2
- Orchestration2
- UI2
Latest incidents
- Flow Runs Crashing on Modal Push Work Pools
Since 18:00 UTC on October 16, most flow runs on Modal push work pools crash during infrastructure startup. Affected runs move from Pending to Crashed with the…
- Elevated API Error Rates
Between 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…
- Elevated connection errors
Between 19:17 and 19:25 UTC, some real-time connections to the Prefect Cloud UI and event streams were interrupted, causing a brief period of elevated errors.…
- Started Oct 16, 2026, 08:08 PM UTC · Resolved Oct 16, 2026, 08:31 PM UTC · 22m
- Elevated API Error Rates ResolvedStarted Oct 01, 2026, 03:08 PM UTC · Resolved Oct 01, 2026, 03:08 PM UTC · –
- Elevated connection errors ResolvedStarted Sep 30, 2026, 07:32 PM UTC · Resolved Sep 30, 2026, 08:52 PM UTC · 1h 20m
- Started Sep 21, 2026, 10:49 PM UTC · Resolved Sep 21, 2026, 10:49 PM UTC · –