Blockdaemon

blockdaemon.com

Blockdaemon declares 8 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Amazon Web Services, Google Cloud and Microsoft. No published changes since we first read it on Nov 6, 2026.

Subprocessors CSV · Atom DORA draft CSV what's this? · 

8 third parties.

NamePurposeLocationListed since
Amazon Web Services Cloud Hosting & Data StorageCloud infrastructure services
Google Cloud Platform Cloud Hosting & Data StorageCloud infrastructure and productivity services (Google Cloud Platform and Google Workspace)
Microsoft Azure Cloud infrastructure and productivity servicesUnited States
OVH Cloud Cloud computing servicesUnited States
Salesforce Customer relationship managementUnited States
Slack IT: Internal communication and collaboration platform.Internal communications
Sum and Substance Ltd (SumSub) Identity verification and AML screeningUnited Kingdom
Velia Data storage and processing

Web TechnologiesCSV · Atom

Blockdaemon's homepage made 99 requests to 23 domains, 6 services controlled by another company, and 1 domain not identified.

Analytics (2): HubSpot, LinkedInAdvertising (1): Google CloudCookie compliance (1): OneTrustCDN (1): CloudflareOther (1): JavaScript libraries: Webflow

6 third parties by category: Analytics 2Advertising 1Cookie compliance 1CDN 1Other 1

Third parties 6 · 94 requests
Webflow Webflow 1.6.0 jQuery 3.5.1 41% of the page's requests 41
Google Cloudsubprocessor DoubleClick Floodlight Google Analytics Google Font API Google Hosted Libraries Google Tag Manager 23% of the page's requests 23
OneTrust OneTrust 13% of the page's requests 13
HubSpot HubSpot HubSpot Analytics 12% of the page's requests 12
LinkedIn Linkedin Insight Tag 3% of the page's requests 3
Cloudflare cdnjs 2% of the page's requests 2
Unknown 1 · 3 requests

webflow.services

First party 1 · 2 requests
Blockdaemon Cloudflare GSAP 3.15.0 HTTP/3 Lucide Open Graph Webpack 2% of the page's requests 2

5 tracked companies loaded by the homepage are not in Blockdaemon's subprocessor list. A website can use a service without it processing customer data.

ComplianceCSV · Atom

Certified
Says it complies with

Certifications as Blockdaemon's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV · Atom

Aug 14: 2 incidents (2 minor)Aug 15: no incident reportedAug 16: no incident reportedAug 17: no incident reportedAug 18: no incident reportedAug 19: no incident reportedAug 20: no incident reportedAug 21: 1 incident (1 no impact stated)Aug 22: no incident reportedAug 23: no incident reportedAug 24: 1 incident (1 no impact stated)Aug 25: no incident reportedAug 26: no incident reportedAug 27: 1 incident (1 minor)Aug 28: no incident reportedAug 29: no incident reportedAug 30: no incident reportedAug 31: 1 incident (1 critical)Sep 1: no incident reportedSep 2: 1 incident (1 minor)Sep 3: no incident reportedSep 4: no incident reportedSep 5: no incident reportedSep 6: no incident reportedSep 7: no incident reportedSep 8: 2 incidents (2 minor)Sep 9: no incident reportedSep 10: no incident reportedSep 11: no incident reportedSep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: no incident reportedSep 17: no incident reportedSep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: 1 incident (1 critical)Sep 23: 1 incident (1 minor)Sep 24: no incident reportedSep 25: no incident reportedSep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reportedSep 29: 1 incident (1 minor)Sep 30: no incident reportedOct 1: 1 incident (1 minor)Oct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: 1 incident (1 minor)Oct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: 1 incident (1 minor)Oct 27: no incident reportedOct 28: 1 incident (1 major)Oct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: no incident reportedNov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: 1 incident (1 minor)Nov 11: no incident reported

90 days agotoday

  • 20 incidents in 90 days
  • 3 major or critical
  • 7 days typical time to resolve
  • 23 days longest major
BeganIncidentImpactLasted
Polygon – Degraded RPC Performanceminor20 days
Ethereum Validator Attestation Issueno impact stated26 days
ETH2 Prysm Client Degradation Following Fusaka Upgrade Impacting L2 Networksminor34 days
[Ethereum] - Degraded Performanceminor35 h 56 min
Solana Validator Service Incidentmajor13 days
[Solana] - Historical Data Missingminor13 days
[Hyperliquid] - Degraded Performanceminor6 days
[Cronos] Archive Nodes – Slow Synchronizationminor7 days

Incidents per month

0 5 10 Dec 2025: 3 incidents (1 critical, 1 minor, 1 no impact stated) · typical time to resolve 24 h 46 min Jan 2026: 6 incidents (1 major, 5 minor) · typical time to resolve 28 h 16 min Feb 2026: 5 incidents (3 minor, 2 no impact stated) · typical time to resolve 3 h 47 min Mar 2026: 4 incidents (4 minor) · typical time to resolve 24 h 6 min Apr 2026: 2 incidents (2 minor) · typical time to resolve 30 h 44 min May 2026: 4 incidents (1 major, 2 minor, 1 no impact stated) · typical time to resolve 2 days Jun 2026: 2 incidents (2 no impact stated) · typical time to resolve 3 days Jul 2026: 9 incidents (2 major, 6 minor, 1 no impact stated) · typical time to resolve 29 h 18 min Aug 2026: 9 incidents (1 critical, 1 major, 5 minor, 2 no impact stated) · typical time to resolve 6 days Sep 2026: 6 incidents (1 critical, 5 minor) · typical time to resolve 45 h 20 min Oct 2026: 4 incidents (1 major, 3 minor) · typical time to resolve 13 days Nov 2026: 1 incident (1 minor) · typical time to resolve 35 h 56 min Dec 2025Jan 2026Feb Mar Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated

Components affected

ComponentIncidents
Ethereum1
Ethereum Validators1
Solana1
Solana Validator1

As Blockdaemon's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by Blockdaemon's subprocessorsCSV · Atom

1 reported incident in the last 30 days, by 1 of the vendors Blockdaemon lists as a subprocessor.

A subprocessor list names a company, not the service an incident touched. This does not show that Blockdaemon was involved.

DateCompanyIncidentImpactLasted
SumsubDegraded performance of International TIN Validation no impact stated5 h 5 min

Who is around them.

ChangesCSV · Atom

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Blockdaemon's site

Blockdaemon transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/blockdaemon"><img src="https://thirdpartyindex.com/badge/blockdaemon.svg" alt="Blockdaemon transparency rating on Third Party Index" height="20"></a>
[![Blockdaemon transparency rating on Third Party Index](https://thirdpartyindex.com/badge/blockdaemon.svg)](https://thirdpartyindex.com/vendors/blockdaemon)