asn.dev

Observed topology

AS16223 COLUMBUS-PE-TE MAXNET TELECOM, LTD

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16223: 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
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv4 IPv6238
AS9002RETN LimitedUnclassifiedIPv4 IPv6197
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv6109
AS3255LLC EKSINTECHUnclassifiedIPv4103
AS6939Hurricane Electric LLCTransitIPv482
AS3303Swisscom (Schweiz) AGResidentialIPv415
AS24482SG.GSHostingIPv4 IPv613

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44318KOLUMBUS PEUnclassifiedIPv4185
AS216012MAXNET TELECOM, LTDUnclassifiedIPv463
AS59652GOLFSTREAM.NET LLCUnclassifiedIPv426
AS208979Canada Network Group LLCUnclassifiedIPv45

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6288
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv4 IPv6278
AS3255LLC EKSINTECHUnclassifiedIPv4199
AS44318KOLUMBUS PEUnclassifiedIPv4185
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv6131
AS6939Hurricane Electric LLCTransitIPv4101
AS216012MAXNET TELECOM, LTDUnclassifiedIPv463
AS59652GOLFSTREAM.NET LLCUnclassifiedIPv426
AS3303Swisscom (Schweiz) AGResidentialIPv421
AS24482SG.GSHostingIPv4 IPv618

Provenance

Where this comes from

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