Arkose Labs Outage History
3 incidents recorded over the last 365 days, 3 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 Arkose Labs Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 21, 2026 | Increased error rates during session setupThis incident has been resolved. | 59 min | Resolved |
| May 12, 2026 | EU-WEST-1: Potential degradation of Arkose ServicesAs of 23:48 UTC on 12 May 2026, the Device ID service has been restored and is operating normally. | 1h 21m | Resolved |
| May 7, 2026 | US-East-1 : Potential degradation of Arkose ServicesAs of 02:33 UTC on 8th May 2026, the Device ID service has been restored and is operating normally. | 2h 35m | 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 Arkose Labs 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 Arkose Labs 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 Arkose Labs 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 Arkose Labs outage in this window ran 2h 35m, against a mean recovery of 1h 38m. If you depend on Arkose Labs 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.