asn.dev

Observed topology

AS139883 SPTEL-AS-AP - SPTEL PTE. LTD.

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139883: 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
AS23856SPTEL PTE. LTD.ResidentialIPv4 IPv6353

Transit

Downstream networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS23767A-STARUnclassifiedIPv41,038
AS56039SPH Media LimitedUnclassifiedIPv4488
AS131195SIM HeadquartersUnclassifiedIPv4189
AS23728Republic Polytechnic. Multihoming AS SingaporeUnclassifiedIPv4 IPv6136
AS58885IQON GLOBAL PTE LTDHostingIPv4120
AS45133Singapore PolytechnicUnclassifiedIPv4 IPv6116
AS133535PRIMABANANEN PTE. LTD.UnclassifiedIPv488
AS134407MediaCorp Pte LtdUnclassifiedIPv488
AS21660Baxalta IncorporatedUnclassifiedIPv484
AS9247National Institute of EducationEducationIPv481

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS23856SPTEL PTE. LTD.ResidentialIPv4 IPv63,616
AS23767A-STARUnclassifiedIPv41,038
AS56039SPH Media LimitedUnclassifiedIPv4488
AS131195SIM HeadquartersUnclassifiedIPv4189
AS23728Republic Polytechnic. Multihoming AS SingaporeUnclassifiedIPv4 IPv6136
AS58885IQON GLOBAL PTE LTDHostingIPv4120
AS45133Singapore PolytechnicUnclassifiedIPv4 IPv6116
AS133535PRIMABANANEN PTE. LTD.UnclassifiedIPv488
AS134407MediaCorp Pte LtdUnclassifiedIPv488
AS21660Baxalta IncorporatedUnclassifiedIPv484

Provenance

Where this comes from

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