asn.dev

Observed topology

AS31103 KEYWEB-AS Keyweb AG

Hosting RIPE NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS31103: 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
AS3223Voxility LLPHostingIPv41,082
AS33891Core-Backbone GmbHHostingIPv4 IPv6633
AS174Cogent Communications, LLCTransitIPv4206
AS6939Hurricane Electric LLCTransitIPv4 IPv6205
AS34549meerfarbig GmbH & Co. KGHostingIPv4108
AS48362Stadtwerke FeldkirchResidentialIPv436
AS3303Swisscom (Schweiz) AGResidentialIPv412
AS6797GlobalConnect ABUnclassifiedIPv412
AS8551Bezeq International Ltd.UnclassifiedIPv412
AS12779IT.Gate S.p.A.UnclassifiedIPv412

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202252OCKNet GmbHUnclassifiedIPv460
AS209610OCKNet GmbHUnclassifiedIPv460
AS210304OCKNet GmbHUnclassifiedIPv460

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS3223Voxility LLPHostingIPv41,082
AS33891Core-Backbone GmbHHostingIPv4 IPv6705
AS174Cogent Communications, LLCTransitIPv4245
AS6939Hurricane Electric LLCTransitIPv4 IPv6232
AS34549meerfarbig GmbH & Co. KGHostingIPv4117
AS202252OCKNet GmbHUnclassifiedIPv460
AS209610OCKNet GmbHUnclassifiedIPv460
AS210304OCKNet GmbHUnclassifiedIPv460
AS48362Stadtwerke FeldkirchResidentialIPv439
AS3303Swisscom (Schweiz) AGResidentialIPv415

All 19 adjacent →

Provenance

Where this comes from

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