Tech & Innovation
Content tailored to your region via Fastly Compute geolocation
Edge Computing Guide
How sub-millisecond latency transforms real-time APIs and WebSocket connections across North American POPs.
Compute@Edge Performance
Benchmarking WASM execution at Fastly POPs vs traditional CDN edge workers.
API Gateway Patterns
Route, transform, and authorize API traffic at the edge before it touches your origin.
Edge Inspection Dashboard
Live🌍 Geolocation Headers
country_codeUS
country_nameunited states
citycolumbus
regionOH
continentNA
latitude40.0400
longitude-82.8600
postal_code43230
utc_offset-400
as_nameamazon.com inc.
conn_speedbroadband
conn_typewired
📱 Device Detection
hardware_typebot
brandN/A
modelCrawler
is_mobilefalse
is_desktopfalse
is_tabletfalse
is_touchscreenfalse
is_bottrue
client_ip216.73.216.186
layout_modedesktop
Client Request
→
Fastly POP
→
Geo Lookup
→
Device Detect
→
HTML Compiled
→
Response
Entire request lifecycle executes at the edge — no origin server involved
This HTML was compiled natively at the Fastly edge using Compute services.
Geolocation and device data were resolved at the POP in sub-millisecond time —
zero origin latency, zero round-trips, zero cold starts.