asn.dev

Observed topology

AS219331 FreePKT Thomas BOUZIN

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS219331: 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
AS6939Hurricane Electric LLCTransitIPv6138
AS205941Lungu Stefan GabrielUnclassifiedIPv633
AS214757Jakub KrsaUnclassifiedIPv621
AS215638Cilix LimitedResidentialIPv612
AS24482SG.GSHostingIPv63
AS50300CustodianDC LimitedUnclassifiedIPv63
AS48185team.blue NVUnclassifiedIPv62
AS202580A-Systems Sp. z o.o.UnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205305Gabriel PeronUnclassifiedIPv637
AS207445Vincent MarounUnclassifiedIPv610
AS41047Bart VranckenUnclassifiedIPv62

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6172
AS205305Gabriel PeronUnclassifiedIPv637
AS205941Lungu Stefan GabrielUnclassifiedIPv633
AS214757Jakub KrsaUnclassifiedIPv623
AS215638Cilix LimitedResidentialIPv619
AS207445Vincent MarounUnclassifiedIPv610
AS24482SG.GSHostingIPv66
AS50300CustodianDC LimitedUnclassifiedIPv66
AS41047Bart VranckenUnclassifiedIPv62
AS48185team.blue NVUnclassifiedIPv62

All 11 adjacent →

Provenance

Where this comes from

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