asn.dev

Observed topology

AS201333 NAQUADRIA-AS Naquadria Global ASN

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201333: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6265
AS9002RETN LimitedUnclassifiedIPv4 IPv6238
AS6939Hurricane Electric LLCTransitIPv4 IPv6134
AS24482SG.GSHostingIPv4 IPv613
AS204092Association GRIFONUnclassifiedIPv4 IPv613
AS6696VERIXI SAUnclassifiedIPv410
AS34927iFog GmbHHostingIPv410
AS59919Brainbox S.r.l.ResidentialIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201058Spaziotempo s.r.l.UnclassifiedIPv4812
AS204903FLASHSTART GROUP SRLUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS201058Spaziotempo s.r.l.UnclassifiedIPv4812
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6685
AS9002RETN LimitedUnclassifiedIPv4 IPv6434
AS6939Hurricane Electric LLCTransitIPv4 IPv6274
AS204092Association GRIFONUnclassifiedIPv4 IPv627
AS59919Brainbox S.r.l.ResidentialIPv425
AS6696VERIXI SAUnclassifiedIPv424
AS34927iFog GmbHHostingIPv424
AS24482SG.GSHostingIPv4 IPv613
AS204903FLASHSTART GROUP SRLUnclassifiedIPv41

Provenance

Where this comes from

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