Arkose Labs Outage History

Arkose Labs is up right now

Arkose Labs had 4 outages in the last 2 years totaling 19h 58m of downtime — averaging 0.2 incidents per month.

There were 4 Arkose Labs outages since October 20, 2025 totaling 19h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.arkoselabs.com

Major August 21, 2026

Increased error rates during session setup

Detected by Pingoru
Aug 21, 2026, 07:09 PM UTC
Resolved
Aug 21, 2026, 10:26 PM UTC
Duration
3h 17m
Affected: Arkose Titan Global Status
Timeline · 5 updates
  1. 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

  2. investigating Aug 21, 2026, 09:33 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

  5. resolved Aug 21, 2026, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 12, 2026

EU-WEST-1: Potential degradation of Arkose Services

Detected by Pingoru
May 12, 2026, 10:26 PM UTC
Resolved
May 12, 2026, 11:48 PM UTC
Duration
1h 21m
Affected: Ireland Healthcheck
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Minor May 7, 2026

US-East-1 : Potential degradation of Arkose Services

Detected by Pingoru
May 07, 2026, 11:55 PM UTC
Resolved
May 08, 2026, 02:30 AM UTC
Duration
2h 35m
Affected: AWS ec2-us-east-1North Virginia Healthcheck
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Minor October 20, 2025

Increased Error Rates and Latencies

Detected by Pingoru
Oct 20, 2025, 07:11 AM UTC
Resolved
Oct 20, 2025, 07:55 PM UTC
Duration
12h 44m
Affected: North Virginia Healthcheck
Timeline · 6 updates
  1. identified Oct 20, 2025, 08:10 AM UTC

    AWS service is having issues. We are failing over affected services.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. resolved Oct 21, 2025, 01:25 AM UTC

    This incident has been resolved.

Read the full incident report →