What is Blockdaemon's uptime?

Over the last 90 days, Blockdaemon reported 97.60% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.blockdaemon.com, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Blockdaemon's uptime history rolling forward in real time.

Has Blockdaemon had outages in 2026?

Yes, Blockdaemon has had 152 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Blockdaemon outage?

The most recent Blockdaemon incident was "[Canton] - Devnet Network-Wide Topology Freeze (Upstream Event)", which started on October 29, 2026 and was resolved on October 30, 2026. Pingoru captured this directly from https://status.blockdaemon.com. See the full incident card above for affected components and the update timeline.

How often does Blockdaemon have outages?

Based on the last 90 days, Blockdaemon averages 50.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components: so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Blockdaemon's status page?

Blockdaemon's official status page is https://status.blockdaemon.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Blockdaemon down right now?

Blockdaemon is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Blockdaemon reports a change. Current status is based on 129 tracked services.

How does Pingoru know if Blockdaemon is down?

We read https://status.blockdaemon.com directly, using Blockdaemon's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Where can I get notified when Blockdaemon has an outage?

Create a free Pingoru account and add Blockdaemon as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Blockdaemon's status page says the service is up, but I'm having issues. What's wrong?

Three common reasons: • A real Blockdaemon incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Blockdaemon issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Blockdaemon status?

We use Blockdaemon's own status page at https://status.blockdaemon.com. Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Partial Outage" mean?

Blockdaemon has a partial outage. One or more components are down, but the rest of the service is operational.

Is Blockdaemon down?

Last checked 4m ago

Current status

Blockdaemon is having a partial outage

2 active incidents: Solana Validator Service Incident, [Solana] - Historical Data Missing

Get alerts when Blockdaemon breaks → View Blockdaemon outage history →

Free, no credit card

Official status page: status.blockdaemon.com
Checked every 5 minutes
129 components tracked

Blockdaemon is reporting a partial outage right now (last checked 4m ago). Some components are affected; others remain operational.

Real-time Blockdaemon status, recent outages, and incident history: pulled directly from Blockdaemon's official status page at status.blockdaemon.com every 5 minutes. Pingoru tracks 129 Blockdaemon services and has captured 154 incidents in the last 90 days (97.60% uptime). Get email, Slack, Discord, or webhook alerts the moment Blockdaemon reports a new incident, free for 3 monitors, no credit card.

Users who monitor Blockdaemon also follow these APIs services:

CloudConvert View all 8,000+ providers

Blockdaemon uptime 97.60% uptime · past 90 days

Mon Wed Fri

AugSepOct

Less More

Active incidents 2

Solana Validator Service Incident

Ongoing ● 3d 2h

Started Oct 28, 2026, 10:46 AM UTC

Solana Validator
Timeline · 3 updates
- identified · Oct 28, 2026, 10:46 AM UTC
  
  Between 26 and 27 October, Blockdaemon identified that operator keys for a small set of our oldest running Solana validators were compromised. The attacker was able to change the withdrawal authority on the impacted validators and move a limited amount of operational assets from their operational accounts. Your delegated SOL is safe. There is no indication of loss or risk to staked principal. Delegated SOL remains in each delegator’s own stake account and was not moved. Reward impact: Because we cannot fund the voting accounts on the compromised validators, they will not earn rewards starting with epoch 1070. Recommended action: The impacted validators must be replaced. A new validator is being prepared, and we will post its details here as soon as it is available. We are working directly with affected customers to move stakes to newly created validators quickly and minimise gaps in rewards. If you need help deactivating, withdrawing or re-delegating, please contact Blockdaemon support - [email protected] Full details and live updates are published here: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
- identified · Oct 28, 2026, 09:13 PM UTC
  
  Following our initial update on October 27 regarding the exposure of operator keys on a small subset of our validators, we are providing a follow-up on our security review. Alongside our external digital forensics partners, our teams are continuing to evaluate the event and review our surrounding environments. Our review has identified no indicators of compromise across our broader infrastructure, and our investigation to date has found no indication that any other Blockdaemon products, services, protocols or validators are affected. Customer data and assets also remain uncompromised. As previously noted, delegated SOL remains safe in delegators' own stake accounts, and no client data or sensitive information was accessed. The scope of this incident remains limited to the operational accounts identified in our initial notice. All impacted customers have been notified. If you did not receive a notification, you were not impacted by this incident. If you believe you were affected, please contact us at [email protected]. Aside from the deactivation and re-delegation steps previously recommended for the impacted validators, no additional client action is required. We are maintaining active monitoring and telemetry analysis across our infrastructure. If you need assistance re-delegating stake or have specific questions, please reach out through standard Blockdaemon support channels. Full details and live updates are published here: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
- identified · Oct 30, 2026, 12:04 AM UTC
  
  Update as of 10/29/2026 Our investigation into the recent validator event remains ongoing in close coordination with independent external forensic specialists. While a final root cause has not yet been formally concluded, findings to date point directly to a historical key generation practice that was discontinued and no longer exists in our environment. This historical practice was strictly limited in scope. Importantly, external forensic findings to date confirm that our present infrastructure, controls, and active environments have not been breached, and no current systems were accessed during this event. The containment of this incident reflects our underlying architecture. Our Software Development Lifecycle enforces protocol isolation by design, accounting for the unique technical requirements and operational mechanics of each network. This model includes segregated delivery teams, isolated source code, and most critically, separate and independent key management for each protocol. We will continue to provide updates and will publish verified findings as soon as the investigation formally concludes. If you have any questions, our support channels remain available. Full details, FAQ and live updates: https://www.blockdaemon.com/incident-reports/operational-impact-on-solana-validators
Latest: Update as of 10/29/2026 Our investigation into the recent validator event remains ongoing in close coordination with independent external forensic specialists. While a final root c…
[Solana] - Historical Data Missing

Ongoing ● 4d 22h

Started Oct 26, 2026, 03:19 PM UTC

Solana
Timeline · 1 update
- identified · Oct 26, 2026, 03:19 PM UTC
  
  We have identified an issue affecting Solana, and our team is actively working on a resolution. We will keep you informed and share updates as progress is made. We sincerely apologize for any inconvenience this may be causing and appreciate your patience as we work to resolve the matter. If you have any questions or need further assistance, please don’t hesitate to contact your Account Manager! Thank you for your understanding!
Latest: We have identified an issue affecting Solana, and our team is actively working on a resolution. We will keep you informed and share updates as progress is made. We sincerely apolog…

Recent outages & incidents

Past 90 days

[Hyperliquid] - Degraded Performance

Resolved 6d 19h

Started Oct 15, 2026, 02:08 PM UTC · Resolved Oct 22, 2026, 09:22 AM UTC

Hyperliquid Native API
Timeline · 3 updates
- investigating · Oct 15, 2026, 02:08 PM UTC
  
  We want to inform you that we are currently experiencing issues with our Hyperliquid nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Hyperliquid nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments! If you have any questions or concerns, please reach out to your Account Manager.
- monitoring · Oct 16, 2026, 04:21 PM UTC
  
  We would like to inform you that a fix has been implemented for the issue affecting Hyperliquid nodes, and we are currently monitoring the service to ensure stability. We will provide further updates once the monitoring period is complete and the issue is fully resolved. We sincerely apologize for any inconvenience this may have caused and appreciate your patience. If you have any questions or need assistance, please feel free to reach out to your Account Manager! Thank you for your understanding!
- resolved · Oct 22, 2026, 09:22 AM UTC
  
  We are pleased to inform you that the issue affecting Hyperliquid nodes has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Account Manager! Thank you for your understanding!
Latest: We are pleased to inform you that the issue affecting Hyperliquid nodes has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience th…
[Cronos] Archive Nodes – Slow Synchronization

Resolved 7d 3h

Started Oct 01, 2026, 10:20 AM UTC · Resolved Oct 08, 2026, 01:33 PM UTC

Cronos
Timeline · 2 updates
- investigating · Oct 01, 2026, 10:20 AM UTC
  
  We want to inform you that we are currently experiencing issues with some Cronos node services. Specifically, our Cronos archive nodes are experiencing slow syncing, while full nodes are operating normally. As a result, you may encounter difficulties accessing the affected Cronos archive nodes. Our team is actively investigating the issue and working diligently to resolve it. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments. If you have any questions or concerns, please reach out to your Account Manager.
- resolved · Oct 08, 2026, 01:33 PM UTC
  
  We are pleased to inform you that the issue affecting Cronos node has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Account Manager! Thank you for your understanding!
Latest: We are pleased to inform you that the issue affecting Cronos node has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may…
[Stellar] - Testnet Network Halt

Resolved 1h 34m

Started Sep 29, 2026, 07:44 PM UTC · Resolved Sep 29, 2026, 09:18 PM UTC

Stellar Native APIStellar
Timeline · 2 updates
- investigating · Sep 29, 2026, 07:44 PM UTC
  
  We want to inform you that we are currently experiencing issues with our Stellar Testnet Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Stellar Testnet Nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated on any developments! If you have any questions or concerns, please reach out to your Customer Success Manager.
- resolved · Sep 29, 2026, 09:18 PM UTC
  
  We are pleased to inform you that the issue affecting Stellar Testnet has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Account Manager.
Latest: We are pleased to inform you that the issue affecting Stellar Testnet has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this…
Degraded Performance - Avalanche Mainnet Native

Resolved 4h 25m

Started Sep 23, 2026, 05:16 AM UTC · Resolved Sep 23, 2026, 09:41 AM UTC

Avalanche ValidatorAvalanche Native APIAvalanche
Timeline · 2 updates
- identified · Sep 23, 2026, 05:16 AM UTC
  
  We are currently investigating an issue affecting Avalanche Mainnet Native RPC, Archive, and Validator services. As a result, some requests to these endpoints may return errors or fail intermittently. A fix has been identified and is being rolled out. We will also be carrying out a brief maintenance window to complete this rollout across the nodes. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will provide updates as more information becomes available. If you have any questions or concerns, please reach out to your Customer Success Manager.
- resolved · Sep 23, 2026, 09:41 AM UTC
  
  This incident has been resolved.
Latest: This incident has been resolved.
[Cosmos] - Protocol wide chain halt

Resolved 1d 21h

Started Sep 22, 2026, 11:35 AM UTC · Resolved Sep 24, 2026, 08:55 AM UTC

Cosmos Staking APICosmos ValidatorCosmos Native APICosmosCosmos Staking Reporting
Timeline · 2 updates
- identified · Sep 22, 2026, 11:35 AM UTC
  
  We have identified that the issue affecting Cosmos is related to an underlying problem with the foundation. Our team is actively collaborating with the foundation's engineering team to work toward a resolution. We will keep you informed and share updates as progress is made. We sincerely apologize for any inconvenience this may be causing and appreciate your understanding as we work with the foundation to resolve the matter. If you have any questions or need further assistance, please don’t hesitate to contact your Customer Success Manager! Thank you for your patience and support!
- resolved · Sep 24, 2026, 08:55 AM UTC
  
  We are pleased to inform you that the issue affecting Cosmos has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the matter. If you have any further questions or concerns, please don’t hesitate to reach out to your Customer Success Manager! Thank you for your understanding!
Latest: We are pleased to inform you that the issue affecting Cosmos has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenience this may have…

See the full Blockdaemon outage history

13 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Blockdaemon outage history →

Or sign up free to get alerts when Blockdaemon breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 129 components checked every 5 minutes

65incidents recorded

60last 12 months

18last 90 days

5 daystypical duration, 12 months

The longest incident in the last year, ETH2 Prysm Client Degradation Following Fusaka Upgrade Impacting L2 Networks on December 4, 2025, ran for 34 days. 326 maintenance windows announced in the same period.

Most affected components, last 12 months

Stellar8
Blockdaemon Universal API7
Solana7
Avalanche6
Avalanche Native API6

Latest incidents

Solana Validator Service Incident October 28, 2026 · still open · major outage
Between 26 and 27 October, Blockdaemon identified that operator keys for a small set of our oldest running Solana validators were compromised. The attacker was…
[Solana] - Historical Data Missing October 26, 2026 · still open · degraded service
We have identified an issue affecting Solana, and our team is actively working on a resolution. We will keep you informed and share updates as progress is…
[Hyperliquid] - Degraded Performance October 15, 2026 · 7 days · degraded service
We want to inform you that we are currently experiencing issues with our Hyperliquid nodes. Our team is actively investigating the problem and working…

Outage history

Past 90 days · 18 incidents View full outage history →

Solana Validator Service Incident Ongoing

Started Oct 28, 2026, 10:46 AM UTC · ● 3d 2h
[Solana] - Historical Data Missing Ongoing

Started Oct 26, 2026, 03:19 PM UTC · ● 4d 22h
[Hyperliquid] - Degraded Performance Resolved

Started Oct 15, 2026, 02:08 PM UTC · Resolved Oct 22, 2026, 09:22 AM UTC · 6d 19h
[Cronos] Archive Nodes – Slow Synchronization Resolved

Started Oct 01, 2026, 10:20 AM UTC · Resolved Oct 08, 2026, 01:33 PM UTC · 7d 3h
[Stellar] - Testnet Network Halt Resolved

Started Sep 29, 2026, 07:44 PM UTC · Resolved Sep 29, 2026, 09:18 PM UTC · 1h 34m
Degraded Performance - Avalanche Mainnet Native Resolved

Started Sep 23, 2026, 05:16 AM UTC · Resolved Sep 23, 2026, 09:41 AM UTC · 4h 25m
[Cosmos] - Protocol wide chain halt Resolved

Started Sep 22, 2026, 11:35 AM UTC · Resolved Sep 24, 2026, 08:55 AM UTC · 1d 21h
[Cosmos Hub] - Degraded Performance Resolved

Started Sep 08, 2026, 11:21 PM UTC · Resolved Sep 09, 2026, 06:16 PM UTC · 18h 54m