rewindex

CompaniesPrefectIncidents

Prefect: Routine scheduled database maintenance

MaintenancemaintenanceStatus: maintenance completeStarted Not resolved6 updatesstatus.prefect.io (opens in new tab)

Affected components: ServerlessServerlessServerlessObservabilityObservabilityObservabilityUIUIUIAPIAPIAPIOrchestrationOrchestrationOrchestrationAutomationsAutomationsAutomationsAutomations & WebhooksAutomations & WebhooksAutomations & WebhooksServerlessServerlessServerlessLogin & AccessLogin & AccessLogin & AccessNotificationsNotificationsNotifications

Timeline of updates

  1. maintenance scheduled

    During maintenance, the Prefect Cloud API and UI will be unavailable. Scheduled runs may start late. Automations and run updates may be delayed.
    Prefect Cloud will return maintenance responses that instruct compatible Prefect clients to wait and retry API requests. Runs already executing will continue, but operations that require the API will be delayed until maintenance is over. Some runs may require manual recovery or rerunning after maintenance depending on the client version, timeouts, and infrastructure configuration.
    For critical workloads, avoid executions that overlap the window where possible. After maintenance, check affected runs and their actual execution status before rerunning them.

  2. maintenance scheduled

    Maintenance will begin in about 5 minutes.

  3. maintenance in progress

    Maintenance has started

  4. maintenance in progress

    Scheduled maintenance extended to 3:30 PM ET

    Our scheduled maintenance is taking longer than planned, and we're extending the window to 3:30 PM ET (19:30 UTC). Part of the planned database work needs additional time to complete safely.

  5. maintenance in progress

    Maintenance is still ongoing. Apologies for the delay

  6. maintenance complete

    Maintenance is lifted and work should now be resuming. We apologize for the extended maintenance window.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.prefect.io (opens in new tab).

Cite this

Maintenance posted by Prefect, started 2026-10-10 18:00 UTC, not resolved, 6 update(s).

Title
Routine scheduled database maintenance
Vendor
Prefect
Date
URL
https://rewindex.com/company/prefect/incidents/01M3CKR7ZNDG8P6AXAK9T6VQPF

Prefect profileRecent Prefect incidentsAll outages on October 10, 2026Prefect in October 2026MarkdownJSON