Arkose Labs Outage History

Arkose Labs is up right now

Arkose Labs had 5 outages in the last 2 years totaling 17h 31m of downtime — averaging 0.2 incidents per month.

There were 5 Arkose Labs outages since June 27, 2025 totaling 17h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.arkoselabs.com

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 →

Major August 11, 2025

Potential degradation of Arkose Services

Detected by Pingoru
Aug 11, 2025, 11:29 PM UTC
Resolved
Aug 11, 2025, 11:38 PM UTC
Duration
8m
Affected: Sydney Healthcheck
Timeline · 2 updates
  1. 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.

  2. resolved Aug 11, 2025, 11:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 27, 2025

Potential degradation Arkose Service

Detected by Pingoru
Jun 27, 2025, 02:00 AM UTC
Resolved
Jun 27, 2025, 02:41 AM UTC
Duration
41m
Affected: Singapore Healthcheck
Timeline · 5 updates
  1. 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.

  2. identified Jun 27, 2025, 02:40 AM UTC

    The issue has been identified and we are working towards a fix.

  3. monitoring Jun 27, 2025, 03:03 AM UTC

    We are currently monitoring our services as degradation has been resolved.

  4. monitoring Jun 27, 2025, 03:06 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 27, 2025, 03:44 AM UTC

    This incident has been resolved.

Read the full incident report →