asn.dev

Observed topology

AS198781 G3NS

Unclassified RIPE NSP

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS198781: 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
AS6939Hurricane Electric LLCTransitIPv41,391
AS3491PCCW Global (HK) Ltd.TransitIPv4138
AS1299Arelion Sweden ABTransitIPv4103
AS174Cogent Communications, LLCTransitIPv460
AS34549meerfarbig GmbH & Co. KGHostingIPv460
AS24482SG.GSHostingIPv4 IPv630
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv623
AS48185team.blue NVUnclassifiedIPv4 IPv623
AS3741Dimension DataUnclassifiedIPv421
AS37100SEACOM LimitedUnclassifiedIPv420

All 24 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8791Kerv Experience LimitedUnclassifiedIPv4159

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv41,505
AS8791Kerv Experience LimitedUnclassifiedIPv4159
AS3491PCCW Global (HK) Ltd.TransitIPv4138
AS1299Arelion Sweden ABTransitIPv4103
AS174Cogent Communications, LLCTransitIPv475
AS34549meerfarbig GmbH & Co. KGHostingIPv469
AS24482SG.GSHostingIPv4 IPv633
AS3741Dimension DataUnclassifiedIPv424
AS37100SEACOM LimitedUnclassifiedIPv423
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv623

All 25 adjacent →

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.