3 / 3 nodes operational · Sep 24, 2026
Static Labs  ·  Network  ·  DNN Live

DNN — Distributed Node Network, live across the US.

DNN — the Distributed Node Network (formerly USDNN) — is officially live as of September 24, 2026. Three nodes serve attestation, verification, and anti-cheat from coast to coast: no single point of failure, faster responses no matter where you are, and automatic failover if any node ever has issues.

View topology How routing works Failover behavior

Three nodes online and serving

West, East, and our DB node are all online. If one node ever has issues, the others pick it up automatically.

Network topology — United States coverage

One primary for truth, replicas everywhere for speed. Purple holds the West, green holds the East, and Central rides whichever answers faster.

DNN Distributed Node Network United States coverage — September 2026 US-CENTRAL ROUTED · NO NODE DALLAS HUB → FASTEST WEST COVERAGE · LAX PRIMARY EAST COVERAGE · IAD CENTRAL ROUTED · TX → FASTEST Hillsboro HIO · EDGE + REPLICA Los Angeles ★ LAX · DB PRIMARY + EDGE Vint Hill IAD · EDGE + REPLICA

Purple West (Los Angeles primary) replicates out to both green edges; Central has no box of its own — Texas and the middle of the country ride whichever of West or East answers faster.

3 / 3
Nodes live
0
Single points of failure
1
Write primary · N replicas
Auto
Failover · reads stay local

US-West · Los Angeles

LAX
DB PRIMARY + EDGE
  • Primary Postgres — the single source of truth for writes
  • Edge serving West & Central reads in single-digit ms
  • Secondary edge for US-Central traffic

US-West · Hillsboro

HIO
EDGE + REPLICA
  • Local Postgres replica — reads never leave the region
  • Attestation & verification served locally
  • Watches primary, degrades honestly on loss

US-East · Vint Hill

IAD
EDGE + REPLICA
  • Local Postgres replica — reads never leave the region
  • Serves East & Central, whichever answers faster
  • Watches primary, degrades honestly on loss

US-Central — routed, no node

VIRTUAL · ROUTED
  • Provider has no US-Central region, so we pivoted
  • Central routes to West or East, whichever is faster

One VPS couldn't reach the whole country

Static Labs infrastructure used to run on a single fail-point VPS in one data center — high latency for US-Central and US-East, and a mass of resources we never pushed to their limits while overpaying for them.

Reads stay local, writes stay singular

A request lands on the nearest healthy node. Reads — project data, ban verdicts, session lookups, dashboard cards — are served from that node's own Postgres replica in single-digit milliseconds.

Writes — bans, project changes, account updates — commit once on the Los Angeles primary, so there is exactly one source of truth and no merge conflicts, ever. All databases are connected to each other and heavily optimized, so everything responds in practically the same time no matter which node you land on. High-volume telemetry (counters, player events, device touches) is written asynchronously in the background, so it never blocks a response.

What improved

  • Lower latency to our servers, coast to coast
  • Higher maximum RPS across the fleet
  • SPOF (single point of failure) removed
  • Better developer & player experience

How it serves

  • Attestation & verification stay fast everywhere
  • Same verdict and data from every node
  • Cross-country round trips removed from reads

One request, nearest node

No region picker, no manual failover. Every client hits the closest healthy node and gets the same answer.

  1. Land nearby. DNS routes the player to the nearest healthy edge — Hillsboro for the West, Vint Hill for the East, Los Angeles for West & Central overflow.
  2. Read locally. Ban verdicts, project data, session lookups, and dashboard cards come straight from that node's Postgres replica — no cross-country trip.
  3. Write once. Bans, project edits, and account changes commit only on the Los Angeles primary. One writer means no conflicts, ever.
  4. Telemetry in background. Counters, player events, and device touches flush asynchronously — they never block the response.
Player regionServed byReadsWrites
US-WestHillsboro · Los AngelesLocal replicaForwarded to LA primary
US-CentralFastest of West / EastLocal to serving nodeForwarded to LA primary
US-EastVint HillLocal replicaForwarded to LA primary

Degraded, never dark

If the primary ever goes unreachable, edges don't error out — they announce it and keep serving.

Reads continue, writes wait

Each edge node watches the primary and reacts on its own if it ever becomes unreachable: reads, ban checks, and verification keep serving from that node's local replica, while writes pause instead of failing with a cryptic error.

Game clients keep attesting — verification never depended on the write path. When the primary comes back, nodes resume writes automatically, with nothing to reconcile beyond a brief gap in telemetry counters.

  1. Detect. Edge health checks notice the primary is unreachable — no human action needed.
  2. Announce. Dashboard and API surface an honest degraded state instead of cryptic 500s.
  3. Serve reads. Attestation, ban verdicts, session auth, and dashboard reads continue from local replicas.
  4. Resume. Primary returns, replication catches up, writes resume automatically.

Keeps working

  • Attestation & verification
  • Ban verdicts & dashboard reads
  • Session auth & polling

Pauses honestly

  • Ban & settings writes
  • New anti-cheat alerts
  • Usage counters & events

More fleets, then the world

The fleet grows by copying, not by re-architecting: a new region is a replica, a config, and a DNS entry.

Live · Sep 2026

DNN live, GDNN tomorrow

Once Kubian has the revenue for it and needs better request handling, we add more fleets across the US — multiples in each location above, plus nodes near Canada — scaling Static Labs LLC infrastructure so everything feels smoother for developers and end-users.

After that comes GDNN, the Globally Distributed Node Network: per-continent edges with local replicas across Europe, Asia, Oceania, and more — the fastest option for international users, with the fastest authentication, verification, and anti-cheat alerts worldwide.

Network questions, answered

Short answers for the questions studios actually ask about DNN (Distributed Node Network).

Where is my data actually written?
Always once, on the Los Angeles primary. Edges hold read replicas — so reads are local and fast, while writes keep a single source of truth with zero merge conflicts.
What happens if Los Angeles goes down?
Edges keep serving reads, ban checks, attestation, and verification from their local replicas. Writes pause with a clear degraded message, then resume automatically — no manual failover, no dark pages.
Why is there no US-Central node?
Our provider has no US-Central region. Rather than force a bad fit, Central traffic routes to whichever of West or East answers faster — covered without a dedicated box.
Do I need to pick a region in my integration?
No. Clients hit the nearest healthy node automatically. The same verdict and data come back from every node.

Build on infrastructure that stays up

Read the integration docs, see how it survives real attacks, or talk to the team about your region.

Status above reflects the September 24, 2026 DNN (Distributed Node Network, formerly USDNN) launch topology (Los Angeles primary + Hillsboro and Vint Hill replicas). For live incident history, contact the team.