Previous incidents

On October 9th, we experienced a delay in our Binance Chain indexer, which fluctuated between 5–60 minutes behind real-time data for a period of roughly 4 hours. The issue was caused by an unexpected spike in network activity, and our systems did not scale quickly enough to handle the load.

As of 17:00 CET on October 9th, we implemented measures to improve our automatic scaling during traffic surges. Since then, performance has been stable and real-time indexing has fully recovered.

We cont...

A surge of malicious traffic caused intermittent disruptions to Web3API and Streams for approximately 20 minutes. The issue was mitigated by applying rate limits, scaling affected systems, and implementing additional safeguards.

All services are now fully restored and stable, and we continue to monitor closely.

We have identified the issue and a fix was deployed. All endpoints are now stable

We have identified the issue and pushed a fix. All services are back in a stable state.

Root cause: an internal routing configuration was mistakenly rolled back during an internal upgrade. This has been corrected and the endpoint is fully operational again.

We’re adding safeguards to prevent this from happening in the future.

All services are now back online and running in real-time now. We continue to monitor the system to ensure service stability.

All services are now running in real-time now.

All services are now running in real-time now.

The issue was resolved and all the data is back in real-time.

The root cause has been identified and fixed. The Ethereum data is now catching up and should be at real time soon.