Is Blockdaemon down?

Last checked 5m ago
Current status
Blockdaemon is down

3 active incidents: **Urgent** [Arc] - Internal Maintenance, [Solana] Testnet Network Halt · +1 more

Official status page: https://status.blockdaemon.com · Polled every 5 minutes · 128 components tracked

Blockdaemon is reporting a major outage right now (last checked 5m ago). 3 active incidents on the official status page.

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

Users who monitor Blockdaemon also follow these APIs services: Vonage Make Vonage Business Retool Telnyx Mapbox Vonage API EasyPost Celigo Olo View all 6,000+ providers
Blockdaemon uptime 97.72% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incidents 2

  1. Ongoing ● 6d 18h
    Started Sep 08, 2026, 12:01 PM UTC
    Solana Staking ReportingSolana Staking APISolana Native APISolana ValidatorSolana
    Timeline · 1 update
    • monitoring · Sep 08, 2026, 12:01 PM UTC

      We want to provide an update regarding the ongoing halt of the Solana Testnet network, which the Solana Foundation initiated at the start of Epoch 1025 as part of the normal stabilization process for Agave v4.3. At this time, we are still waiting for the Solana Testnet reset. Our engineering team is actively monitoring the situation and will keep you informed as soon as the reset is completed. We greatly appreciate your continued patience and understanding during this time!

    Latest: We want to provide an update regarding the ongoing halt of the Solana Testnet network, which the Solana Foundation initiated at the start of Epoch 1025 as part of the normal stabil…

  2. Ongoing ● 14d 14h
    Started Aug 31, 2026, 03:25 PM UTC
    Cronos Native APICronos
    Timeline · 2 updates
    • investigating · Aug 31, 2026, 03:25 PM UTC

      We want to inform you that we are currently experiencing issues with our Cronos nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Cronos 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.

    • monitoring · Sep 03, 2026, 01:52 PM UTC

      We’d like to share an update on this incident. The Cronos Network chain halt is a network-wide issue impacting the synchronization and availability of Cronos nodes. The Cronos team has advised that a network rule put in place during their incident response is still blocking connections. We continue to monitor the situation and will provide further updates as more information becomes available. We apologize for the inconvenience and appreciate your patience and understanding.

    Latest: We’d like to share an update on this incident. The Cronos Network chain halt is a network-wide issue impacting the synchronization and availability of Cronos nodes. The Cronos team…

Recent outages & incidents

Past 90 days
  1. Resolved 18h 54m
    Started Sep 08, 2026, 11:21 PM UTC · Resolved Sep 09, 2026, 06:16 PM UTC
    Cosmos Native APICosmos
    Timeline · 2 updates
    • identified · Sep 08, 2026, 11:21 PM UTC

      We have identified an issue affecting our Cosmos Hub API nodes, full nodes, and archive nodes following a recent network upgrade. Our team has identified the root cause and is actively working on recovery. We will post updates as they become available. We apologize for the inconvenience and appreciate your patience and understanding. If you have any questions or concerns, please reach out to your Customer Success Manager.

    • resolved · Sep 09, 2026, 06:16 PM UTC

      We are pleased to inform you that the issue affecting Cosmos Hub API nodes, full nodes, and archive 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 Customer Success Manager! Thank you for your understanding!

    Latest: We are pleased to inform you that the issue affecting Cosmos Hub API nodes, full nodes, and archive nodes has been resolved, and the service is now fully operational. We sincerely …

  2. Resolved 7d 18h
    Started Sep 02, 2026, 06:12 PM UTC · Resolved Sep 10, 2026, 12:13 PM UTC
    Blockdaemon Universal APISolana
    Timeline · 4 updates
    • investigating · Sep 02, 2026, 06:12 PM UTC

      Blockdaemon is currently investigating degraded performance and increased latency affecting the Universal API on Solana Mainnet. Specifically, customers may experience issues retrieving older blocks. We are actively working to identify the root cause and restore full performance as quickly as possible. We will provide further updates as our investigation progresses. If you have any questions or concerns, please reach out to your Customer Success Manager.

    • identified · Sep 03, 2026, 03:16 PM UTC

      We have identified an unusual spike in traffic as the contributing factor to the degraded performance and increased latency on the Universal API for Solana Mainnet. While the service is operating as expected, our team is actively drilling into the root cause of this traffic anomaly and will provide further updates as our investigation progresses. If you have any questions or concerns, please reach out to your Customer Success Manager.

    • monitoring · Sep 04, 2026, 02:54 PM UTC

      We would like to inform you that a fix has been implemented for the issue affecting the performance of Universal API on Solana Mainnet, 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 Customer Success Manager! Thank you for your understanding!

    • resolved · Sep 10, 2026, 12:13 PM UTC

      We are pleased to inform you that the issue affecting Universal API for Solana Mainnet 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 Universal API for Solana Mainnet has been resolved, and the service is now fully operational. We sincerely apologize for any i…

  3. Resolved 6d
    Started Aug 27, 2026, 12:28 PM UTC · Resolved Sep 02, 2026, 01:07 PM UTC
    Polkadot Native API
    Timeline · 2 updates
    • investigating · Aug 27, 2026, 12:28 PM UTC

      We want to inform you that we are currently experiencing issues with our Polkadot Westend Nodes. Our team is actively investigating the problem and working diligently to resolve it. As a result, you may encounter difficulties accessing your Polkadot Westend Nodes 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 02, 2026, 01:07 PM UTC

      We are pleased to inform you that the issue affecting Polkadot Westend 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 Customer Success Manager! Thank you for your understanding!

    Latest: We are pleased to inform you that the issue affecting Polkadot Westend Nodes has been resolved, and the service is now fully operational. We sincerely apologize for any inconvenien…

  4. Resolved 7d 21h
    Started Aug 24, 2026, 12:41 PM UTC · Resolved Sep 01, 2026, 10:36 AM UTC
    Cardano Staking Reporting
    Timeline · 2 updates
    • investigating · Aug 24, 2026, 12:41 PM UTC

      We are currently investigating an issue affecting Cardano staking reporting. As a result, new staking data may not be available from the time the issue began. Historical data from before the issue started remains accessible. Our engineering team is actively working to restore the affected services. 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 01, 2026, 10:36 AM UTC

      We are pleased to inform you that the issue affecting Cardano Staking reporting 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 Cardano Staking reporting has been resolved, and the service is now fully operational. We sincerely apologize for any inconven…

  5. Resolved 6d 2h
    Started Aug 21, 2026, 10:23 AM UTC · Resolved Aug 27, 2026, 12:33 PM UTC
    Base Native APIBase
    Timeline · 2 updates
    • investigating · Aug 21, 2026, 10:23 AM UTC

      We are currently investigating an issue affecting some Basechain Reth Archive nodes, which may cause nodes to fall behind the latest block height and result in delayed or degraded RPC responses. Our engineering team has completed the underlying migration and applied a mitigation across the affected nodes. We are continuing to closely monitor Basechain nodes to ensure they remain synchronized and stable. Customers may experience intermittent delays while affected nodes catch up with the latest block height. We will provide further updates as monitoring continues. Reference link: https://github.com/base/node/issues/1163 If you have any questions or need further assistance, please don't hesitate to contact your Customer Success Manager! Thank you for your understanding!

    • resolved · Aug 27, 2026, 12:33 PM UTC

      We are pleased to inform you that the issue affecting Basechain Reth Archive 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 Customer Success Manager! Thank you for your understanding!

    Latest: We are pleased to inform you that the issue affecting Basechain Reth Archive nodes has been resolved, and the service is now fully operational. We sincerely apologize for any incon…

See the full Blockdaemon outage history

17 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

Outage history

Past 90 days · 22 incidents View full outage history →