asn.dev

Observed topology

AS200950 CALIBOURNETWORK _

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200950: 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
AS197071active 1 GmbHUnclassifiedIPv4 IPv6408
AS44592SkyLink Data Center BVHostingIPv4 IPv698
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv697
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv611
AS213438ColocaTel Inc.UnclassifiedIPv4 IPv611
AS401753BIXCE IncUnclassifiedIPv4 IPv611
AS56662Marcin GondekUnclassifiedIPv610
AS206499LOCIX LIMITEDUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206540BEANSUMMERHOST NEXTGEN SHED HOSTING SOLUTIONS LLCUnclassifiedIPv676
AS205591Alyx FunkenUnclassifiedIPv674
AS208753Marco d'AngeloUnclassifiedIPv673

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS197071active 1 GmbHUnclassifiedIPv4 IPv6542
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv6143
AS44592SkyLink Data Center BVHostingIPv4 IPv6126
AS206540BEANSUMMERHOST NEXTGEN SHED HOSTING SOLUTIONS LLCUnclassifiedIPv676
AS205591Alyx FunkenUnclassifiedIPv674
AS208753Marco d'AngeloUnclassifiedIPv673
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS401753BIXCE IncUnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv614
AS56662Marcin GondekUnclassifiedIPv614

All 12 adjacent →

Provenance

Where this comes from

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