Goldsky - Notice history

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.

We observed increased latency on subgraph API endpoints as a result of a database failover between 9:45 and 9:58 AM Pacific time.

The systems are now operating normally.

Not all customers are affected, and no data has been lost, we've identified the issue and are working to resolve it.

A portion of subgraphs have their queries timing out. Our team is mitigating the issue currently.

Subgraph pipeline ingestion is back online

We are currently investigating an outage with an upstream provider. This will affect pipeline creation and operation of some pipelines. There may be lag in data arriving, but no data has been lost.