1. Current Network Status
Published 8/5/2026, 11:02:23 PM
The Graph's decentralized indexing infrastructure is not currently down, and there is no evidence of a month-long protocol-wide outage as of August 5, 2026. The network is operational across 40+ chains, though it has faced specific regional degradations and a brief oracle-related incident in late July.
The perception that decentralized indexing is "broken" likely stems from a 20-hour outage on July 20, 2026, and the ongoing transition to more complex decentralized oracle architectures which have introduced localized performance issues.
1. Current Network Status
As of August 5, 2026, major monitoring services report The Graph as Operational [Source: https://statusgator.com/services/the-graph]. While the network is functional, it has experienced several significant incidents in 2026 that may contribute to the user's query:
| Incident | Date (2026) | Duration | Status |
|---|---|---|---|
| Oracle Reconciliation Outage | July 20 | ~20 Hours | Resolved [Source: https://status.thegraph.com/history] |
| Gnosis Indexing Degradation | Jan 21 – Jan 30 | 9 Days | Resolved [Contested: Jan 30 resolution date not independently confirmed] |
| Etherlink-Sepolia Lag | Dec 23 – Jan 21 | 29 Days | Resolved [Note: not independently confirmed] |
2. The "Oracle Outage" Explained
The most recent significant disruption occurred on July 20, 2026, lasting approximately 19 hours and 47 minutes. This was specifically a Subgraph Availability Oracle reconciliation outage [Source: https://status.thegraph.com/history].
- Root Cause: The failure involved the process that ensures subgraphs are correctly indexed across the decentralized network.
- Centralization Concerns: Core developers have previously noted that the current Epoch Block Oracle (EBO) system has historically relied on a single operator on Arbitrum One, creating a potential point of failure [Note: not independently confirmed].
- The Solution: The protocol is actively moving toward GIP-0080 (Optimistic EBO) to further decentralize this oracle and remove single-operator dependencies.
3. Is Decentralized Indexing "Broken"?
Decentralized indexing is functional but undergoing a major "quality of service" transition. Two factors are often misinterpreted as the network being "broken":
- Indexer Ineligibility: As of late July 2026, approximately 50.5% of indexers (49 out of 97) were flagged as "ineligible" by the Rewards Eligibility Oracle (REO) [Source: https://graphtools.pro/reo]. This is not a network failure but a strict enforcement of performance standards to ensure query reliability.
- Chain-Specific Lag: While the protocol is up, specific chains like Gnosis and Polygon frequently experience "block ingestor lagging." These are often localized to the indexers supporting those specific chains rather than a total protocol failure.
Conclusion
The Graph is not experiencing a month-long outage. The network is operational, but the transition from the centralized "Hosted Service" (deprecated in early 2026) to the decentralized network has made localized chain lags and oracle reconciliation issues more visible to end-users. The "broken" sentiment is likely a reaction to the 50.5% indexer ineligibility rate and the 20-hour July outage, rather than a total loss of functionality.