asn.dev

Observed topology

AS29030 Telekabel TELECABEL PLC

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS29030: 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
AS9002RETN LimitedUnclassifiedIPv4210
AS31287IPACCT CABLE LtdUnclassifiedIPv4210
AS34224Neterra Ltd.UnclassifiedIPv4111
AS57463NetIX Communications JSCUnclassifiedIPv498
AS6939Hurricane Electric LLCTransitIPv484
AS34549meerfarbig GmbH & Co. KGHostingIPv428
AS20764CJSC RASCOMUnclassifiedIPv414
AS24482SG.GSHostingIPv414
AS34019Hivane AssociationUnclassifiedIPv414
AS34927iFog GmbHHostingIPv414

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50368Bulsat Ltd.UnclassifiedIPv488

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS31287IPACCT CABLE LtdUnclassifiedIPv4230
AS9002RETN LimitedUnclassifiedIPv4226
AS57463NetIX Communications JSCUnclassifiedIPv4118
AS34224Neterra Ltd.UnclassifiedIPv4111
AS50368Bulsat Ltd.UnclassifiedIPv488
AS6939Hurricane Electric LLCTransitIPv484
AS34549meerfarbig GmbH & Co. KGHostingIPv436
AS24482SG.GSHostingIPv418
AS34927iFog GmbHHostingIPv418
AS50673Serverius Holding B.V.UnclassifiedIPv418

All 15 adjacent →

Provenance

Where this comes from

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