Halcyon Edge

Points of presence

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.

CodeLocationRegionShieldState
sg01SingaporeSoutheast Asiaap-shield-1Operational
hkg01Hong KongEast Asiaap-shield-1Operational
fra02FrankfurtEuropeeu-shield-1Operational
ams01AmsterdamEuropeeu-shield-1Operational
iad03AshburnNorth Americana-shield-1Operational

Peering

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.

RequirementDetail
Prefix filteringRPKI ROV, plus IRR-derived filters refreshed daily
Contact24/7 NOC role account, kept current in PeeringDB
MD5Optional, supported on request
Traffic ratioNot enforced

Shield topology

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