Observed topology

AS137535 JTIP-AS-AP JT TELECOM INTERNATIONAL PTE.LTD.

Unclassified APNIC Cable/DSL/ISP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

Upstream graph Who carries AS137535, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS137535 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS137535: 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
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4	3,289
AS18186	Nebula Global LLC	Hosting	IPv4	1,495
AS7607	JT TELECOM INTERNATIONAL PTE.LTD.	Unclassified	IPv4	120
AS24482	SG.GS	Hosting	IPv4	50
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	46
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	43

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS140227	Hong Kong Communications International Co., Limited	Unclassified	IPv4	9

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4	3,347
AS18186	Nebula Global LLC	Hosting	IPv4	1,495
AS7607	JT TELECOM INTERNATIONAL PTE.LTD.	Unclassified	IPv4	120
AS140227	Hong Kong Communications International Co., Limited	Unclassified	IPv4	58
AS24482	SG.GS	Hosting	IPv4	50
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	46
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	43

Provenance

Where this comes from

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