asn.dev

Observed topology

AS25098 NETCALIBRE

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25098: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6397
AS174Cogent Communications, LLCTransitIPv4 IPv6152
AS6939Hurricane Electric LLCTransitIPv4 IPv6103
AS20473The Constant Company, LLCHostingIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612
AS33891Core-Backbone GmbHHostingIPv410
AS13030Init7 (Switzerland) Ltd.HostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS577931310 LimitedResidentialIPv4 IPv6563
AS34675Prima Internet Holdings LimitedUnclassifiedIPv457
AS208123SPN Alliance LimitedUnclassifiedIPv457
AS57483Ian ChiltonUnclassifiedIPv45

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6873
AS577931310 LimitedResidentialIPv4 IPv6563
AS174Cogent Communications, LLCTransitIPv4 IPv6327
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS20473The Constant Company, LLCHostingIPv4 IPv661
AS34675Prima Internet Holdings LimitedUnclassifiedIPv457
AS208123SPN Alliance LimitedUnclassifiedIPv457
AS24482SG.GSHostingIPv4 IPv614
AS48185team.blue NVUnclassifiedIPv4 IPv614
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv614

Provenance

Where this comes from

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