asn.dev

Observed topology

AS28546 Servnet Mexico, S.A. de C.V.

Hosting LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28546: 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
AS28458S DE RL DE CVUnclassifiedIPv41,033
AS32098Transtelco IncUnclassifiedIPv4 IPv6751
AS174Cogent Communications, LLCTransitIPv4460
AS11172S. de R.L. de C.V.UnclassifiedIPv4 IPv6300

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15107Financiero BancomerUnclassifiedIPv4126

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28458S DE RL DE CVUnclassifiedIPv41,131
AS32098Transtelco IncUnclassifiedIPv4 IPv6763
AS174Cogent Communications, LLCTransitIPv4476
AS11172S. de R.L. de C.V.UnclassifiedIPv4 IPv6300
AS15107Financiero BancomerUnclassifiedIPv4126

Provenance

Where this comes from

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