Prefect: Service disruption for logs component
Affected components: Observability
Timeline of updates
- investigating
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.
- identified
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.
- monitoring
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.
- resolved
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.
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.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
54eea5afb3aaf8c1…
Impact, status and times are the vendor’s own, as last archived. View on status.prefect.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Prefect, started 2026-07-24 21:21 UTC, resolved after 6 min, 4 update(s).
- Title
- Service disruption for logs component
- Vendor
- Prefect
- Date
- URL
- https://rewindex.com/company/prefect/incidents/01KYB023QA8XS4WGYRH11BVNTG
Prefect profileRecent Prefect incidentsAll outages on July 24, 2026Prefect in July 2026MarkdownJSON