Is Arkose Labs down?
Last checked 8m agoNo incidents right now.
Arkose Labs is operational right now. Last checked 8m ago; the most recent incident resolved 32d ago.
Real-time Arkose Labs status, recent outages, and incident history — pulled directly from Arkose Labs's official status page at https://status.arkoselabs.com every 5 minutes. Pingoru tracks 13 Arkose Labs services and has captured 2 incidents in the last 90 days (99.66% uptime). Get email, Slack, Discord, or webhook alerts the moment Arkose Labs reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Ireland Healthcheck
Timeline · 3 updates
- investigating · May 12, 2026, 10:54 PM UTC
We are currently investigating an issue affecting the Device ID service. The degradation is caused by an infrastructure problem with a third-party cloud provider, impacting service availability in EU-WEST-1. Our team has identified the affected resources and is actively working on remediation. All other services remain unaffected. We will provide a further update as the situation progresses.
- identified · May 12, 2026, 11:51 PM UTC
Device ID service has returned to normal operation in EU-WEST-1. We are continuing to monitor service stability while we await full mitigation. All other services remain unaffected. We will provide a further update once the issue is fully resolved.
- resolved · May 13, 2026, 12:05 AM UTC
As of 23:48 UTC on 12 May 2026, the Device ID service has been restored and is operating normally.
Latest: As of 23:48 UTC on 12 May 2026, the Device ID service has been restored and is operating normally.
-
- AWS ec2-us-east-1North Virginia Healthcheck
Timeline · 3 updates
- investigating · May 08, 2026, 01:47 AM UTC
We are currently investigating an issue affecting the Device ID service. The degradation is caused by an infrastructure problem with a third-party cloud provider, impacting service availability in US-East-1. Our team has identified the affected resources and is actively working on remediation, including failing over to an alternate region. All other services remain unaffected. We will provide a further update as the situation progresses.
- identified · May 08, 2026, 02:33 AM UTC
We have successfully failed over from the affected infrastructure to a healthy region, and the Device ID service has returned to normal operation. We are continuing to monitor service stability while we await full mitigation from our third-party cloud provider on their end. All other services remain unaffected. We will provide a further update once the issue is fully resolved.
- resolved · May 08, 2026, 03:04 AM UTC
As of 02:33 UTC on 8th May 2026, the Device ID service has been restored and is operating normally.
Latest: As of 02:33 UTC on 8th May 2026, the Device ID service has been restored and is operating normally.
-
- Started May 12, 2026, 10:26 PM UTC · Resolved May 12, 2026, 11:48 PM UTC · 1h 21m
- Started May 07, 2026, 11:55 PM UTC · Resolved May 08, 2026, 02:30 AM UTC · 2h 35m