Castle incident

Degraded performance and latency due to upstream provider issues

Resolved after 12 hours 9 minutes, affecting Risk and Filter APIs and Log API and 1 more, on May 8, 2026.

monitoring May 08, 2026, 04:56 AM UTC

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

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

Affected components

Risk and Filter APIsLog APILegacy APIs

Update timeline

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

  2. monitoring May 08, 2026, 04:56 AM UTC

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

  3. resolved May 08, 2026, 04:41 PM UTC

    This incident has been resolved.

Your product runs on more than Castle

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →