Is Prefect Down?

No — Prefect is up

Prefect's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 284 ms

Right now

The verdict is the worse of these two. How we decide

Prefect's status page

status.prefect.io · read 2 minutes ago · checked every 3 minutes

Operational

Prefect's components, as its status page reports them
Component	Status
Automations	Operational
Docs	Operational
Login & Access	Operational
Notifications	Operational
Observability	Operational
Orchestration	Operational
Serverless	Operational
UI	Operational
API	Operational
Automations & Webhooks	Operational
Serverless	Operational

Open their status page

FlareWarden checks

prefect.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 284 ms
Checked: 3 hours ago

By region

Ashburn reachable, 245 ms
Frankfurt reachable, 250 ms
Johannesburg reachable, 626 ms
London reachable, 107 ms
Los Angeles reachable, 209 ms
Newark reachable, 281 ms
São Paulo reachable, 282 ms
Tokyo reachable, 277 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	113 ms	1 ms	7 ms	227 ms
Frankfurt	189 ms	1 ms	9 ms	243 ms
Johannesburg	436 ms	1 ms	76 ms	588 ms
London	39 ms	1 ms	10 ms	99 ms
Los Angeles	135 ms	1 ms	29 ms	195 ms
Newark	170 ms	1 ms	22 ms	269 ms
São Paulo	205 ms	1 ms	11 ms	270 ms
Tokyo	193 ms	1 ms	7 ms	268 ms

We check that prefect.io loads, not every feature behind it. Test it yourself

History

Incidents Prefect reported

Since Oct 22, 3 days · from status.prefect.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Prefect website availability

Measured by FlareWarden · prefect.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 297ms

Last 30 days

63-day clean streak

Sep 25 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of prefect.io from multiple regions every 6 hours. Prefect's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 63 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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.

Test it yourself

Related services

Prefect outage FAQ

Does a Prefect Cloud outage stop flows that are already running?

Not immediately. Flows execute on your own workers, so the Python keeps running where it was. What breaks is the reporting path: logs sent to the Prefect Cloud API do not arrive, state updates are not recorded, and the run appears stuck in the interface. The work may well have completed successfully with no record that it did.

Why did my scheduled run never start?

Because workers get their work by polling. A worker checks its work pool for scheduled runs at a regular interval, fifteen seconds by default, and if the orchestration API is unavailable there is nothing to hand it. The worker itself is healthy and picks the run up once the API answers, which is why restarting workers during an incident does not help.

Is self-hosted Prefect Server affected?

No. Prefect Server runs in your own infrastructure and does not depend on Prefect Cloud, so an incident on Prefect's side does not reach it. Workers can be pointed at either one. If you are self-hosted and flows have stopped, the cause is in your own deployment rather than anything on the status page.

Do automations and notifications catch up after an outage?

Treat them as missed rather than delayed. Automations and Notifications are tracked as their own components, separate from Orchestration, which means alerting can fail while flows keep being scheduled. That is the dangerous combination: a pipeline fails, the notification never arrives, and nobody looks until the next morning.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Prefect itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Prefect goes down

We check Prefect every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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

Free plan available No credit card required