asn.dev

Observed topology

AS197248 DRAVANET-AS

Hosting ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197248: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv61,436
AS6939Hurricane Electric LLCTransitIPv466
AS33891Core-Backbone GmbHHostingIPv446

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213869WiNext Kft.UnclassifiedIPv4 IPv6112
AS214175Pecsi EgyhazmegyeUnclassifiedIPv460
AS196970Langaton Hungary KftUnclassifiedIPv411
AS206814SCI-Network pInc.UnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv61,932
AS21229Dravanet Co Ltd.UnclassifiedIPv4310
AS213869WiNext Kft.UnclassifiedIPv4 IPv6112
AS6939Hurricane Electric LLCTransitIPv466
AS214175Pecsi EgyhazmegyeUnclassifiedIPv460
AS33891Core-Backbone GmbHHostingIPv446
AS196970Langaton Hungary KftUnclassifiedIPv411
AS206814SCI-Network pInc.UnclassifiedIPv43

Provenance

Where this comes from

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