Codex Outage History

Started Sep 10, 2026, 09:06 AM UTC· resolved Sep 10, 2026, 02:24 PM UTC

1. investigating Sep 10, 2026, 09:06 AM UTC

   We're experiencing latency with BNB token balances processing.

2. identified Sep 10, 2026, 09:16 AM UTC

   Wallet balances and holder counts are lagging. We are working on a fix.

3. identified Sep 10, 2026, 10:40 AM UTC

   Wallet balances and holders delayed for BNB. We are continuing to work on a remedy.

4. monitoring Sep 10, 2026, 11:58 AM UTC

   We've released some changes to help catch up. We are monitoring and will update as needed.

5. monitoring Sep 10, 2026, 12:59 PM UTC

   The released fix is working as intended. We are processing the backlog of data. Will continue to monitor and update when resolved.

6. resolved Sep 10, 2026, 02:24 PM UTC

   BNB wallet balances and holder counts are now up-to-date.

Read the full incident report →

Started Sep 08, 2026, 03:20 PM UTC· resolved Sep 08, 2026, 04:29 PM UTC

1. investigating Sep 08, 2026, 03:20 PM UTC

   We're experiencing delayed pricing for Solana.

2. identified Sep 08, 2026, 03:42 PM UTC

   We've identified the issue causing delays to the Solana token and are working on a fix.

3. resolved Sep 08, 2026, 04:29 PM UTC

   We've put a fix in place and the delayed data has now recovered.

Read the full incident report →

Started Sep 01, 2026, 05:31 PM UTC· resolved Sep 03, 2026, 04:56 PM UTC

1. identified Sep 01, 2026, 05:31 PM UTC

   Multiple of our RPC providers for robinhood nodes have degraded latencies, causing indexing to slow.

2. resolved Sep 03, 2026, 04:56 PM UTC

   This was resolved

Read the full incident report →

Started Sep 01, 2026, 05:44 AM UTC· resolved Sep 01, 2026, 06:07 AM UTC

1. investigating Sep 01, 2026, 05:44 AM UTC

   Wallet balance calculations are delayed for BNB

2. monitoring Sep 01, 2026, 05:58 AM UTC

   We've identified the issue and put a fix in place. We will monitor recovery.

3. resolved Sep 01, 2026, 06:07 AM UTC

   System has recovered. BNB wallet balance data is up-to-date.

Read the full incident report →

Started Aug 31, 2026, 03:28 PM UTC· resolved Aug 31, 2026, 03:33 PM UTC

1. identified Aug 31, 2026, 03:28 PM UTC

   Robinhood network is experiencing delays, but recovering.

2. resolved Aug 31, 2026, 03:33 PM UTC

   Robinhood network data is caught up

Read the full incident report →

Started Aug 30, 2026, 02:38 PM UTC· resolved Aug 31, 2026, 03:00 PM UTC

1. monitoring Aug 30, 2026, 02:38 PM UTC

   Cronos Network has been halted. When activity resumes, we will monitor our system's response. Historical data is still available via Codex API. More information here: https://x.com/CronosNetwork

2. resolved Aug 31, 2026, 03:00 PM UTC

   Cronos network has resumed

Read the full incident report →

Started Aug 29, 2026, 03:52 PM UTC· resolved Sep 03, 2026, 04:57 PM UTC

1. identified Aug 29, 2026, 03:52 PM UTC

   Fogo network was intentionally halted as a security measure. Historical data is still available via Codex API. More information here https://x.com/fogo

2. monitoring Aug 29, 2026, 11:51 PM UTC

   When Fogo network activity resumes, we will monitor our system's response.

3. resolved Sep 03, 2026, 04:57 PM UTC

   We are following the chain and will provide updates as we receive them.

Read the full incident report →

Started Aug 17, 2026, 06:59 AM UTC· resolved Aug 17, 2026, 07:58 AM UTC

1. investigating Aug 17, 2026, 06:59 AM UTC

   Our upstream rpc nodes for BNB have fallen behind the head. We are investigating the issue. Other systems than balances are unaffected.

2. monitoring Aug 17, 2026, 07:25 AM UTC

   Fix implemented. Backfilling and catching up now.

3. resolved Aug 17, 2026, 07:58 AM UTC

   Incident has been resolved

Read the full incident report →

Started Aug 12, 2026, 09:00 PM UTC· resolved Aug 12, 2026, 09:23 PM UTC

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.

Read the full incident report →

Started Aug 11, 2026, 06:12 PM UTC· resolved Aug 11, 2026, 06:15 PM UTC

1. identified Aug 11, 2026, 06:12 PM UTC

   Memory spike in our router is causing failed requests. We're working on a fix.

2. resolved Aug 11, 2026, 06:15 PM UTC

Read the full incident report →

Started Aug 11, 2026, 06:11 PM UTC· resolved Aug 11, 2026, 06:53 PM UTC

1. identified Aug 11, 2026, 06:11 PM UTC

   Some queries containing balances have higher latency than normal latency. We have identified the issue and are working on a solution

2. resolved Aug 11, 2026, 06:53 PM UTC

   Everything is back to normal. We identified an inefficient path in a field resolver that when used at high scale could degrade the request timing to the point of timing out the origin.

Read the full incident report →

Started Aug 11, 2026, 04:10 PM UTC· resolved Aug 11, 2026, 04:14 PM UTC

1. investigating Aug 11, 2026, 04:10 PM UTC

   Our upstream data providers for robinhood chain are all lagging behind the chain

2. resolved Aug 11, 2026, 04:14 PM UTC

   We are seeing recovery after one of the providers came back up to speed

Read the full incident report →

Started Aug 04, 2026, 07:32 AM UTC· resolved Aug 04, 2026, 07:45 AM UTC

1. investigating Aug 04, 2026, 07:32 AM UTC

   We have observed a slowdown in our processing of BNB Smart Chain data. Engineers are investigating.

2. resolved Aug 04, 2026, 07:45 AM UTC

   BSC is back up to date after a large influx of ERC20 data.

Read the full incident report →

Started Jul 31, 2026, 05:57 AM UTC· resolved Jul 31, 2026, 06:09 AM UTC

1. investigating Jul 31, 2026, 05:57 AM UTC

   A sudden spike in unusual activity has degraded our services, causing significant latency in GraphQL endpoints. The team is investigating.

2. resolved Jul 31, 2026, 06:09 AM UTC

   The burst of unusual activity abated; additional resources were deployed to help services swiftly return to nominal.

Read the full incident report →

Started Jul 26, 2026, 10:33 PM UTC· resolved Jul 26, 2026, 11:01 PM UTC

1. investigating Jul 26, 2026, 10:33 PM UTC

   Elevated reponse time have been observed

2. resolved Jul 26, 2026, 11:01 PM UTC

   resposne times have returned to normal

Read the full incident report →

Started Jul 23, 2026, 05:49 PM UTC· resolved Jul 23, 2026, 06:27 PM UTC

1. investigating Jul 23, 2026, 05:49 PM UTC

   GraphQL/API performance suddenly degraded at 10:49AM PT. The team is investigating and will update as soon as a cause is found.

2. identified Jul 23, 2026, 06:10 PM UTC

   An unusual surge of requests led to a degradation in our GraphQL/API performance. The affected services are recovering, but have not yet returned to nominal. We are continuing our investigation.

3. resolved Jul 23, 2026, 06:27 PM UTC

   A burst of unusual activity caused nearly an hour of degraded endpoint performance. The team's efforts to mitigate the impact has allowed services to recover. We continue to investigate avenues to harden our services to prevent similar issues from occurring in future.

Read the full incident report →