Update - The incident has been resolved. However, the infrastructure provider incident corrupted some data in our cluster, so we’ve initiated a backfilling process.
During this time, customers in the Europe and Asia regions may notice elevated latency for these methods until backfilling is complete. We’ll fully resolve the incident once we’re back at full capacity.
Jun 25, 2026 - 12:52 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 25, 2026 - 10:42 UTC
Investigating - We are currently investigating an issue resulting in elevated error rates or latency for the getSignatureStatuses and getSignaturesForAddress methods in the Europe region.
Jun 25, 2026 - 10:30 UTC
Scheduled network upgrade for Injective Testnet at block #131,560,000, estimated for Jun 26, 2026 at 14:15 UTC. A brief blip or delay may occur during the upgrade, but impact is expected to be minimal. Posted on
Jun 25, 2026 - 13:06 UTC
Investigating -
We are currently investigating a network-wide stall on Base Mainnet at block 0x2d9784e. We’re working with the Base team to get more details on the issue.
Jun 25, 15:58 UTC
Resolved -
This incident has been resolved.
Jun 24, 18:05 UTC
Update -
We are continuing to investigate this issue.
Jun 24, 17:34 UTC
Investigating -
We are currently investigating an issue with our infrastructure provider, which may result in elevated error rates or latency for the getSignatureStatuses and getSignaturesForAddress methods.
Jun 24, 17:23 UTC
Resolved -
This incident has been resolved.
Jun 24, 17:39 UTC
Investigating -
We are investigating a network-wide stall on Abstract Mainnet at block #71,688,310 with no new blocks being produced.
Jun 24, 17:26 UTC
Resolved -
This incident has been resolved.
Jun 22, 15:58 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 22, 15:31 UTC
Update -
We are continuing to investigate this issue.
Jun 22, 15:09 UTC
Investigating -
We’re currently investigating an issue affecting eth_getLogs performance on networks with unlimited block ranges. Customers may see intermittent errors or increased latency, but this only affects blocks very close to the chain tip.
Jun 22, 13:27 UTC
Resolved -
This incident has been resolved.
Jun 22, 10:35 UTC
Update -
A fix is in place and eth_getProof data on Base is steadily catching up to the chain tip. We're monitoring as it converges. Other Base methods remain unaffected.
We will continue to share updates.
Jun 17, 11:09 UTC
Identified -
We're aware of an issue affecting eth_getProof requests on Base Mainnet for blocks beyond the most recent ~1,000 blocks. Affected requests may return an error indicating the requested block is outside the available proof window.
Recent blocks near the chain tip are unaffected. Our team has identified the cause and is actively working on a fix to restore historical proof coverage. We'll post an update as soon as service is fully restored.
Jun 16, 07:25 UTC
Resolved -
This incident has been resolved. The root cause was a service crash on our replay mechanism. This issue has been patched and functionality has been completely restored
Jun 20, 16:07 UTC
Investigating -
We are investigating a potential outage on our Solana gRPC service in US-East 1 region. We are re-routing gRPC connections to other regions to stabilize service. Users located in US-East may see delays in payload delivery following this. We are investigating for a route cause and will have more details shortly.
Jun 20, 01:10 UTC
Resolved -
The backfill has now finished, and the incident is fully resolved.
Jun 13, 17:30 UTC
Monitoring -
Between June 11 and June 12, Solana webhook delivery was disrupted. An internal service issue caused repeated disconnects from the Solana data stream over a ~24 hour window. During each disconnect, events were not recovered, resulting in missed webhook deliveries.
This has been resolved. Webhooks are delivering normally for all new events as of June 12 19:30 UTC.
If you have active Solana webhook subscriptions, you may notice two things:
- Missed events - Some events from the incident window (June 11 19:43 UTC through June 12 19:30 UTC) may not have been delivered. We are working to backfill these. - Possible duplicate events - As part of the backfill, some events from the incident window may be delivered more than once. We recommend handling deduplication on your end using the transaction signature if you haven't already.
- New events from June 12 19:30 UTC onwards are unaffected - deliveries are complete and accurate.
We will update the status once the backfill is completed. We're sorry for the disruption.
Jun 12, 20:14 UTC
Resolved -
This incident has been resolved.
Jun 12, 06:22 UTC
Update -
We managed to fix underlying issue with eth_getLogs, Websockets remain to be affected.
Jun 12, 05:30 UTC
Update -
HTTP requests are progressing again. Customers may still experience issues with eth_getLogs and WebSockets. We are actively investigating and will provide further updates shortly.
Jun 12, 05:25 UTC
Investigating -
We are currently investigating Hyperliquid Mainnet stall at block 37597796.
Jun 12, 05:05 UTC