Prefect incident

Elevated Error Rates

Minor Resolved View vendor source →

Prefect experienced a minor incident on July 16, 2026 affecting Cloud Orchestration and Status page (Prefect Cloud), lasting 15m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 04:09 PM UTC
Resolved
Jul 16, 2026, 04:25 PM UTC
Duration
15m
Detected by Pingoru
Jul 16, 2026, 04:09 PM UTC

Affected components

Cloud OrchestrationStatus page (Prefect Cloud)

Update timeline

  1. identified Jul 16, 2026, 04:09 PM UTC

    We are investigating an issue causing intermittent errors when loading flow run lists and details in the UI and API. Other Prefect Cloud functionality - including flow run execution, scheduling, and task orchestration - is not affected, and your workflows continue to run normally. Affected requests may return a 503 error and can be retried. Our engineering team has identified the source and is actively working on remediation. We will provide another update shortly. Back to current status Status History Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

  2. identified Jul 16, 2026, 04:09 PM UTC

    We are investigating an issue causing intermittent errors when loading flow run lists and details in the UI and API. Other Prefect Cloud functionality - including flow run execution, scheduling, and task orchestration - is not affected, and your workflows continue to run normally. Affected requests may return a 503 error and can be retried. Our engineering team has identified the source and is actively working on remediation. We will provide another update shortly.

  3. resolved Jul 16, 2026, 04:25 PM UTC

    Between roughly 15:50 and 16:15 UTC, some requests intermittently returned errors. Execution of flows and tasks was unaffected. Service returned to normal by ~16:15 UTC.