Extole Outage History
13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Extole Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Extole Update to Service Sub-ProcessorsThis is a notice of a new service sub-processor Extole clients may elect to use, OpenAI. Sub-processor purpose: Extole uses OpenAI to power its in-product AI Chat offered to client organizations. Data shared with… | 0 min | Resolved |
| Sep 14, 2026 | Consumer API PerformanceThis incident has been resolved. | 10 min | Resolved |
| Jun 26, 2026 | CSS Not RenderingThis incident has been resolved. | 3h 57m | Resolved |
| May 21, 2026 | GitHub Security Incident ResponseGitHub security incident (May 2026) — investigated, no Extole impact We are aware of the security incident disclosed by GitHub on May 20, 2026, involving unauthorized access to GitHub's internal repositories via… | 0 min | Resolved |
| May 5, 2026 | Email DelaysThis incident has been resolved. | 3h 58m | Resolved |
| May 1, 2026 | Consumer Database FailoverOne of the databases in US-EAST-1 experienced a failover and one of the backup database has been promoted. Requests were delayed from 05:08:09 UTC to 05:11:19 UTC. | 0 min | Resolved |
| Apr 29, 2026 | Incerased API Error RateThis incident has been resolved. | 28 min | Resolved |
| Feb 4, 2026 | Core API ErrorsThis incident has been resolved. | 27 min | Resolved |
| Jan 28, 2026 | Consumer API Response DelaysThis incident has been resolved. | 1h 15m | Resolved |
| Jan 26, 2026 | Data Processing DelaysThere is a delay in data processing causing reports to run slower than usual. The root cause has been identified and fixed and reports should run shortly. | 0 min | Resolved |
| Jan 21, 2026 | Data Processing DelaysThis incident has been resolved. | 2h 28m | Resolved |
| Jan 12, 2026 | Consumer API Error RateThis incident has been resolved. We have deployed a fix and are not seeing more errors. Our team is investigating the root cause to mitigate future problems. | 6 min | Resolved |
| Nov 22, 2025 | Consumer API 404s for /zones RequestsThis incident has been resolved. | 51 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Extole incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Extole Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Extole acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Extole outage in this window ran 3h 58m, against a mean recovery of 1h 3m. If you depend on Extole in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.