asn.dev

Observed topology

AS13178 DIGCOMM LLC "Real-net"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13178: 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
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv6450
AS29076Citytelecom LLCHostingIPv6161
AS1299Arelion Sweden ABTransitIPv4 IPv6131
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6113
AS31133PJSC MegaFonMobileIPv450
AS24482SG.GSHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS25478iHome LLCUnclassifiedIPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15552LLC "Real-net"UnclassifiedIPv4 IPv6718
AS198076Lite Group Ltd.UnclassifiedIPv453

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv6955
AS15552LLC "Real-net"UnclassifiedIPv4 IPv6718
AS1299Arelion Sweden ABTransitIPv4 IPv6254
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6246
AS29076Citytelecom LLCHostingIPv6183
AS198076Lite Group Ltd.UnclassifiedIPv453
AS31133PJSC MegaFonMobileIPv450
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv435
AS24482SG.GSHostingIPv422
AS37721Virtual Technologies & SolutionsResidentialIPv422

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.