Observed topology

AS152131 INC-AS-AP - ILEAD NETWORK CORPORATION

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152131: 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
AS151354	MCBROAD IT SOLUTIONS	Residential	IPv4	49
AS63927	RISE	Residential	IPv4	15
AS24482	SG.GS	Hosting	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS150806	R. C. Yulo Telephone System, Inc.	Unclassified	IPv4	130
AS131465	Marbel Telephone System, Inc.	Unclassified	IPv4	65
AS137208	ILEAD ICT SOLUTIONS INC	Unclassified	IPv4	65
AS139204	RACITELCOM Inc.	Unclassified	IPv4	65
AS151678	Iriga Telephone Company Inc.	Unclassified	IPv4	65
AS152907	PANAY TELEPHONE CORPORATION II	Unclassified	IPv4	65

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS151354	MCBROAD IT SOLUTIONS	Residential	IPv4	397
AS150806	R. C. Yulo Telephone System, Inc.	Unclassified	IPv4	130
AS63927	RISE	Residential	IPv4	116
AS131465	Marbel Telephone System, Inc.	Unclassified	IPv4	65
AS137208	ILEAD ICT SOLUTIONS INC	Unclassified	IPv4	65
AS139204	RACITELCOM Inc.	Unclassified	IPv4	65
AS151678	Iriga Telephone Company Inc.	Unclassified	IPv4	65
AS152907	PANAY TELEPHONE CORPORATION II	Unclassified	IPv4	65
AS24482	SG.GS	Hosting	IPv4	7

Provenance

Where this comes from

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