Halcyon Edge
SG01 · operational

Singapore edge, close to the request.

SG01 terminates TLS and serves cached objects for customer origins across Southeast Asia. It is one point of presence in the Halcyon Edge delivery network — anycast in front, regional shielding behind.

Edge documentationNetwork map

TLS 1.3 termination

Session resumption and OCSP stapling are handled at the edge. Certificates are issued and rotated automatically; customer keys never leave the origin.

HTTP/2 and HTTP/3

Multiplexed delivery with configurable stream concurrency. Clients that do not negotiate h3 fall back to h2 transparently.

Origin shielding

Regional shields collapse concurrent misses into a single upstream fetch, so an origin sees one request instead of a hundred.

Stale-while-revalidate

Objects continue to be served from cache while a background revalidation runs, keeping p99 flat during origin hiccups.

Purge API

Tag-based and prefix-based invalidation propagate across the fleet in a few seconds. Purges are idempotent and safe to retry.

Structured logs

Per-request JSON lines with cache disposition, upstream timing and TLS parameters, streamed to an S3-compatible bucket.

This point of presence

SG01 is deployed in a carrier-neutral facility in Singapore and peers regionally. Figures below describe the node configuration, not a service-level guarantee.

PropertyValue
PoP codesg01
RegionSoutheast Asia (Singapore)
ProtocolsHTTP/1.1, HTTP/2, HTTP/3 (QUIC)
TLS1.2 and 1.3, ECDSA P-256 leaf
Cache tierNVMe, two-tier with regional shield
StatusOperational
Checked

Health for this node is exposed at /healthz and returns a plain-text token for automated probes.