Goldsky - Notice history

This incident has been resolved. Our API endpoint suffered an outage as a result of a bad deploy which interfered with networking.

This incident has been resolved. Data will automatically be backfilled.

Only chain ingestion was lagging, and mirror pipelines using subgraph sources were not affected.

This incident has been resolved. There was an infinite loop eating up resources. A fix has been deployed.

Our ingestion system has recovered and all subgraph sourced mirror data for the affected subgraphs have been backfilled. No data was lost.

We've recovered the failing system and are currently backfilling data.

Recovery has started. For the next few minutes:

• Consumers might experience loss of data freshness.

• Pipelines might not start.

This incident has been resolved.

A database read replica was locked due to an automated maintenance system. We have implemented an immediate fix and are investigating the underlying causes to prevent future issues like this.

We've opened a support ticket with AWS. One of our database shards is under high load and our proxies are showing a high number of pending transactions.

This incident has been resolved. Arweave search and indexing is back to normal, no data has been lost.

BSC indexing has resolved

We have found a new RPC provider that is not having issues. Status seems resolved. We will be monitoring for further issues.

DB load is back to normal. Mirror pipelines using subgraph sources should no longer be lagging.

Subgraph indexing was not affected, but replication into mirror pipelines may have seen lag over this period of time.