asn.dev

Observed topology

AS30998 NAL-AS

Hosting AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30998: 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
AS36932unnamedUnclassifiedIPv43,154
AS6939Hurricane Electric LLCTransitIPv42,138
AS37662WIOCC-ASUnclassifiedIPv4 IPv61,644
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6858
AS37148globacom-asUnclassifiedIPv4801
AS37721Virtual-Technologies-Solutions-SAResidentialIPv4 IPv6218

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37088VDT-ASHostingIPv4 IPv6204
AS37480CobranetResidentialIPv4117
AS37125Layer3-UnclassifiedIPv481
AS37714BITFLUXHostingIPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS36932unnamedUnclassifiedIPv43,154
AS6939Hurricane Electric LLCTransitIPv42,138
AS37662WIOCC-ASUnclassifiedIPv4 IPv62,103
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv61,128
AS37148globacom-asUnclassifiedIPv4874
AS37088VDT-ASHostingIPv4 IPv6469
AS37721Virtual-Technologies-Solutions-SAResidentialIPv4 IPv6218
AS37125Layer3-UnclassifiedIPv4 IPv6172
AS37480CobranetResidentialIPv4117
AS37714BITFLUXHostingIPv636

Provenance

Where this comes from

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