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

Managed Execution




Operational

1

Upcoming Maintenances

2

Incidents Last 30 Days

0

Maintenances Last 30 Days

External Services

Scheduled Maintenance

Schedule

September 20, 2025 21:00 - 22:00 UTC

Components

Cloud Orchestration, Cloud Automations, Cloud Events/Logs, Cloud UI, Managed Execution

Locations

Prefect Cloud

Description

Prefect Cloud 2 will undergo routine scheduled maintenance for our Redis and database instances. During this time, the Prefect Cloud API 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.

History (Last 30 days)

Incident Status

Operational


Components

Managed Execution


Locations

Prefect Cloud




September 11, 2025 14:07 UTC
[Resolved] We experienced a service disruption that caused flow runs executed via managed execution to crash due to an AWS outage. The incident occurred from 6:01 AM to 6:40 AM ET, lasting approximately 39 minutes.

Incident Status

Partial Service Disruption


Components

Cloud Orchestration


Locations

Prefect Cloud




September 4, 2025 21:56 UTC
[Resolved] Our team has confirmed the bug is fixed. Deployment concurrency limits should function as expected.

September 4, 2025 18:30 UTC
[Monitoring] We have identified an issue with deployment concurrency limits and deployed a fix.