Is Hedera down?
Minor issues reported
From status.hedera.com · checked 44 seconds ago · every 5 minutes
An email when it goes down, and when it’s back.
As of 03:27 UTC on 12 November 2026, Hedera's status page reports minor issues.
- Last problem
- Going on now
- Problems, last 30 days
- 2
- Typical incident
- 11 days
- Longest in 90 days
- 12 days · 4 Oct
Minor Service Outage
IssueStarted 14 days ago, affecting Node 11 (account 0.0.14) | Hosted by IBM | Texas, USA, Node 26 (account 0.0.29) | Hosted by Aberdeen Investments | London, UK, Node 36 (account 0.0.39) | Hosted by McLaren Racing | London, UK.
Read the updates on status.hedera.com ↗Uptime
Hedera, last 30 days
0 %
Biggest dip: Hedera, 346 h of issue on Oct 28.
Incidents
Started in the last 7 days
0
This week Week before
No incidents this week. The last one: Hedera, issue on Oct 28.
Recovery
Median time back online
287 h 34 min
0 of 1 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 53
3 with issues
- Hedera Mainnet (v0.78.2) | Network Uptime
- Hedera Testnet (v0.79.0) | Network Uptime
- Hedera Previewnet (v0.80.0-alpha.5) | Network Uptime
Hedera Mirror Node Mainnet (v0.165.1) 2
parts 
- Mirror Node REST API Mainnet
- Mirror Node HCS gRPC Mainnet
Hedera Mirror Node Previewnet (v0.166.2) 2
parts
- Mirror Node REST API Previewnet
- Mirror Node HCS gRPC Previewnet
Hedera Testnet (v0.79.0) | Individual Nodes 7
parts
- Node 0 (account 0.0.3)
- Node 1 (account 0.0.4)
- Node 2 (account 0.0.5)
- Node 3 (account 0.0.6)
- Node 4 (account 0.0.7)
- Node 5 (account 0.0.8)
- Node 6 (account 0.0.9)
Hedera Previewnet (v0.80.0-alpha.5) | Individual Nodes 7
parts
- Node 0 (account 0.0.3)
- Node 1 (account 0.0.4)
- Node 2 (account 0.0.5)
- Node 3 (account 0.0.6)
- Node 4 (account 0.0.7)
- Node 5 (account 0.0.8)
- Node 6 (account 0.0.9)
Hedera Mainnet (v0.78.2) | Individual Nodes 30
parts
- Node 0 (account 0.0.3) | Hosted by LG | Singapore
- Node 1 (account 0.0.4) | Hosted by Swirlds | Iowa, USA
- Node 4 (account 0.0.7) | Hosted by Nomura | Tokyo, Japan
- Node 5 (account 0.0.8) | Hosted by Google | Helsinki, Finland
- Node 6 (account 0.0.9) | Hosted by Zain Group | Kuwait City, Kuwait
- Node 7 (account 0.0.10) | Hosted by Magalu | São Paulo, Brazil
- Node 9 (account 0.0.12) | Hosted by DLA Piper | Helsinki, Finland
- Node 10 (account 0.0.13) | Hosted by Tata Communications | Frankfurt, Germany
- Node 11 (account 0.0.14) | Hosted by IBM | Texas, USA Major outage
- Node 12 (account 0.0.15) | Hosted by Deutsche Telekom | Berlin, Germany
- Node 15 (account 0.0.18) | Hosted by Dentons | Roubaix, France
- Node 17 (account 0.0.20) | Hosted by Australian Payments Plus | Sydney, Australia
- Node 18 (account 0.0.21) | Hosted by EDF | Paris, France
- Node 19 (account 0.0.22) | Hosted by Shinhan Bank | London, UK
- Node 20 (account 0.0.23) | Hosted by Chainlink Labs | Michigan, USA
- Node 21 (account 0.0.24) | Hosted by LSE | Falkenstein, Germany
- Node 22 (account 0.0.25) | Hosted by IIT Madras | Naaldwijk, Netherlands
- Node 25 (account 0.0.28) | Hosted by Ubisoft | Quebec, Canada
- Node 26 (account 0.0.29) | Hosted by Aberdeen Investments | London, UK Major outage
- Node 30 (account 0.0.33) | Hosted by Mondelēz International | Mumbai, India
- Node 31 (account 0.0.34) | Hosted by BitGo | Stockholm, Sweden
- Node 32 (account 0.0.35) | Hosted by Arrow Electronics | Virginia, USA
- Node 33 (account 0.0.36) | Hosted by Nairobi Securities Exchange | London, UK
- Node 34 (account 0.0.37) | Hosted by Blockchain for Energy | Helsinki, Finland
- Node 35 (account 0.0.38) | Hosted by Repsol | La Rioja, Spain
- Node 36 (account 0.0.39) | Hosted by McLaren Racing | London, UK Major outage
- Node 37 (account 0.0.40) | Hosted by FedEx | Zürich, Switzerland
- Node 38 (account 0.0.41) | Hosted by Accenture | Brussels, Belgium
- Node 39 (account 0.0.42) | Hosted by Dell | Cork, Ireland
- Node 43 (account 0.0.46) | Hosted by Standard Bank | Vilnius, Lithuania
Hedera Mirror Node Testnet (v0.166.2) 2
parts
- Mirror Node REST API Testnet
- Mirror Node HCS gRPC Testnet
Last 90 days
5 incidents in 48 days tracked · no reported issues 0.1% of the time · typical incident 11 days
Recent incidents
Times in UTC
- Mainnet Upgrade to v0.78.2 23 min
Maintenance - Minor Service Outage 11 days Issue
- Mainnet Upgrade to v0.78.1 25 min Maintenance
- Minor Service Outage and 2 more 12 days Issue
- Mainnet Upgrade to v0.77 20 min Maintenance
- AccountBalanceQuery Deprecation in v0.77 and 2 more 4 days Issue
- AccountBalanceQuery Deprecation in v0.77 32 min Maintenance
- Minor Service Outage and 2 more at least 3 days Issue
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
CriticalAWS · Bahrain (me-south-1) Region Availability
CriticalAWS · UAE (me-central-1) Region Availability
CriticalGW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
Popular services
All services
Where this comes from
Stackpulse reads Hedera’s official status page at status.hedera.com every 5 minutes and keeps 90 days of what changed. We don’t test Hedera ourselves, so a problem shows here once Hedera reports it.
Stackpulse isn’t affiliated with Hedera. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.