Observed topology
AS134152 XTSB-AS-AP XMT Technologies Sdn Bhd
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS134152: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9930 | TIME dotCom Berhad No. 14, Jalan Majistret U126 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia | Unclassified | IPv4 IPv6 | 288 |
| AS4788 | TM TECHNOLOGY SERVICES SDN. BHD. | Mobile | IPv4 | 84 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 17 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 6 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS134152 was observed as the last hop before the origin, meaning it appears to provide them transit.
No downstream observed. This network does not appear to carry transit for anyone.
Adjacency
Adjacent networks
Every AS seen directly next to AS134152 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9930 | TIME dotCom Berhad No. 14, Jalan Majistret U126 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia | Unclassified | IPv4 IPv6 | 288 |
| AS4788 | TM TECHNOLOGY SERVICES SDN. BHD. | Mobile | IPv4 | 84 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 17 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 6 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 5 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-27 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.06M 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.