asn.dev

Observed topology

AS200062 OPTITRUST

Hosting RIPE

Upstreams 16 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 15
Adjacent (IPv6) 12
Upstream graph Who carries AS200062, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS200062 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS200062: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6203
AS174Cogent Communications, LLCTransitIPv4 IPv694
AS6939Hurricane Electric LLCTransitIPv4 IPv656
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv68
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68
AS6797GlobalConnect ABUnclassifiedIPv47
AS12779IT.Gate S.p.A.UnclassifiedIPv47

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213410OakHost OUUnclassifiedIPv4 IPv6152

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6269
AS213410OakHost OUUnclassifiedIPv4 IPv6152
AS174Cogent Communications, LLCTransitIPv4 IPv6124
AS6939Hurricane Electric LLCTransitIPv4 IPv676
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv631
AS24482SG.GSHostingIPv4 IPv611
AS34019Hivane AssociationUnclassifiedIPv4 IPv611
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv611
AS212024Marc SchmittUnclassifiedIPv4 IPv611
AS6797GlobalConnect ABUnclassifiedIPv49

All 17 adjacent →

Provenance

Where this comes from

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