Codex incident

Degraded FilterTokens API performance

Resolved after 23 minutes, affecting GraphQL Api, on August 12, 2026.

resolved Aug 12, 2026, 09:23 PM UTC

Codex API services are fully operational. We are working with Amazon Web Services to determine causes and future mitigations of their degraded services we experienced.

Started
Aug 12, 2026, 09:00 PM UTC
Resolved
Aug 12, 2026, 09:23 PM UTC
Duration
23m
Detected by Pingoru
Aug 12, 2026, 09:00 PM UTC

Affected components

GraphQL Api

Update timeline

  1. investigating Aug 12, 2026, 09:00 PM UTC

    We are currently investigating degraded performance within the FilterTokens API endpoint. Consumers may experience degraded pair aggregate data while the team is working on a resolution.

  2. identified Aug 12, 2026, 09:09 PM UTC

    We have identified the source of the degradation to be Amazon Web Service's (AWS) internal networking timeouts. We have escalated support with AWS to work out a resolution as quickly as possible.

  3. monitoring Aug 12, 2026, 09:14 PM UTC

    We have implemented a workaround, while we continue to monitor the Amazon Web Services degradation. Codex API services are returning to full operation.

  4. resolved Aug 12, 2026, 09:23 PM UTC

    Codex API services are fully operational. We are working with Amazon Web Services to determine causes and future mitigations of their degraded services we experienced.

Your product runs on more than Codex

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 →