asn.dev

Observed topology

AS22908 AS22908 - Sixsigma Networks Mexico, S.A. de C.V.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22908: 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
AS174Cogent Communications, LLCTransitIPv4 IPv63,742
AS32098Transtelco IncUnclassifiedIPv4 IPv61,635
AS1299Arelion Sweden ABTransitIPv4 IPv6330
AS198949Radware LtdUnclassifiedIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17249BURSATEC, S.A. DE C.V.UnclassifiedIPv4120
AS64112PIT CHILE SPUnclassifiedIPv4 IPv671
AS46071Pioneer Elabs Ltd.UnclassifiedIPv460
AS22011Sixsigma Networks Mexico, S.A. de C.V.UnclassifiedIPv636
AS8007Servicios Administrados Mexis, S.A. de C.V.UnclassifiedIPv43
AS14249Internet Engine, S.A. de C.V.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv63,749
AS32098Transtelco IncUnclassifiedIPv4 IPv61,916
AS1299Arelion Sweden ABTransitIPv4 IPv6333
AS17249BURSATEC, S.A. DE C.V.UnclassifiedIPv4120
AS64112PIT CHILE SPUnclassifiedIPv4 IPv671
AS46071Pioneer Elabs Ltd.UnclassifiedIPv460
AS198949Radware LtdUnclassifiedIPv460
AS22011Sixsigma Networks Mexico, S.A. de C.V.UnclassifiedIPv636
AS8007Servicios Administrados Mexis, S.A. de C.V.UnclassifiedIPv43
AS14249Internet Engine, S.A. de C.V.UnclassifiedIPv41

Provenance

Where this comes from

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