All Systems Operational

Updated a few seconds ago

We continuously monitor our service. Any issues will be posted here. Prefect Cloud occasionally undergoes routine scheduled maintenance, which results in delayed work during this window. Prefect strives to publish upcoming maintenance events on this page at least 7 days in advance. Public Status JSON API: https://2266113422411059.hostedstatus.com/1.0/status/5f33ff702715c204c20d6da1 Please note that Legacy Cloud incidents and maintenance will be posted to https://prefect-legacy.status.io/ instead.

Cloud Orchestration




Operational

Cloud Automations




Operational

Cloud Events/Logs




Operational

Cloud UI




Operational

Cloud IP address




Operational

Webhooks and Automations IP Addresses




Operational

0

Upcoming Maintenances

3

Incidents Last 30 Days

0

Maintenances Last 30 Days

External Services

GitHub

Google Cloud

SendGrid

Status.io

Stripe

History (Last 30 days)

Partial disruption to marking runs lateOperational

Incident Status

Operational


Components

Cloud Orchestration


Locations

Prefect Cloud



June 6, 2025 16:14 UTC
[Resolved] We have identified an issue where some runs were not marked as late between 2025-06-04 and 2025-06-06. This is now resolved and runs will be correctly marked as late.
Elevated Flow Run Failure RatesPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Cloud Orchestration


Locations

Prefect Cloud



May 30, 2025 19:43 UTC
[Resolved] Error rates have decreased as of 11:15a PT / 2:15p ET. This issue is now resolved

May 30, 2025 18:35 UTC
[Monitoring] We've identified the issue and have pushed a fix. We are monitoring

May 30, 2025 17:49 UTC
[Investigating] At 10:30a PT / 1:30p ET, Prefect Cloud started experiencing elevated error rates and latency. We are investigating
Elevated Flow Run Failure RatesOperational

Incident Status

Operational


Components

Cloud Orchestration


Locations

Prefect Cloud



May 13, 2025 08:00 UTC
[Resolved] At 4 am ET, elevated API error rates resulted in failed flow runs. The issue was immediately identified and resolved.