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

5

Incidents Last 30 Days

1

Maintenances Last 30 Days

External Services

GitHub

Google Cloud

SendGrid

Status.io

Stripe

History (Last 30 days)

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.
Routine scheduled database maintenancePlanned Maintenance

Description

Prefect Cloud will undergo routine scheduled maintenance for our database instance. During this time, the Prefect Cloud APIs will be inaccessible for a brief period, which is typically less than ten minutes, but may last for up to an hour. While work may run late during this maintenance window, no work or data will be lost.


Components

Cloud Orchestration, Cloud Automations, Cloud Events/Logs, Cloud UI, Cloud IP address, Webhooks and Automations IP Addresses


Locations

Prefect Cloud


Schedule

May 10, 2025 18:00 - May 10, 2025 19:00 UTC


May 10, 2025 18:54 UTC
[Update] Prefect Cloud maintenance has completed. Thank you for your patience.

May 10, 2025 18:02 UTC
[Update] Prefect Cloud maintenance has begun.
12:45 ET - 12:52 ET Runs CrashingOperational

Incident Status

Operational


Components

Cloud Orchestration


Locations

Prefect Cloud



May 8, 2025 17:06 UTC
[Resolved] From 12:45 ET - 12:52 ET runs may have crashed from being unable to access the Prefect Cloud API. The issue was immediately identified and resolved.
Elevated Flow Run Failure RatesOperational

Incident Status

Operational


Components

Cloud Orchestration, Cloud UI


Locations

Prefect Cloud



April 24, 2025 15:06 UTC
[Resolved] Error rates have remained at baseline level and the system continues to function as expected.

April 24, 2025 14:47 UTC
[Monitoring] Error rates have returned to normal levels as has the ability to view task runs from the UI. We are continuing to monitor.

April 24, 2025 14:38 UTC
[Identified] Update: Task runs are being processed but are unable to be viewed in the UI. We are continuing to investigate.

April 24, 2025 14:30 UTC
[Identified] We have identified the cause and are working on implementing a fix.

April 24, 2025 14:16 UTC
[Investigating] We are investigating unusually high Flow Run failure rates. The team will update as we investigate further.
Delayed Execution - Prefect Serverless and Push Work PoolsOperational

Incident Status

Operational


Components

Cloud Orchestration


Locations

Prefect Cloud



April 21, 2025 19:45 UTC
[Resolved] Our team has confirmed the system is working as expected.

April 21, 2025 19:40 UTC
[Monitoring] Beginning at approximately 2:30 pm eastern, flow run execution for Prefect Serverless and Push Work Pools was delayed. Our team has implemented a fix and will continue to monitor.
Elevated API Error RatesPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Cloud Orchestration


Locations

Prefect Cloud



April 17, 2025 16:11 UTC
[Resolved] Error rates have returned to baseline and the system is functioning as expected.

April 17, 2025 15:50 UTC
[Monitoring] We have implemented a fix. Error rates have returned to baseline. Our team is continuing to monitor.

April 17, 2025 15:26 UTC
[Identified] We have identified the root cause of elevated error rates and we are taking steps to mitigate.

April 17, 2025 15:11 UTC
[Investigating] Our team is investigating elevated API error rates