Castle Outage History

Castle had 4 outages in the last 2 years totaling 12h 9m of downtime — averaging 0.2 incidents per month.

There were 4 Castle outages since June 27, 2025 totaling 12h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.castle.io

Minor May 8, 2026

Degraded performance and latency due to upstream provider issues

Detected by Pingoru: May 08, 2026, 04:31 AM UTC
Resolved: May 08, 2026, 04:41 PM UTC
Duration: 12h 9m

Affected: Risk and Filter APIsLog APILegacy APIs

Timeline · 3 updates

identified May 08, 2026, 04:31 AM UTC

We are observing an elevated number of errors and slightly higher latency than normal due to upstream provider issues in AWS US-EAST-1 (us-east-1a). We are continuing to monitor the situation. https://health.aws.amazon.com/health/status
monitoring May 08, 2026, 04:56 AM UTC

A fix has been implemented and we are monitoring the results.
resolved May 08, 2026, 04:41 PM UTC

This incident has been resolved.

Read the full incident report →

Notice March 17, 2026

Risk and Filter API Outage

Detected by Pingoru: Mar 17, 2026, 09:56 AM UTC
Resolved: Mar 17, 2026, 09:56 AM UTC
Duration: —

Affected: Risk and Filter APIs

Timeline · 1 update

resolved Mar 17, 2026, 09:56 AM UTC

We experienced an issue with downsizing one of our underlying nodes that affected the 25% of our traffic.

Read the full incident report →

Notice January 22, 2026

API Outage

Detected by Pingoru: Jan 22, 2026, 11:01 PM UTC
Resolved: Jan 22, 2026, 11:01 PM UTC
Duration: —

Affected: Risk and Filter APIs

Timeline · 1 update

resolved Jan 22, 2026, 11:01 PM UTC

This incident has been resolved.

Read the full incident report →

Minor June 27, 2025

We observe a slight increase in 5xx errors due to transient backend issues.

Detected by Pingoru: Jun 27, 2025, 07:30 AM UTC
Resolved: Jun 27, 2025, 06:52 AM UTC
Duration: —

Timeline · 1 update

resolved Jun 27, 2025, 07:18 AM UTC

We’re currently experiencing an elevated number of errors returned by our API. Our team has identified the root cause and is actively working on a fix. We apologize for any inconvenience and will provide updates as soon as more information becomes available.

Read the full incident report →