Home
/
Status
/
Service
Blockchain platform for fast, secure, and fair transactions.
Source
auto
Category
Analytics
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Degraded
Checked 48m ago
58
Components
0
Active incidents
4
Maintenance
0%
90d uptime
Hedera mainnet is still upgrading
May 20, 5:53 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 25 of 58 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Hedera Mainnet (v0.74.2) | Individual Nodes This status informs uptime of individual nodes which constitute the Hedera mainnet. Less than 1/3 of Hedera network nodes can go offline before affecting the Hedera mainnet in its entirety. | Partial Outage | Group | Not recorded |
Hedera Mirror Node Mainnet (v0.156.0) | Operational | Group | Not recorded |
Hedera Testnet (v0.74.0) | Individual Nodes This status informs uptime of individual nodes which constitute the Hedera testnet. Less than 1/3 of Hedera network nodes can go offline before affecting the Hedera testnet in its entirety. | Operational | Group | Not recorded |
Hedera Mirror Node Testnet (v0.156.0) | Operational | Group | Not recorded |
Hedera Previewnet (v0.75.0-rc.6) | Individual Nodes This status informs uptime of individual nodes which constitute the Hedera previewnet. Less than 1/3 of Hedera network nodes can go offline before affecting the Hedera previewnet in its entirety. | Operational | Group | Not recorded |
Hedera Mirror Node Previewnet (v0.157.0-rc2) | Operational | Group | Not recorded |
Hedera Mainnet (v0.74.2) | Network Uptime This status informs uptime of the Hedera mainnet (beta) in its entirety. The Hedera mainnet is online and fully functional, so long as 2/3 of its nodes are online and contributing to consensus. | Operational | Component | 6/20/2026 |
Mirror Node REST API Mainnet | Operational | Component | Not recorded |
Mirror Node REST API Previewnet | Operational | Component | Not recorded |
Node 0 (account 0.0.3) | Operational | Component | Not recorded |
Node 0 (account 0.0.3) | Operational | Component | Not recorded |
Node 0 (account 0.0.3) | Hosted by LG | Singapore | Operational | Component | 6/20/2026 |
Mirror Node HCS gRPC Mainnet | Operational | Component | Not recorded |
Mirror Node HCS gRPC Previewnet | Operational | Component | Not recorded |
Mirror Node REST API Testnet | Operational | Component | Not recorded |
Node 1 (account 0.0.4) | Operational | Component | Not recorded |
Node 1 (account 0.0.4) | Operational | Component | Not recorded |
Node 1 (account 0.0.4) | Hosted by Swirlds | Iowa, USA | Operational | Component | 6/20/2026 |
Mirror Node HCS gRPC Testnet | Operational | Component | Not recorded |
Node 2 (account 0.0.5) | Operational | Component | Not recorded |
Node 2 (account 0.0.5) | Operational | Component | Not recorded |
Node 3 (account 0.0.6) | Operational | Component | Not recorded |
Node 3 (account 0.0.6) | Operational | Component | Not recorded |
Hedera Testnet (v0.74.0) | Network Uptime For access to the Hedera testnet, please register at portal.hedera.com | Operational | Component | Not recorded |
Node 4 (account 0.0.7) | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Hedera is currently marked as Degraded in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
0%
Known uptime
22 known history days
58
Components tracked
3 outage, 0 degraded
36
Incidents indexed
0 active right now
56
Maintenance windows
4 active or scheduled
Components with the most recent status-page events.
Node 37 (account 0.0.40) | Hosted by FedEx | Zürich, Switzerland
Partial Outage
Node 11 (account 0.0.14) | Hosted by IBM | Texas, USA
Partial Outage
Hedera Mainnet (v0.74.2) | Individual Nodes
Partial Outage
Node 32 (account 0.0.35) | Hosted by Arrow Electronics | Virginia, USA
Operational
Node 26 (account 0.0.29) | Hosted by Aberdeen Investments | London, UK
Operational
0
operational days
0
degraded days
4
outage days
18
maintenance days
68
unknown days
Latest outages and degradations detected from the official status page.
The problem that led to the extended outage has been resolved and the upgrade to 0.73.0 has been completed successfully. Release notes: https://docs.hedera.com/hedera/networks/release-notes/services#release-v0-73
The issue affecting Hedera Testnet Smart Contracts has now been resolved. The update resolving the issue has been released to Testnet in v0.64.2. https://status.hedera.com/incidents/fk8hvt7p3vhd If you are experiencing any unexpected behaviour, please raise this on the Hedera Discord: https://hedera.com/discord
This incident has been resolved.
This issue has been resolved with the release of Hedera Services v0.58 on February 19, 2025. Values shown for staking rewards accrued for an account will be accurate after the next time it collects staking rewards.
This incident has been resolved
We have resolved the incident and the mirrornode is behaving as expected.
The issue is now resolved on Mainnet. The `MAX_ENTITIES_IN_PRICE_REGIME_HAVE_BEEN_CREATED` error was caused by the increased network usage and adoption we’re seeing from multiple applications. Although the network capacity was increased recently with the “Data on Disk” improvements, the token associations limit was not adjusted to match this increased capacity. The limit has been updated to accurately reflect the expanded network capacity.
The incident has been resolved. A postmortem report will be added to this incident as it becomes available
The Hedera testnet had an incident yesterday which resulted in approximately five hours of downtime \(for testnet only\). The issue arose in the centralized management of testnet. It was fixed, and testnet is now running correctly. No data was lost or corrupted. This was not caused by any code bugs, and does not affect mainnet. Engineering and DevOps will be conducting a root cause analysis around this issue to better understand how to prevent these issues from occurring in the future.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
We will be undergoing scheduled maintenance during this time.
As of May 20, transitional nodes are being phased out and replaced with permanent nodes. This transition may temporarily affect staking while solutions are being implemented. Thank you for your patience and understanding.
Aberdeen Investments/node26 scheduled maintenance from 2026-06-29 07:00 to 2026-06-29 13:00 UTC
Hedera will be upgrading the Hedera testnet to v0.75 on Tuesday, June 23 2026 at 17:00 UTC. The upgrade will take approximately 40 minutes to complete, users should expect some disruption to network services during this time.
The scheduled maintenance has been completed.
Completed: The Hedera mainnet upgrade to v0.74.2 has been completed successfully! https://docs.hedera.com/hedera/networks/release-notes/services#release-v0.74
The scheduled maintenance has been completed.
The testnet v0.75 upgrade scheduled for Wednesday, June 17 2026 at 17:00 UTC has been rescheduled to Tuesday, June 23 2026 at 17:00 UTC.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Hedera status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.hedera.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
