- Detected by Pingoru
- May 12, 2026, 10:54 PM UTC
- Resolved
- May 13, 2026, 12:05 AM UTC
- Duration
- 1h 10m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:47 AM UTC
- Resolved
- May 08, 2026, 03:04 AM UTC
- Duration
- 1h 17m
Affected: 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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- Detected by Pingoru
- May 06, 2025, 10:50 PM UTC
- Resolved
- May 06, 2025, 11:09 PM UTC
- Duration
- 19m
Affected: Ireland Healthcheck
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2025, 04:49 PM UTC
- Resolved
- Mar 10, 2025, 03:42 PM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
Critical December 30, 2024 - Detected by Pingoru
- Dec 30, 2024, 03:11 PM UTC
- Resolved
- Dec 30, 2024, 03:22 PM UTC
- Duration
- 10m
Affected: North Virginia Healthcheck
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Oct 10, 2024, 11:22 PM UTC
- Resolved
- Oct 10, 2024, 11:37 PM UTC
- Duration
- 14m
Affected: North Virginia HealthcheckOregon HealthcheckSingapore HealthcheckIreland HealthcheckOhio HealthcheckSydney Healthcheck
Timeline · 3 updates
-
investigating Oct 10, 2024, 11:22 PM UTC
We are currently investigating an issue with Arkose Labs Puzzles. We will post an update as soon as possible.
-
identified Oct 10, 2024, 11:31 PM UTC
We believe we have identified the issue and are validating resolution.
-
resolved Oct 10, 2024, 11:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2024, 06:31 PM UTC
- Resolved
- Sep 10, 2024, 07:22 PM UTC
- Duration
- 51m
Affected: North Virginia HealthcheckOregon HealthcheckSingapore HealthcheckIreland HealthcheckOhio HealthcheckSydney Healthcheck
Timeline · 2 updates
-
identified Sep 11, 2024, 01:08 AM UTC
Between 18:31 UTC and 19:22 UTC on September 10, we experienced an issue with our Verify API affecting multiple regions. The issue has been identified and mitigated, and we are actively working on a solution to prevent any future impact to our customers.
-
resolved Sep 11, 2024, 01:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2024, 08:22 AM UTC
- Resolved
- Sep 02, 2024, 08:48 AM UTC
- Duration
- 25m
Affected: Sydney Healthcheck
Timeline · 2 updates
-
investigating Sep 02, 2024, 08:22 AM UTC
We have detected a potential degradation of the Verify API in the AP-SOUTHEAST-2 region. We are actively investigating the issue and will provide an update shortly.
-
resolved Sep 02, 2024, 08:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2024, 07:35 AM UTC
- Resolved
- Sep 02, 2024, 08:11 AM UTC
- Duration
- 36m
Affected: Sydney Healthcheck
Timeline · 2 updates
-
investigating Sep 02, 2024, 07:35 AM UTC
We have detected a potential degradation of the Verify API in the AP-SOUTHEAST-1 region. We are actively investigating the issue and will provide an update shortly.
-
resolved Sep 02, 2024, 08:11 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2024, 06:36 AM UTC
- Resolved
- Aug 31, 2024, 07:43 AM UTC
- Duration
- 1h 7m
Affected: Singapore HealthcheckSydney Healthcheck
Timeline · 4 updates
-
investigating Aug 31, 2024, 06:36 AM UTC
We have detected a potential degradation of the Verify API in the AP-SOUTHEAST-2 region. We are actively investigating the issue and will provide an update shortly.
-
investigating Aug 31, 2024, 06:54 AM UTC
We are continuing to investigate this issue.
-
identified Aug 31, 2024, 07:34 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Aug 31, 2024, 07:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 30, 2024, 11:58 AM UTC
- Resolved
- Aug 30, 2024, 03:15 PM UTC
- Duration
- 3h 17m
Affected: Ireland Healthcheck
Timeline · 4 updates
-
investigating Aug 30, 2024, 11:58 AM UTC
We have detected a potential degradation of the Verify API in the Eu-west-1 region. We are actively investigating the issue and will provide an update shortly.
-
investigating Aug 30, 2024, 12:24 PM UTC
We are continuing to investigate this issue.
-
monitoring Aug 30, 2024, 03:05 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 30, 2024, 03:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2024, 12:10 AM UTC
- Resolved
- Jul 23, 2024, 01:13 AM UTC
- Duration
- 1h 3m
Affected: North Virginia HealthcheckOregon HealthcheckSingapore HealthcheckIreland HealthcheckOhio HealthcheckSydney Healthcheck
Timeline · 3 updates
-
investigating Jul 23, 2024, 12:10 AM UTC
We are currently investigating this issue.
-
monitoring Jul 23, 2024, 12:32 AM UTC
We are monitoring the results and we are seeing improvements.
-
resolved Jul 23, 2024, 01:13 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2024, 08:03 AM UTC
- Resolved
- Jul 22, 2024, 09:34 AM UTC
- Duration
- 1h 31m
Affected: North Virginia HealthcheckOregon HealthcheckSingapore HealthcheckIreland HealthcheckOhio HealthcheckSydney Healthcheck
Timeline · 4 updates
-
investigating Jul 22, 2024, 08:03 AM UTC
We are currently investigating this issue.
-
investigating Jul 22, 2024, 08:08 AM UTC
We are continuing to investigate this issue.
-
identified Jul 22, 2024, 09:22 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jul 22, 2024, 09:34 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2024, 08:46 AM UTC
- Resolved
- Jul 08, 2024, 12:49 PM UTC
- Duration
- 4h 3m
Affected: Sydney Healthcheck
Timeline · 6 updates
-
investigating Jul 08, 2024, 08:46 AM UTC
We have detected a potential degradation of the Verify API in the AP-SOUTHEAST-2 region. We are actively investigating the issue and will provide an update shortly.
-
investigating Jul 08, 2024, 09:17 AM UTC
We are experiencing higher latency and regional errors in AP-SOUTHEAST-1 and AP-SOUTHEAST-2.
-
investigating Jul 08, 2024, 10:21 AM UTC
We are continuing to investigate on the issue.
-
identified Jul 08, 2024, 11:30 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 08, 2024, 12:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 08, 2024, 12:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 05, 2024, 08:24 AM UTC
- Resolved
- Jul 05, 2024, 10:44 AM UTC
- Duration
- 2h 19m
Affected: Ireland Healthcheck
Timeline · 2 updates
-
investigating Jul 05, 2024, 09:58 AM UTC
We are currently investigating the issue.
-
resolved Jul 05, 2024, 10:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2024, 11:27 PM UTC
- Resolved
- Jun 26, 2024, 11:41 PM UTC
- Duration
- 1d
Affected: North Virginia HealthcheckOregon HealthcheckSingapore HealthcheckIreland HealthcheckOhio HealthcheckSydney Healthcheck
Timeline · 2 updates
-
identified Jun 26, 2024, 12:06 AM UTC
We have identified an outage in our Verify Endpoint.
-
resolved Jun 26, 2024, 12:08 AM UTC
This has been resolved.
Read the full incident report →
