Goldsky - Notice history

We are currently investigating this incident. New blockchain events may be slow to be indexed. There has been no data loss, and we will backfill all data.

We are continuing to work on a fix for this incident. This will lead to a temporary delay in data from some subgraphs arriving in mirror sinks. We will backfill the data, and nothing should be lost.

We are in the middle of a compute outage with AWS. We have opened a high urgency support ticket with them. We expect resolution soon. Degraded performance for Mirror.

During a routine database tuning operation at 8:02am Pacific Time, subgraph failure emails were sent out in error, and users looking at the dashboard might have seen an error status on the subgraph.

The subgraphs marked with errors were in fact healthy, and the error status would have disappeared after 5 minutes.

Subgraph indexing and querying was not degraded during that time.

Our error notification system will be tuned further to prevent this from happening again, sorry for the inconvenience!

Our RPC providers are having issues with the BSC nodes.

One of our database shards is experiencing high write volume, which is resulting in lag for mirror pipelines using Subgraph Sources for some subgraphs.

One of our database shards is undergoing heavy load, and certain subgraphs with larger tables will receive timeouts.

Users may see elevated timeout rates for some subgraphs.

We are currently investigating this incident. Some users are reporting that the GraphQL API for subgraphs has issues connecting to the database. Sometimes the dashboard is slow to load. Subgraph replication with mirror is lagging.

We have opened a chat with AWS to help investigate our database.

We have identified the root cause, measures are being applied but will take some time to complete.

Subgraph deployments are degraded. We've found the issue (runaway wantlist growth for IPFS) and are working on a fix.