Arkose Labs Outage History
Arkose Labs is up right nowPingoru has recorded 50 incidents for Arkose Labs: 3 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 2 | 4 of 744 (1%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 3 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 526 (0%) |
Incidents, newest first
Major August 21, 2026 Increased error rates during session setup 3h 17m Arkose Titan Global Status
Started Aug 21, 2026, 07:09 PM UTC· resolved Aug 21, 2026, 10:26 PM UTC
- investigating Aug 21, 2026, 09:27 PM UTC
We are seeing elevated error rates when loading the Arkose challenge during session setup. Some end users may experience failures or delays when completing challenges. We are investigating and will provide an update shortly
- investigating Aug 21, 2026, 09:33 PM UTC
We are continuing to investigate this issue.
- investigating Aug 21, 2026, 10:09 PM UTC
We are seeing elevated error rates during session setup, impacting interactive and challenge traffic. Some end users may experience failures or delays when loading or completing challenges.We are actively investigating and will provide our next update within 45 minutes.
- identified Aug 21, 2026, 10:32 PM UTC
We have identified the issue and recovery is underway. We will continue to monitor and provide our next update within 45 minutes.
- resolved Aug 21, 2026, 10:42 PM UTC
This incident has been resolved.
Notice May 12, 2026 EU-WEST-1: Potential degradation of Arkose Services 1h 21m Ireland Healthcheck
Started May 12, 2026, 10:26 PM UTC· resolved May 12, 2026, 11:48 PM UTC
- 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.
Minor May 7, 2026 US-East-1 : Potential degradation of Arkose Services 2h 35m AWS ec2-us-east-1, North Virginia Healthcheck
Started May 07, 2026, 11:55 PM UTC· resolved May 08, 2026, 02:30 AM UTC
- 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.
Minor October 20, 2025 Increased Error Rates and Latencies 12h 44m North Virginia Healthcheck
Started Oct 20, 2025, 07:11 AM UTC· resolved Oct 20, 2025, 07:55 PM UTC
- identified Oct 20, 2025, 08:10 AM UTC
AWS service is having issues. We are failing over affected services.
- monitoring Oct 20, 2025, 08:45 AM UTC
We’re currently experiencing service interruptions due to an ongoing AWS outage. Our team has initiated failover procedures to minimize impact and restore functionality as quickly as possible. We’re monitoring the situation closely and will provide updates as AWS works toward resolution.
- monitoring Oct 20, 2025, 10:18 AM UTC
We are currently observing improvements in the affected services. We are continuing to actively monitor an ongoing AWS service disruption affecting regions in the Eastern part of the US; we have successfully failed over the majority of our services to alternate infrastructure and will provide another update when full service restoration occurs.
- monitoring Oct 20, 2025, 11:36 AM UTC
Though we are seeing consistent improvements, AWS is still working on fixing issues, we will update once we have information on full resolution.
- monitoring Oct 20, 2025, 12:23 PM UTC
We are currently operating in a failed-over state due to ongoing AWS service disruptions in the US-EAST-1 region; we will continue monitoring recovery progress and initiate failback procedures once AWS confirms full service restoration and stability. Services should be operating normally, however in elevated status condition until all normal AWS region services recover.
- resolved Oct 21, 2025, 01:25 AM UTC
This incident has been resolved.
Major August 11, 2025 Potential degradation of Arkose Services 8m Sydney Healthcheck
Started Aug 11, 2025, 11:29 PM UTC· resolved Aug 11, 2025, 11:38 PM UTC
- investigating Aug 11, 2025, 11:35 PM UTC
We have detected a potential degradation of Arkose Services in the AP-SOUTHEAST-2 region. We are actively investigating the issue and will provide an update shortly.
- resolved Aug 11, 2025, 11:42 PM UTC
This incident has been resolved.
Major June 27, 2025 Potential degradation Arkose Service 41m Singapore Healthcheck
Started Jun 27, 2025, 02:00 AM UTC· resolved Jun 27, 2025, 02:41 AM UTC
- investigating Jun 27, 2025, 02:11 AM UTC
We have detected a potential degradation of Arkose Services in the AP-SOUTHEAST-1 region. We are actively investigating the issue and will provide an update shortly.
- identified Jun 27, 2025, 02:40 AM UTC
The issue has been identified and we are working towards a fix.
- monitoring Jun 27, 2025, 03:03 AM UTC
We are currently monitoring our services as degradation has been resolved.
- monitoring Jun 27, 2025, 03:06 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 27, 2025, 03:44 AM UTC
This incident has been resolved.
Critical May 6, 2025 Potential outage of Arkose Services 19m Ireland Healthcheck
Started May 06, 2025, 10:50 PM UTC· resolved May 06, 2025, 11:09 PM UTC
- investigating May 06, 2025, 10:55 PM UTC
We have detected a potential outage of the Arkose Services Globally. We are actively investigating the issue and will provide an update shortly.
- identified May 06, 2025, 11:06 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 06, 2025, 11:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 06, 2025, 11:10 PM UTC
This incident has been resolved.
Critical March 10, 2025 Arkose Bot Manager: Increased Latency and Timeout Errors 24m
Started Mar 10, 2025, 03:42 PM UTC· resolved Mar 10, 2025, 04:06 PM UTC
- resolved Mar 10, 2025, 04:49 PM UTC
Beginning at 15:42 UTC on March 10, Arkose Bot Manager experienced increased latency and timeouts. Initial investigation shows that this was a backend issue. The issue has stopped occurring and we are currently investigating the root cause. At this time customers should not see an impact as by 16:06 UTC on March 10th the issue had stopped occurring. An Incident Report will be published once investigation of RCA is completed.
Critical December 30, 2024 Arkose Global Bot Manager Errors And Latency 10m North Virginia Healthcheck
Started Dec 30, 2024, 03:11 PM UTC· resolved Dec 30, 2024, 03:22 PM UTC
- investigating Dec 30, 2024, 04:21 PM UTC
We are currently investigating an issue where some customers are seeing increased errors and latency in some regional endpoints.
- investigating Dec 30, 2024, 05:21 PM UTC
We are currently addressing platform issues, with some impact observed in regions including US East 1. While the error rate has decreased significantly, a small number of 503 errors are still being reported. We understand the importance of resolving this quickly and have our team fully engaged, with all hands on deck to ensure the platform’s stability. We have identified some issues within our platform we believe to be contributing to the impact. We are working at stabilizing those services to reduce their overall impact and will continue to troubleshoot after that. Our priority is to restore full functionality as quickly and efficiently as possible. Once the immediate resolution is complete, we will take the time to conduct a detailed post-mortem to analyze the incident thoroughly.
- identified Dec 30, 2024, 05:46 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Dec 30, 2024, 05:53 PM UTC
We have identified that the cause of this incident was resource contention among shared services. We isolated the service causing contention which freed up resources to allow the platform to recover and enter a healthy state again. We are continuing to monitor and conduct a full root cause analysis on this Incident. The Incident impact is now mitigated.