asn.dev

Observed topology

AS38278 OTSB-AS-AP Orient Telecoms Sdn. Bhd

Unclassified APNIC

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS38278: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,035
AS174Cogent Communications, LLCTransitIPv4136
AS9304HGC Global Communications LimitedHostingIPv4 IPv6112
AS9498BHARTI Airtel Ltd.MobileIPv490
AS24482SG.GSHostingIPv4 IPv624
AS38001NewMedia Express Pte LtdHostingIPv4 IPv623
AS5511Orange S.A.TransitIPv422
AS17639Converge ICT Solutions Inc.UnclassifiedIPv422
AS55720Gigabit Hosting Sdn BhdHostingIPv421
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv66

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150712Weber Meyer Sdn BhdUnclassifiedIPv464
AS134066Lynuxtel Malaysia Sdn BhdHostingIPv459

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,081
AS174Cogent Communications, LLCTransitIPv4158
AS9498BHARTI Airtel Ltd.MobileIPv4117
AS9304HGC Global Communications LimitedHostingIPv4 IPv6112
AS150712Weber Meyer Sdn BhdUnclassifiedIPv464
AS134066Lynuxtel Malaysia Sdn BhdHostingIPv459
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv431
AS24482SG.GSHostingIPv4 IPv625
AS5511Orange S.A.TransitIPv424
AS38001NewMedia Express Pte LtdHostingIPv4 IPv623

All 15 adjacent →

Provenance

Where this comes from

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