asn.dev

Observed topology

AS48503 TELE2-KZ Mobile Telecom-Service LLP

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48503: 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
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv618,520
AS35168TNS-Plus LLPUnclassifiedIPv4 IPv69,802
AS35104QMOBILE JSCUnclassifiedIPv4 IPv62,996
AS41798JSC TranstelecomUnclassifiedIPv4 IPv61,954

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29555Mobile Telecom-Service LLPUnclassifiedIPv4 IPv67,853

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv623,347
AS35168TNS-Plus LLPUnclassifiedIPv4 IPv612,046
AS29555Mobile Telecom-Service LLPUnclassifiedIPv4 IPv67,853
AS35104QMOBILE JSCUnclassifiedIPv4 IPv62,996
AS41798JSC TranstelecomUnclassifiedIPv4 IPv62,740

Provenance

Where this comes from

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