asn.dev

Observed topology

AS213822 BUIJSIT

Unclassified RIPE Content

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS213822: 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
AS39637ADES BVUnclassifiedIPv4 IPv640
AS24785Broadband Hosting B.V.HostingIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv4 IPv619
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62
AS48185team.blue NVUnclassifiedIPv4 IPv62
AS204092Association GRIFONUnclassifiedIPv4 IPv62
AS6696VERIXI SAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS39637ADES BVUnclassifiedIPv4 IPv640
AS24785Broadband Hosting B.V.HostingIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv4 IPv619
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62
AS48185team.blue NVUnclassifiedIPv4 IPv62
AS204092Association GRIFONUnclassifiedIPv4 IPv62
AS6696VERIXI SAUnclassifiedIPv41

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.