asn.dev

Observed topology

AS4773 MOBILEONELTD-AS-AP MobileOne Ltd. MobileInternet Service Provider Singapore

Mobile APNIC

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS4773: 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,276
AS1299Arelion Sweden ABTransitIPv4 IPv61,015
AS2914NTT America, Inc.TransitIPv4 IPv6903
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4449
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6416
AS4657StarHub LtdResidentialIPv4 IPv6320
AS24482SG.GSHostingIPv4 IPv692
AS38001NewMedia Express Pte LtdHostingIPv4 IPv692
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv690
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv658

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132915M1 Limited/ Next Generation Broadband NetworkUnclassifiedIPv636

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,301
AS1299Arelion Sweden ABTransitIPv4 IPv61,019
AS2914NTT America, Inc.TransitIPv4 IPv6905
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4449
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6416
AS4657StarHub LtdResidentialIPv4 IPv6320
AS24482SG.GSHostingIPv4 IPv693
AS38001NewMedia Express Pte LtdHostingIPv4 IPv693
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv691
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv659

Provenance

Where this comes from

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