asn.dev

Observed topology

AS199248 NUMLOG

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS199248: 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
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6249
AS49434FBW NETWORKS SASUnclassifiedIPv4132
AS6939Hurricane Electric LLCTransitIPv4 IPv624
AS9002RETN LimitedUnclassifiedIPv62
AS24482SG.GSHostingIPv4 IPv62
AS33891Core-Backbone GmbHHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv62
AS5405Inter.link GmbHUnclassifiedIPv41
AS12779IT.Gate S.p.A.UnclassifiedIPv41

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210839STJ SASUnclassifiedIPv460

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6294
AS49434FBW NETWORKS SASUnclassifiedIPv4132
AS210839STJ SASUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv4 IPv635
AS24482SG.GSHostingIPv4 IPv63
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63
AS9002RETN LimitedUnclassifiedIPv62
AS20766Association "Gitoyen"UnclassifiedIPv42
AS33891Core-Backbone GmbHHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62

All 17 adjacent →

Provenance

Where this comes from

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