asn.dev

Observed topology

AS23856 SPTEL-AS-AP - SPTEL PTE. LTD.

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23856: 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
AS23764CTGNetUnclassifiedIPv4 IPv6324
AS9002RETN LimitedUnclassifiedIPv4 IPv6153
AS3356Level 3 Parent, LLCTransitIPv4 IPv6112
AS4657StarHub LtdResidentialIPv4 IPv663
AS134078NETPLUZ HOLDINGS PRIVATE LIMITEDUnclassifiedIPv444
AS24482SG.GSHostingIPv4 IPv612
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv612
AS38001NewMedia Express Pte LtdHostingIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139883SPTEL PTE. LTD.UnclassifiedIPv4 IPv6353

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS139883SPTEL PTE. LTD.UnclassifiedIPv4 IPv63,729
AS23764CTGNetUnclassifiedIPv4 IPv62,052
AS3356Level 3 Parent, LLCTransitIPv4 IPv6728
AS9002RETN LimitedUnclassifiedIPv4 IPv6694
AS4657StarHub LtdResidentialIPv4 IPv6593
AS134078NETPLUZ HOLDINGS PRIVATE LIMITEDUnclassifiedIPv4153
AS24482SG.GSHostingIPv4 IPv684
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv677
AS38001NewMedia Express Pte LtdHostingIPv4 IPv671
AS17639Converge ICT Solutions Inc.UnclassifiedIPv44

Provenance

Where this comes from

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