Observed topology

AS134187 BSO Network Solutions SAS

Unclassified RIPE NSP

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134187: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS197981	BSO Network Solutions SAS	Unclassified	IPv4	18

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS197981	BSO Network Solutions SAS	Unclassified	IPv4	18
AS6939	Hurricane Electric LLC	Transit	IPv4	12
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	1
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1
AS33891	Core-Backbone GmbH	Hosting	IPv4	1
AS38001	NewMedia Express Pte Ltd	Hosting	IPv4	1
AS132132	MyRepublic Ltd.	Residential	IPv4	1

Provenance

Where this comes from

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