ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains Status
ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains is experiencing degraded performance with some services running slower than normal.
Degraded1
Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains
Last checked Jul 22, 2026 2:23 AM UTC from ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains's official status page
ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains Status
Part of ENSNode
Degraded
Last updated Jul 22, 2026 2:23 AM UTC•4 sub-components
Service Health — Last 15 days
Availability
100.0%
Last Incident
None
No recent incidents
Incidents
0
All systems operational
Avg Resolution
—
No incidents to measure
Availability is averaged equally across all monitored components. Each component is tracked independently to give you a clear picture of overall service reliability.
Stay ahead of outages
Get Notified When ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains Is Back Up
Get instant alerts when ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains recovers. Sign up for free and never miss an outage.
Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains Sub-Components
4 sub-components with real-time status monitoring
ENSNode Alpha
Operational
ENSNode Alpha Sepolia
Degraded
ENSNode Mainnet
Degraded
ENSNode Sepolia
Degraded
Frequently Asked Questions About ENSNode Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains
Common questions about monitoring Worst-case indexing distance within an acceptable distance from the current 'tip' of all indexed chains and understanding component status