asn.dev

Observed topology

AS57487 MIXTELECOM-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57487: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6317
AS31133PJSC MegaFonMobileIPv4 IPv6203
AS6939Hurricane Electric LLCTransitIPv4 IPv692
AS24482SG.GSHostingIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS49673Truenetwork LLCUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42889Metavira LLCUnclassifiedIPv459
AS43299Limited Company TelecontactUnclassifiedIPv435
AS207104"BiZone" LLCUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6373
AS31133PJSC MegaFonMobileIPv4 IPv6244
AS6939Hurricane Electric LLCTransitIPv4 IPv698
AS42889Metavira LLCUnclassifiedIPv459
AS43299Limited Company TelecontactUnclassifiedIPv435
AS24482SG.GSHostingIPv4 IPv614
AS207104"BiZone" LLCUnclassifiedIPv412
AS49673Truenetwork LLCUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv48

Provenance

Where this comes from

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