Is Prefect Down?
Reachable from all 8 checked regions
Average response time: 309ms
Last checked · checks run every 6 hours
Official status page: https://status.prefect.io
Prefect uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 49 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
49-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Prefect does
Prefect orchestrates Python data workflows. Prefect Cloud holds the schedule, the run history and the orchestration API, while workers deployed in the customer's own infrastructure poll it for work and execute flows there. Data teams use it to run pipelines on a schedule and to see what failed, so it sits between the schedule and the compute rather than being the compute.
What an outage looks like
Scheduled flow runs never start, because workers poll the Prefect API for work and nothing is answering. Runs already executing keep going on your own infrastructure but stop reporting, so the interface shows them as running long after they finished. Logs and events go missing for the window, and automations and notifications do not fire.
What to do about it
Check status.prefect.io, which lists Orchestration, Login and Access, UI, Observability, Automations, Notifications and Serverless as separate components. If only the UI is affected, scheduling is unaffected and there is nothing to do. Let workers keep polling rather than restarting them, since they retry on their own. Before re-triggering a pipeline by hand, check whether the missed run has already been queued.
Is it down for everyone, or just you?
If this page says Prefect is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Prefect outage FAQ
Does a Prefect Cloud outage stop flows that are already running?
Why did my scheduled run never start?
Is self-hosted Prefect Server affected?
Do automations and notifications catch up after an outage?
How we measure this
- We request Prefect's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Prefect publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Prefect goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring