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

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

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

This was resolved

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

Robinhood network data is caught up

Cronos network has resumed

Incident has been resolved

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.

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.

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

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

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

resposne times have returned to normal

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.

We have finished our monitoring phase, the outage is now fully resolved.

Robinhood network has returned to a healthy state.

The Robinhood Chain is experiencing a known issue where delayed transactions can be incorrectly filtered, causing downstream RPC failure modes. The Robinhood team is aware of the issue and is working on a fix.

We have deployed a temporary workaround that will dramatically reduce the impact on our indexing.

Services are back to normal.

Unusual spikes of network activity on Base and Solana caused a temporary delay in the freshness of our published data. Underlying problem was found and has been fixed.

Robinhood balances are up to date.

All systems have recovered

Base network is unstuck and everything is caught up.