asn.dev

Observed topology

AS210232 Pactoo PACTOO SAS

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS210232: 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
AS4455IX Reach LtdUnclassifiedIPv4120
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv699
AS6939Hurricane Electric LLCTransitIPv440
AS31216BSO Network Solutions SASUnclassifiedIPv440
AS39801France IX Services SASUUnclassifiedIPv4 IPv69
AS20766Association "Gitoyen"UnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS43531BSO Network Solutions SASUnclassifiedIPv45

All 11 upstreams →

Transit

Downstream networks

inferred

Networks for which AS210232 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 11

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

ASNetworkTypeFamiliesPaths seen
AS4455IX Reach LtdUnclassifiedIPv4120
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv699
AS6939Hurricane Electric LLCTransitIPv440
AS31216BSO Network Solutions SASUnclassifiedIPv440
AS39801France IX Services SASUUnclassifiedIPv4 IPv69
AS20766Association "Gitoyen"UnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS43531BSO Network Solutions SASUnclassifiedIPv45

All 11 adjacent →

Provenance

Where this comes from

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