01 — Addressing
The map is public
You can see every city, its latency and its status. What each node is called stays internal: a directory of active hostnames is useful to nobody but the people who block them.
9 points of presence · 7 countries · 3 regions
Nine edges.
One origin.
We run a small delivery network and serve every node from the same stack. Static assets are cached at the edge, TLS terminates there, and the origin only wakes up for cache misses. Every edge serves this same page; what differs is only how close it is to you.
The network
Nine cities, nine caches.
Nothing hides behind a single round-robin name. Every edge is measurable and independently reachable — we publish the map, not the hostnames that address it.
9 / 9 healthy · 9 shown
01
fra-01here
Frankfurt DE
EU
12
healthy
02
fra-02here
Frankfurt DE
EU
13
healthy
03
fra-03here
Frankfurt DE
EU
14
healthy
04
cdg-01here
Paris FR
EU
16
healthy
05
waw-01here
Warsaw PL
EU
22
healthy
06
hel-01here
Helsinki FI
EU
26
healthy
07
svo-01here
Moscow RU
EU
34
healthy
08
ist-01here
Istanbul TR
TR
47
healthy
09
buf-01here
Buffalo US
NA
96
healthy
all edges running build edge-2026.11
you are on this edge
health checked every 5 s
Edge model
Small network, strict rules.
Three properties keep nine machines behaving like one — and keep the origin out of the request path.
02 — Caching
Cache close, origin quiet
Assets are immutable at the edge and revalidate against the origin by ETag. Traffic can grow across three continents while origin egress stays flat.
03 — Failure
Health checks, not hope
An edge that misses three checks is withdrawn from the pool within 15 seconds. It returns only after answering ten checks in a row, so a flapping node stays out of rotation.
Why does one page live on nine edges?
Because the network is the product, not the page. Each node publishes the same small set of documents so a request can be answered by the closest machine — and so an answer that comes from any node is the same document. Same page, same headers, same certificate policy, same counters on all nine. If two edges ever disagreed, one of them would be broken.
Under the hood
What an edge returns.
No cookies, no client-side fingerprinting, no JavaScript required to read a byte. The headers say everything.
TLS terminates at the edge1.3 on every node, HTTP/3 advertised via Alt-Svc.
One cache per nodeObjects are regional; a miss revalidates against the origin.
One document, nine edgesThe same page from every city — there is no regional variant to drift out of sync.
$ curl -sI https://bigwig.bond/ HTTP/2 200 server: Caddy content-type: text/html; charset=utf-8 alt-svc: h3=":8001"; ma=2592000 accept-ranges: bytes vary: Accept-Encoding # one document, served from every edge
9points of presence7 countries
96.4%cache hit ratioall edges · 30 d
18 msmedian TTFB, Europep50 · 30 d
99.98%availabilityrolling 30 d
FAQ
Reasonable questions.
Short answers about the network, the hostnames and what the edges actually keep.
Why don't you list the edge hostnames?
We publish the map, not the machine names. Where the edges are, how they perform and what they return is public. What each one is called is routing detail, and a list of it would be a directory of every active node — useful to nobody except the people who block them. The name you arrived on is the only one this page will show you.
Is bigwig edge a public CDN?
No. There is no signup, no pricing page and no customer dashboard. The network serves our own properties and a small set of static assets behind them. Capacity is sized for that, not for resale.
What actually runs on a node?
A TLS terminator, an HTTP/2 + HTTP/3 server and a regional cache — nothing else. No application logic, no databases, no per-user state. That is why a node can be replaced in minutes and why all nine serve the same document.
How is an edge picked for my request?
By DNS. The resolver returns the lowest-latency healthy node for its region, and the client connects straight to that node. There is no manual pinning here; the name you arrived on is the only one this page will show you.
Do the edges keep request logs?
Edges keep aggregate counters (requests, hits, misses, timings). Per-request access lines are rotated within 24 hours and are not kept beyond that window. The edge itself sets no cookies.