Cursor
No data
Last success —
No component payload
No data
Last success —
No component payload
Official incident · Cursor
resolved · 2026-09-23 17:14:16 UTC · Resolved 2026-09-23 18:43:20 UTC
Official updates
This incident has been resolved.
A fix has been implemented and we are monitoring for service restoration.
The root cause has been identified and a fix is being implemented.
Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.