asn.dev

Observed topology

AS31510 IKB-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS31510: 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 LLPHostingIPv4119
AS9002RETN LimitedUnclassifiedIPv4 IPv6103
AS174Cogent Communications, LLCTransitIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv650
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv617
AS24482SG.GSHostingIPv4 IPv66
AS34019Hivane AssociationUnclassifiedIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66
AS212024Marc SchmittUnclassifiedIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50180MED-EL Elektromedizinische Geraete GmbHUnclassifiedIPv4 IPv692
AS201759Oesterreichisches Rotes Kreuz, Landesverband TirolUnclassifiedIPv41

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6129
AS3223Voxility LLPHostingIPv4119
AS174Cogent Communications, LLCTransitIPv4 IPv6111
AS50180MED-EL Elektromedizinische Geraete GmbHUnclassifiedIPv4 IPv692
AS6939Hurricane Electric LLCTransitIPv4 IPv668
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv68
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68

Provenance

Where this comes from

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