Observed topology

AS199837 TREPSYSTEMAS

Residential RIPE

Upstreams 10 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS199837: 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
AS47927	WIFIWEB s.r.l.	Unclassified	IPv4	172
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	151
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	78
AS9002	RETN Limited	Unclassified	IPv4	72
AS24482	SG.GS	Hosting	IPv4 IPv6	9
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	8
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	8
AS31543	myNet GmbH	Residential	IPv4	8
AS59919	Brainbox S.r.l.	Residential	IPv4	8
AS29632	Netassist International EOOD	Unclassified	IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS12481	Planetel Nordest SRL	Unclassified	IPv4	27

Adjacency

Adjacent networks

All 11

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

AS	Network	Type	Families	Paths seen
AS47927	WIFIWEB s.r.l.	Unclassified	IPv4	172
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	151
AS9002	RETN Limited	Unclassified	IPv4	93
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	78
AS12481	Planetel Nordest SRL	Unclassified	IPv4	27
AS24482	SG.GS	Hosting	IPv4 IPv6	12
AS59919	Brainbox S.r.l.	Residential	IPv4	11
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	8
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	8
AS31543	myNet GmbH	Residential	IPv4	8

All 11 adjacent →

Provenance

Where this comes from

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