The Graph
Rinkeby: Block ingestor lagging behind
Update - [Comment from Opsgenie]leo acknowledged alert: "Rinkeby: Block ingestor lagging behind"
Jun 23, 15:25 UTC
Investigating - We are currently investigating this issue.
Jun 23, 14:28 UTC
Problems with callHandlers on Ropsten
Investigating - We are currently seeing problems with callHandlers on Ropsten. Given the uncertainty about the support of Ethereum testnets we highly advise developers to migrate their contracts and subgraphs to Goerli as soon as possible.

Affected subgraphs show the following logs:

```
Trying again after trace_filter RPC call for block range: [12326064..12326064] failed (attempt #10) with result Err(RPC error: Error { code: ServerError(-32000), message: "could not find block 0000000000000000000000000000000000000000000000000000000000000000 12326064", data: None } Caused by: Server error: could not find block 0000000000000000000000000000000000000000000000000000000000000000 12326064), component: BlockStream
```

And

```
Trying again after trace_filter RPC call for block range: [12326066..12326066] failed (attempt #10) with result Err(RPC error: Error { code: InternalError, message: "hash 4dd5bd7e4dc3a95da925384c3bc45efcd37f3c75d6f2d99f7f2d34ca9a8c99e8 is not currently canonical", data: None } Caused by: Internal error: hash 4dd5bd7e4dc3a95da925384c3bc45efcd37f3c75d6f2d99f7f2d34ca9a8c99e8 is not currently canonical), component: BlockStream
```
Jun 3, 01:48 UTC
Aurora Chain Malfunction - Found no transaction for event
Investigating - failed to process trigger: block #1234.. (0x8a70…09de), transaction....: Found no transaction for event
Might occur while syncing subgraph on aurora chain. This is an rpc issue reported to the aurora team and we are working with them to get this resolved.
May 23, 14:01 UTC
Slow indexing on NEAR
Update - We are still working on this issue, the original fix did not return indexing performance to normal
Mar 17, 18:10 UTC
Identified - Block processing time has been degraded, some fixes have been implemented but full resolution is ongoing.
Mar 16, 16:08 UTC

About This Site

Status, incident and maintenance information for The Graph.
Use the RSS feed together with https://zapier.com/apps/rss to have updates sent straight to Slack or Discord.

Uptime over the past 90 days. View historical uptime.
Network - Gateway ? Operational
90 days ago
99.98 % uptime
Today
Network - Explorer ? Operational
90 days ago
100.0 % uptime
Today
Network - Subgraph Studio ? Operational
90 days ago
99.98 % uptime
Today
Network - Network Subgraph ? Operational
90 days ago
99.89 % uptime
Today
Hosted Service - Queries ? Operational
90 days ago
99.98 % uptime
Today
Hosted Service - Subgraph Health Operational
90 days ago
100.0 % uptime
Today
Hosted Service - Indexing Partial Outage
90 days ago
98.78 % uptime
Today
Mainnet Operational
90 days ago
99.95 % uptime
Today
Kovan Operational
90 days ago
99.99 % uptime
Today
Rinkeby Partial Outage
90 days ago
98.61 % uptime
Today
Ropsten Operational
90 days ago
99.99 % uptime
Today
Goerli Operational
90 days ago
99.33 % uptime
Today
POA Core Operational
90 days ago
99.94 % uptime
Today
POA Sokol Operational
90 days ago
99.93 % uptime
Today
xDai Operational
90 days ago
81.24 % uptime
Today
Polygon (Matic) Operational
90 days ago
99.99 % uptime
Today
Mumbai Operational
90 days ago
99.9 % uptime
Today
Fantom Operational
90 days ago
99.99 % uptime
Today
BSC Operational
90 days ago
99.96 % uptime
Today
BSC Chapel Operational
90 days ago
93.07 % uptime
Today
Clover Operational
90 days ago
100.0 % uptime
Today
Avalanche Operational
90 days ago
99.99 % uptime
Today
Avalanche Fuji Operational
90 days ago
99.99 % uptime
Today
Celo Operational
90 days ago
100.0 % uptime
Today
Celo Alfajores Operational
90 days ago
100.0 % uptime
Today
Fuse Operational
90 days ago
97.7 % uptime
Today
Moonbeam Operational
90 days ago
100.0 % uptime
Today
Arbitrum One Operational
90 days ago
99.99 % uptime
Today
Arbitrum Testnet (on Rinkeby) Operational
90 days ago
99.93 % uptime
Today
Optimism Operational
90 days ago
100.0 % uptime
Today
Optimism Testnet (on Kovan) Operational
90 days ago
100.0 % uptime
Today
Moonriver Operational
90 days ago
99.99 % uptime
Today
NEAR Degraded Performance
Hosted Service - Miscellaneous Operational
90 days ago
99.9 % uptime
Today
Deployments ? Operational
90 days ago
99.98 % uptime
Today
IPFS Operational
90 days ago
99.98 % uptime
Today
Subgraph Logs ? Operational
90 days ago
99.98 % uptime
Today
Explorer ? Operational
90 days ago
99.98 % uptime
Today
thegraph.com ? Operational
90 days ago
99.57 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
Network: Gateway (Response Time)
Fetching
Network Subgraph (Test Query)
Fetching
Network: Explorer (Response Time)
Fetching
Past Incidents
Jun 27, 2022

No incidents reported today.

Jun 26, 2022
Goerli: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 26, 10:58 UTC
Investigating - We are currently investigating this issue.
Jun 25, 23:22 UTC
Jun 25, 2022
Jun 24, 2022

No incidents reported.

Jun 23, 2022
Goerli: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 23, 18:11 UTC
Update - [Comment from Opsgenie]leo acknowledged alert: "Goerli: Block ingestor lagging behind"
Jun 23, 17:31 UTC
Investigating - We are currently investigating this issue.
Jun 23, 17:12 UTC
Moonriver: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 23, 17:52 UTC
Investigating - We are currently investigating this issue.
Jun 23, 17:32 UTC
Mainnet: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 23, 16:58 UTC
Update - [Comment from Opsgenie]leo acknowledged alert: "Mainnet: Block ingestor lagging behind"
Jun 23, 15:25 UTC
Investigating - We are currently investigating this issue.
Jun 23, 14:31 UTC
Jun 22, 2022

No incidents reported.

Jun 21, 2022
Gnosis Chain not indexing
Resolved - We were able to stabilise the JSON RPC endpoint and subgraphs on Gnosis Chain should now index as expected. Feel free to reach out in thegraph.com/discord if you still experience problems with Gnosis Chain.
Jun 21, 14:37 UTC
Investigating - Subgraphs on Gnosis Chain do not receive new blocks. We are working with the Gnosis Chain team to find a solution.
Jun 5, 02:24 UTC
Mumbai: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 21, 07:43 UTC
Investigating - We are currently investigating this issue.
Jun 21, 07:39 UTC
Polygon (Matic): Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 21, 07:42 UTC
Investigating - We are currently investigating this issue.
Jun 21, 07:39 UTC
Avalanche: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 21, 07:41 UTC
Investigating - We are currently investigating this issue.
Jun 21, 07:39 UTC
Arbitrum One: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 21, 07:40 UTC
Investigating - We are currently investigating this issue.
Jun 21, 07:33 UTC
Network: Gateway has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:34 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - string Ready to roll! not found on https://gateway.network.thegraph.com:443/ - 1443 bytes in 15.296 second response time

time=15.295898s;;;0.000000 size=1443B;;;0
Jun 21, 07:28 UTC
API: IPFS has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:22 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 323 bytes in 0.041 second response time

time=0.040784s;;;0.000000 size=323B;;;0
Jun 21, 06:32 UTC
API: Deploy has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:22 UTC
Investigating - CRITICAL - STEP 2: Expected status code 200 but server returned 500.

time=0.057796
Jun 21, 06:36 UTC
thegraph.com: Web Server HTTPS has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:22 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 323 bytes in 0.045 second response time

time=0.044591s;;;0.000000 size=323B;;;0
Jun 21, 06:39 UTC
API: Subgraph Logs has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:21 UTC
Investigating - CRITICAL - STEP 2: Expected status code 200 but server returned 500.

time=0.173488
Jun 21, 06:36 UTC
API: Explorer Query has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:21 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - string data:{featuredSubgraphs... not found on https://api.thegraph.com:443/explorer/graphql?query=%7BfeaturedSubgraphs%7Bid%7D%7D - 967 bytes in 0.046 second response time

time=0.045729s;;;0.000000 size=967B;;;0
Jun 21, 06:30 UTC
Network: Gateway has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:21 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 522 - string Ready to roll! not found on https://gateway.network.thegraph.com:443/ - 8861 bytes in 30.624 second response time

time=30.623926s;;;0.000000 size=8861B;;;0
Jun 21, 06:33 UTC
Studio API: Deployment Router has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:20 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 522 - 655 bytes in 30.813 second response time

time=30.812887s;;;0.000000;40.000000 size=655B;;;0
Jun 21, 06:37 UTC
Studio API: GraphQL has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:20 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 323 bytes in 0.071 second response time

time=0.071437s;;;0.000000;40.000000 size=323B;;;0
Jun 21, 06:32 UTC
Studio API: Query Proxy has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:20 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 323 bytes in 0.047 second response time

time=0.047072s;;;0.000000;40.000000 size=323B;;;0
Jun 21, 06:38 UTC
API: Query Nodes has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:20 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 962 bytes in 0.058 second response time

time=0.058227s;;;0.000000 size=962B;;;0
Jun 21, 06:31 UTC
Gateway: Network Deployment has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:20 UTC
Investigating - CRITICAL - STEP 2: Expected status code 200 but server returned 500.

time=0.181051
Jun 21, 06:36 UTC
API: Explorer OAuth has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:20 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 962 bytes in 0.098 second response time

time=0.098306s;;;0.000000 size=962B;;;0
Jun 21, 06:31 UTC
thegraph.com: Hosted Service Explorer has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:19 UTC
Investigating - HTTP CRITICAL: HTTP/1.1 522 - 1369 bytes in 30.878 second response time

time=30.877869s;;;0.000000 size=1369B;;;0
Jun 21, 06:33 UTC
Network: Subgraph Studio has failed an uptime check
Resolved - This incident has been resolved.
Jun 21, 07:19 UTC
Investigating - HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 40001 milliseconds with 0 bytes received
Jun 21, 06:34 UTC
Jun 20, 2022

No incidents reported.

Jun 19, 2022

No incidents reported.

Jun 18, 2022
Goerli: Block ingestor lagging behind
Resolved - This incident has been resolved.
Jun 18, 21:48 UTC
Update - [Comment from Opsgenie]leo acknowledged alert: "Goerli: Block ingestor lagging behind"
Jun 18, 21:08 UTC
Investigating - We are currently investigating this issue.
Jun 18, 20:50 UTC
Jun 17, 2022

No incidents reported.

Jun 16, 2022

No incidents reported.

Jun 15, 2022

No incidents reported.

Jun 14, 2022

No incidents reported.

Jun 13, 2022

No incidents reported.

← Incident History Powered by Atlassian Statuspage