The resolver providers behind ThisDID's routing chains — the TS Universal Resolver driver fleet and
the redundant upstreams — with live availability, a measured reliability composite
(success consistency, stability, latency discipline, throttle behavior, verification
agreement), and each provider's share of routed traffic. Numbers come from the engine's own
probes and analytics.
upTypeScript DID Resolver fleet
Twenty-four isolated TypeScript driver Workers — the first hop of every routing chain, probation-verified against redundant upstreams while new.
avail 24h 99% ·
reliability 55 ·
share 7d 66% ·
methods 25
upHosted Universal Resolver
Danube Tech's hosted Universal Resolver — the broad-catalog second hop for most methods. Quota-throttled: probed via its unmetered health endpoint, and 429s count as up-but-throttled, never as downtime.
avail 24h 100% ·
reliability 71 ·
share 7d 1% ·
methods 18
upUniversal Resolver + cid Gatekeeper
A full Universal Resolver deployment plus the cid-only Gatekeeper API — the probation verifier for several TS Universal Resolver drivers (iden3, cid, sol, hedera among them).
avail 24h 100% ·
reliability 80 ·
share 7d 27% ·
methods 14
updid:oyd method resolver
Public resolver for the did:oyd method (OYDID). The identifier is cryptographically derived from the DID Document, and a cryptographically linked public provenance log guarantees that resolution yields the latest valid version.
avail 24h 94% ·
reliability 84 ·
share 7d 0% ·
methods 1
degradedAlgorand-native Universal Resolver
The Algorand-native resolver: authoritative first hop for did:algo and did:nfd.
avail 24h 53% ·
reliability 81 ·
share 7d 6% ·
methods 2