asn.dev

Observed topology

AS15516 DK-DANSKKABELTV DKTV A/S

Residential RIPE Cable/DSL/ISP

Upstreams 14 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 9
Upstream graph Who carries AS15516, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS15516 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS15516: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3292TDC Holding A/SResidentialIPv4 IPv6303
AS20562Broadband Hosting B.V.HostingIPv4 IPv6162
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv613
AS48185team.blue NVUnclassifiedIPv4 IPv613
AS204092Association GRIFONUnclassifiedIPv4 IPv613
AS6696VERIXI SAUnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410
AS37100SEACOM LimitedUnclassifiedIPv410

Transit

Downstream networks

inferred

Networks for which AS15516 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 14

Every AS seen directly next to AS15516 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3292TDC Holding A/SResidentialIPv4 IPv6303
AS20562Broadband Hosting B.V.HostingIPv4 IPv6162
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv613
AS48185team.blue NVUnclassifiedIPv4 IPv613
AS204092Association GRIFONUnclassifiedIPv4 IPv613
AS6696VERIXI SAUnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410
AS37100SEACOM LimitedUnclassifiedIPv410

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.