asn.dev

Observed topology

AS24679 SSERV-AS kyberio GmbH

Hosting RIPE NSP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS24679: 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
AS9136Wobcom GmbHResidentialIPv4541
AS3356Level 3 Parent, LLCTransitIPv4 IPv6261
AS6939Hurricane Electric LLCTransitIPv4 IPv6166
AS6797GlobalConnect ABUnclassifiedIPv4 IPv681
AS3320Deutsche Telekom AGMobileIPv457
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv616
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv616
AS212024Marc SchmittUnclassifiedIPv4 IPv616
AS213241TECHIT.BE SRLResidentialIPv4 IPv616

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44780kyberio GmbHUnclassifiedIPv4 IPv6131
AS210909Tutao GmbHUnclassifiedIPv4 IPv647
AS209347Freifunk HannoverUnclassifiedIPv636
AS204867Lightning Wire Labs GmbHUnclassifiedIPv69

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS9136Wobcom GmbHResidentialIPv4554
AS3356Level 3 Parent, LLCTransitIPv4 IPv6292
AS6939Hurricane Electric LLCTransitIPv4 IPv6279
AS44780kyberio GmbHUnclassifiedIPv4 IPv6131
AS6797GlobalConnect ABUnclassifiedIPv4 IPv695
AS3320Deutsche Telekom AGMobileIPv461
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv653
AS210909Tutao GmbHUnclassifiedIPv4 IPv647
AS209347Freifunk HannoverUnclassifiedIPv636
AS24482SG.GSHostingIPv4 IPv622

Provenance

Where this comes from

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