Prefect Outage History

Started Oct 16, 2026, 08:08 PM UTC· resolved Oct 16, 2026, 08:31 PM UTC

1. identified Oct 16, 2026, 08:08 PM UTC

   Since 18:00 UTC on October 16, most flow runs on Modal push work pools crash during infrastructure startup. Affected runs move from Pending to Crashed with the message "sandbox exited with non-zero code 137." We have tracked the issue to an upgrade in the Modal client library and working to roll back.

2. resolved Oct 16, 2026, 08:31 PM UTC

   This incident has been resolved and Modal push pools are fully operational.

Read the full incident report →

Started Oct 01, 2026, 03:08 PM UTC· resolved Oct 01, 2026, 03:08 PM UTC

1. resolved Oct 01, 2026, 03:08 PM UTC

   Between 11:08 and 11:16 AM EDT, a subset of requests to the Prefect Cloud API returned elevated error rates. Some users may have seen failed or slow API requests and delays in background processing during this window. The issue has been resolved and all services are operating normally.

Read the full incident report →

Started Sep 30, 2026, 07:32 PM UTC· resolved Sep 30, 2026, 08:52 PM UTC

1. monitoring Sep 30, 2026, 07:32 PM UTC

   Between 19:17 and 19:25 UTC, some real-time connections to the Prefect Cloud UI and event streams were interrupted, causing a brief period of elevated errors. Affected clients reconnected automatically.

2. resolved Sep 30, 2026, 08:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 10:49 PM UTC· resolved Sep 21, 2026, 10:49 PM UTC

1. resolved Sep 21, 2026, 10:49 PM UTC

   Between about 22:49 and 00:06 UTC on 21 September, AWS could not start new EC2 and Fargate containers in the us-east-1 region. This caused flow runs submitted in that window to crash. The issue has since been resolved and Prefect Serverless is operating normally.

Read the full incident report →

Started Jul 30, 2026, 12:33 AM UTC· resolved Jul 30, 2026, 02:15 AM UTC

1. identified Jul 30, 2026, 12:33 AM UTC

   We've identified the root cause of the issue affecting outbound email. Customers signing in with an email magic link may be unable to log in. Email invitations and automation email notifications are delayed. Flow runs and API access are unaffected. We'll post another update when the issue is resolved.

2. monitoring Jul 30, 2026, 02:15 AM UTC

   A fix has been implemented and we're monitoring the results. Email services should now be operating normally. We'll continue to watch closely to confirm full recovery before marking this incident as resolved.

3. resolved Jul 30, 2026, 02:17 AM UTC

   This incident has been resolved. Email-related services are fully operational. We apologize for any inconvenience and thank you for your patience.

Read the full incident report →

Started Jul 24, 2026, 09:21 PM UTC· resolved Jul 24, 2026, 09:23 PM UTC

1. investigating Jul 24, 2026, 09:21 PM UTC

   We're currently investigating an issue affecting our logs service. Users may experience issues viewing logs. Our team is actively looking into the cause, and we'll provide an update as soon as we have more information.

2. identified Jul 24, 2026, 09:22 PM UTC

   We've identified the root cause and are working on a fix. Logs may continue to be affected until the fix is fully rolled out. We'll post another update when the issue is resolved.

3. monitoring Jul 24, 2026, 09:23 PM UTC

   A fix has been implemented and we're monitoring the results. Logs should now be operating normally. We'll continue to watch closely to confirm full recovery before marking this incident as resolved.

4. resolved Jul 24, 2026, 09:26 PM UTC

   This incident has been resolved. Logs are fully operational. The issue was caused by an edge case in autoscaling, and we've taken steps to prevent recurrence. We apologize for any inconvenience and thank you for your patience.

Read the full incident report →

Started Jul 16, 2026, 04:09 PM UTC· resolved Jul 16, 2026, 04:25 PM UTC

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.

Read the full incident report →

Started Jul 16, 2026, 09:48 AM UTC· resolved Jul 16, 2026, 10:55 AM UTC

1. identified Jul 16, 2026, 09:48 AM UTC

   An ongoing outage at our authentication provider, WorkOS, is preventing new sign-ins (SSO, Google, Microsoft, and magic-link/email). Users already signed in are unaffected, and API keys, workers, and flow runs continue to operate normally. We're monitoring WorkOS's recovery; sign-in will restore automatically. 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, 09:48 AM UTC

   An ongoing outage at our authentication provider, WorkOS, is preventing new sign-ins (SSO, Google, Microsoft, and magic-link/email). Users already signed in are unaffected, and API keys, workers, and flow runs continue to operate normally. We're monitoring WorkOS's recovery; sign-in will restore automatically.

3. identified Jul 16, 2026, 09:50 AM UTC

   We are seeing some recovery on net new cloud UI logins and will continue to monitor.

4. identified Jul 16, 2026, 09:50 AM UTC

   We are seeing some recovery on net new cloud UI logins and will continue to monitor.

5. monitoring Jul 16, 2026, 10:19 AM UTC

   We continue to see improved UI log-in success rates in new UI sessions and are continuing to monitor.

6. monitoring Jul 16, 2026, 10:19 AM UTC

   We continue to see improved UI log-in success rates in new UI sessions and are continuing to monitor.

7. resolved Jul 16, 2026, 10:55 AM UTC

   We are considering this issue resolved as WorkOS is fully operational.

Read the full incident report →

Started Jun 25, 2026, 02:32 PM UTC· resolved Jun 25, 2026, 02:47 PM UTC

1. investigating Jun 25, 2026, 02:32 PM UTC

   The team has identified elevated API error rates and is investigating. 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. investigating Jun 25, 2026, 02:32 PM UTC

   The team has identified elevated API error rates and is investigating.

3. identified Jun 25, 2026, 02:36 PM UTC

   We have identified a potential root cause and are working on a fix.

4. monitoring Jun 25, 2026, 02:39 PM UTC

   Error rates are improving. The team is continuing to monitor.

5. resolved Jun 25, 2026, 02:47 PM UTC

   Error rates have normalized and the root cause has been identified. Thank you for your patience.

Read the full incident report →

Started Jun 05, 2026, 03:47 PM UTC· resolved Jun 05, 2026, 04:13 PM UTC

1. investigating Jun 05, 2026, 03:47 PM UTC

   We are investigating elevated API error rates beginning at 11:40 am ET. 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. investigating Jun 05, 2026, 03:47 PM UTC

   We are investigating elevated API error rates beginning at 11:40 am ET.

3. monitoring Jun 05, 2026, 03:57 PM UTC

   Error rates have returned to baseline and we will continue to monitor.

4. monitoring Jun 05, 2026, 03:57 PM UTC

   Error rates have returned to baseline and we will continue to monitor.

5. resolved Jun 05, 2026, 04:13 PM UTC

   The issue has been resolved. Error rates have returned to baseline.

Read the full incident report →

Started Jun 01, 2026, 02:26 PM UTC· resolved Jun 01, 2026, 02:56 PM UTC

1. identified Jun 01, 2026, 02:26 PM UTC

   We're investigating elevated API error rates beginning around 10:00 AM eastern. We've identified the issue and are shipping a fix. 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 Jun 01, 2026, 02:26 PM UTC

   We're investigating elevated API error rates beginning around 10:00 AM eastern. We've identified the issue and are shipping a fix.

3. monitoring Jun 01, 2026, 02:45 PM UTC

   Error rates have returned to normal. The team is monitoring.

4. monitoring Jun 01, 2026, 02:45 PM UTC

   Error rates have returned to normal. The team is monitoring.

5. resolved Jun 01, 2026, 02:56 PM UTC

   API error rates are back to normal and stable. Our team appreciates your patience.

Read the full incident report →

Started May 17, 2026, 12:14 AM UTC· resolved May 17, 2026, 12:44 AM UTC

1. investigating May 17, 2026, 12:14 AM UTC

   We're investigating elevated API error rates beginning around 8:00 PM eastern. 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. investigating May 17, 2026, 12:14 AM UTC

   We're investigating elevated API error rates beginning around 8:00 PM eastern.

3. investigating May 17, 2026, 12:24 AM UTC

   Error rates are improving. The team is continuing to investigate.

4. investigating May 17, 2026, 12:24 AM UTC

   Error rates are improving. The team is continuing to investigate.

5. monitoring May 17, 2026, 12:37 AM UTC

   Error rates have returned to normal. The team is monitoring.

6. monitoring May 17, 2026, 12:37 AM UTC

   Error rates have returned to normal. The team is monitoring.

7. resolved May 17, 2026, 12:44 AM UTC

   API error rates are back to normal and stable. Our team appreciates your patience.

Read the full incident report →

Started Apr 19, 2026, 09:08 PM UTC· resolved Apr 19, 2026, 09:08 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →