Each PoP terminates client connections and falls back to its regional shield on a cache miss. Capacity is added per region rather than per customer.
| Code | Location | Region | Shield | State |
|---|---|---|---|---|
sg01 | Singapore | Southeast Asia | ap-shield-1 | Operational |
hkg01 | Hong Kong | East Asia | ap-shield-1 | Operational |
fra02 | Frankfurt | Europe | eu-shield-1 | Operational |
ams01 | Amsterdam | Europe | eu-shield-1 | Operational |
iad03 | Ashburn | North America | na-shield-1 | Operational |
We maintain an open peering policy at regional exchanges and accept bilateral sessions with networks that keep consistent routing policy and up-to-date contact records.
| Requirement | Detail |
|---|---|
| Prefix filtering | RPKI ROV, plus IRR-derived filters refreshed daily |
| Contact | 24/7 NOC role account, kept current in PeeringDB |
| MD5 | Optional, supported on request |
| Traffic ratio | Not enforced |
A miss at the edge is resolved by the regional shield, which deduplicates concurrent requests for the same object. Only the shield talks to a customer origin.
client -> sg01 (edge) cache lookup, TLS termination
-> ap-shield-1 request collapsing, conditional fetch
-> customer origin single upstream request