Goldsky - Notice history

A misconfigured internal network caused services to lose communication. We've rolled back the change and affected pipelines should auto-restore.

Our database experienced temporary unexpected load but the cause has been identified and this incident has been resolved.

We implemented a fix and are currently monitoring the result. The problem is improving slowly. We are looking for how to accelerate the rate of recovery.

Incedent has been resolved:
Subgraph support for HyperEVM was temporarily disrupted for ~1 hour due to some of the nodes on our load balancer not returning correct blocks data. This issue took a bit longer than expected to get resolved as the new node configuration seemingly fixed the problem but it turned out to be a false signal; we identified it and applied a proper configuration to get it resolved.
As a countermeasure, we've also added new network-wide monitors to proactively notify us if this specific problem shall occur in the future.