Is Arkose Labs Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We have detected a potential outage of the Arkose Services Globally. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

Arkose Labs Engineering is still actively investigating the Platform issue.We are working diligently to resolve this and will provide another update soon.

Arkose Labs Engineering is currently conducting an active investigation to resolve the ongoing Platform issue. Few customers may experience temporary increases in load times or encounter intermittent errors. We are working diligently to minimize disruption and restore normal service as quickly as possible

We are continuing to investigate this issue.

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.

This incident has been resolved.

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.

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.

This incident has been resolved.

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.

We observed a brief period of latency in our AP-Southeast-2 (Sydney) region for Arkose services. The latency has passed and we are performing an investigation into root cause.

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.

This incident has been resolved.

At this time our observability is showing increased latency in the Sydney region (AP-Southeast-2). We are actively investigating this issue. At this time this issue does not impact any other regions.

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.

This incident has been resolved.

We have detected a potential degradation of Arkose Services. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

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.

This incident has been resolved.

We have detected a potential degradation of Arkose Services in the US-EAST-1 region. We are actively investigating the issue and will provide an update shortly.

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.

The issue has been identified and a fix is being implemented.

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.

We are currently investigating an issue where some customers are seeing increased errors and latency in some regional endpoints.

This incident has been resolved.

We believe we have identified the issue and are validating resolution.

We are currently investigating an issue with Arkose Labs Puzzles. We will post an update as soon as possible.

This incident has been resolved.

We are continuing to investigate this issue.

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

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.

We have seen recovery across regions and all Arkose Services are now stable.

We have implemented changes to mitigate the issue and are seeing some recovery. We are monitoring at this time to ensure the issue is resolved.

We have identified an issue in our environment and are working to mitigate the situation. Next update by August 30, 2024 19:00 UTC

We are continuing to investigate this issue.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

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.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are monitoring the results and we are seeing improvements.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We have detected a potential degradation of the Verify API in the US-EAST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-EAST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-EAST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate on the issue.

We are experiencing higher latency and regional errors in AP-SOUTHEAST-1 and AP-SOUTHEAST-2.

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.

This incident has been resolved.

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.

This incident has been resolved.

We are currently investigating the issue.

This incident has been resolved.

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.

This has been resolved.

We have identified an outage in our Verify Endpoint.

This incident has been resolved.

We have released a fix to address API_REQUEST_ERRORs (4xx’s errors), and we have observed improvements, returning to normal and continue monitoring.

We have narrowed down the issue and working towards a fix within our minor environments and will provide an update in 3 hours.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Initial investigation indicates that the increased HTTP 500 errors is stemming from a database migration that was completed at approximately 4:45 AM UTC on Thursday, April 11th. Our metrics show that the error rate is approximately 0.1% which is elevated compared to prior to the migration. We are continuing to investigate.

We are continuing to investigate this issue

We have detected a potential degradation in US-EAST-1 and EU-WEST-1 region. Users may experience increase in 5xx errors. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We have detected a potential degradation of Setup session in US-EAST-1 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-WEST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-WEST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-WEST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

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.

This incident has been resolved.

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.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-EAST-1 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-EAST-1 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue with increased challenge rates.

At this time services have been restored. We are continuing to investigate root cause.

We have detected a potential degradation of the Verify API in the US-EAST-1 region. We are actively investigating the issue and will provide an update shortly.

At this time services have been restored. We are continuing to investigate root cause.

We are currently investigating an issue with increased latency and errors in the the North Virginia and Oregon regions.

This incident has been resolved.

We have detected a potential degradation of the Verify API in the US-WEST-2 region. We are actively investigating the issue and will provide an update shortly.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

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.

This incident has been resolved.

Traffic has been re-routed accordingly to avoid impact across the region.

A fix has been implemented and we are monitoring results.

The issue has been identified and is due to an outage on AWS US-EAST-1 region.

We have detected a potential degradation of the Verify API in the US-EAST-1 region. We are actively investigating the issue and will provide an update shortly.