asn.dev

Observed topology

AS205845 PLANISWARE Planisware SA

Hosting RIPE Content

Upstreams 15 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 10
Upstream graph Who carries AS205845, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS205845 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS35280F5 Networks SARLHostingIPv4 IPv6159
AS1299Arelion Sweden ABTransitIPv4 IPv6105
AS3320Deutsche Telekom AGMobileIPv4 IPv627
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv621
AS1836green.ch AGResidentialIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS33891Core-Backbone GmbHHostingIPv46

All 15 upstreams →

Transit

Downstream networks

inferred

Networks for which AS205845 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

All 15

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

ASNetworkTypeFamiliesPaths seen
AS35280F5 Networks SARLHostingIPv4 IPv6159
AS1299Arelion Sweden ABTransitIPv4 IPv6105
AS3320Deutsche Telekom AGMobileIPv4 IPv627
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv621
AS1836green.ch AGResidentialIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS33891Core-Backbone GmbHHostingIPv46

All 15 adjacent →

Provenance

Where this comes from

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