From our Copenhagen node on AS42708 (Glesys), typical ICMP round-trip times to well-peered destinations run roughly like this: Copenhagen to Hamburg around 17 ms, to Stockholm around 20 ms, to Amsterdam around 22 ms, to London around 25 ms, to Frankfurt around 28–35 ms, to Warsaw around 35 ms, to New York around 90–105 ms. These figures assume direct transit or peering paths. Routes through congested or indirect carriers can push those numbers 15–30 ms higher.

Denmark is geographically compact, so intra-country ping times are low — most Danish residential users are reachable under 15 ms from a Copenhagen data center. The more interesting use of a ping test from Denmark is understanding how your server looks to the broader Nordic and Central European region, since Copenhagen sits equidistant between Scandinavia and northern Germany.

ICMP is commonly deprioritized or rate-limited at firewall level. A high RTT in the ping result alone does not confirm real application latency — compare against a TCP check on the same host's service port to determine whether the ICMP path reflects actual application behavior. Consistent packet loss across both ICMP and TCP is a more reliable indicator of actual connectivity trouble between Denmark and the target.

Copenhagen is the primary internet hub for Denmark and functions as a routing crossroads between Scandinavia, the Baltic region, and Central Europe. Netnod operates an IX in Copenhagen alongside its Stockholm infrastructure, and the Danish Internet Exchange (DIX) provides a community-run peering alternative. Together these make Copenhagen a well-connected location for networks that need to peer with Nordic and Baltic ISPs without routing through Frankfurt or Amsterdam first.

Denmark bridges the Scandinavian peninsula and the European mainland through its land connection via Jutland into Germany. This geography means Copenhagen has low-latency paths to both Stockholm (around 20 ms) and Hamburg (around 17 ms), giving it natural reach in both directions. Cross-Øresund links to Malmö keep latency to southern Sweden well under 10 ms. Several submarine cables connect Denmark to the UK, Norway, and the Baltic states, providing path diversity for international traffic.

Our Copenhagen probe node runs on AS42708, operated by Glesys AB. Glesys is a Swedish-Nordic hosting and infrastructure provider with data center presence in Stockholm, Gothenburg, and Copenhagen. The Glesys Copenhagen location at their Glostrup Municipality facility gives the probe node good upstream connectivity to the broader Nordic hosting ecosystem. AS42708 announces routes via Netnod and has transit agreements that cover both Nordic and Central European destinations.

The Danish hosting market includes both local operators and international providers. TDC (AS3292) is the incumbent national carrier and operates a significant share of the Danish backbone. Telia (AS1299) and Telenor (AS2119) provide additional transit capacity. Bandwidth-intensive traffic — video streaming, cloud workloads — often routes via Equinix Copenhagen, where CDNs and cloud providers maintain local cache or edge nodes to serve Danish users without pulling content from more distant data centers.

For operators targeting Danish users, Copenhagen is the natural test location. A server hosted in Copenhagen or peered into DIX or Netnod CPH should reach most Danish residential users well under 15 ms. A server in Frankfurt adds 35–45 ms for Danish users before accounting for any last-mile variation. CDN edge placement in Copenhagen or nearby Malmö makes a material difference for latency-sensitive applications serving the Danish market.