Observed topology

AS31083 Telepoint Telepoint Ltd

Hosting RIPE

Upstreams 3 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 19

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31083: 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
AS57344	Telehouse AD	Residential	IPv4	3,840
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	3
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS25332	Linkos Ltd.	Unclassified	IPv4	177
AS202968	Credissimo JSCo	Unclassified	IPv4	123
AS57122	PSP Bulgaria Ltd.	Unclassified	IPv4	59
AS202309	Radibase EOOD	Unclassified	IPv4	13
AS51605	XS Software JSC	Hosting	IPv4	2

Adjacency

Adjacent networks

All 19

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

AS	Network	Type	Families	Paths seen
AS57344	Telehouse AD	Residential	IPv4	4,140
AS25332	Linkos Ltd.	Unclassified	IPv4	177
AS202968	Credissimo JSCo	Unclassified	IPv4	123
AS57122	PSP Bulgaria Ltd.	Unclassified	IPv4	59
AS6939	Hurricane Electric LLC	Transit	IPv4	26
AS48452	Telco power Ltd	Residential	IPv4	19
AS202309	Radibase EOOD	Unclassified	IPv4	19
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	6
AS174	Cogent Communications, LLC	Transit	IPv4	4
AS2914	NTT America, Inc.	Transit	IPv4	4

All 19 adjacent →

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.