Close outage on 29 September 2026
Major outageAn email when it goes down, and when it’s back.
“Application impairment”
On 29 September, Close had a major outage affecting its Application UI, which was listed from 17:48 to 18:15 UTC, about 27 minutes. Close's postmortem gave a slightly different window, saying its systems were unavailable from 17:40 to 18:10 UTC. It said a database migration run during a deployment raised error rates on servers still running the previous version, and that service was restored by reverting the change. OpenAI also reported elevated errors across ChatGPT, Codex and its API at the same time, from 17:52 UTC.
Close’s own incident page ↗- When
- 17:49–18:16 UTC
- How long
- 27 min
- Incident open on its page
- 17:48–18:15 UTC
- Components affected
- 1
- Close, 30 days before
- No other outages
What broke when
From Close’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 54 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Update posted
- Investigating
- Application UI: partial outage
- Fix in place, monitoring
- Resolved
- Application UI: back to normal
Where this comes from
Stackpulse reads Close’s official status page at status.close.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with Close. Names and logos belong to their owners.