Observed topology

AS205019 G1SAT G1SAT B.V.

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205019: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	1,101
AS174	Cogent Communications, LLC	Transit	IPv4	1,087
AS4455	IX Reach Ltd	Unclassified	IPv4	288
AS31216	BSO Network Solutions SAS	Unclassified	IPv4	80
AS24785	Broadband Hosting B.V.	Hosting	IPv4	45
AS43531	BSO Network Solutions SAS	Unclassified	IPv4	7

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,101
AS174	Cogent Communications, LLC	Transit	IPv4	1,087
AS4455	IX Reach Ltd	Unclassified	IPv4	288
AS31216	BSO Network Solutions SAS	Unclassified	IPv4	80
AS24785	Broadband Hosting B.V.	Hosting	IPv4	45
AS43531	BSO Network Solutions SAS	Unclassified	IPv4	7

Provenance

Where this comes from

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