asn.dev

Observed topology

AS16082 SPITFIRE Spitfire Network Services Limited

Unclassified AFRINIC

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS16082: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6206
AS174Cogent Communications, LLCTransitIPv4 IPv6158
AS6939Hurricane Electric LLCTransitIPv4 IPv6121
AS9002RETN LimitedUnclassifiedIPv4 IPv637
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv637
AS50304Blix Solutions ASUnclassifiedIPv424
AS24482SG.GSHostingIPv4 IPv613
AS48185team.blue NVUnclassifiedIPv4 IPv613
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv613
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv613

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61093Solution Computers LtdUnclassifiedIPv4118

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6239
AS174Cogent Communications, LLCTransitIPv4 IPv6185
AS6939Hurricane Electric LLCTransitIPv4 IPv6137
AS61093Solution Computers LtdUnclassifiedIPv4118
AS9002RETN LimitedUnclassifiedIPv4 IPv643
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv643
AS50304Blix Solutions ASUnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv615
AS48185team.blue NVUnclassifiedIPv4 IPv615
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv615

All 22 adjacent →

Provenance

Where this comes from

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