bgpreport

Network · data from 2026-11-12

AS29033 Eckoh UK

Registry name: ECKOH Eckoh UK Limited, GB · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS29033, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29033, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
81.20.32.0/20 Valid RIR databaseRIPE 672 100% 67
185.129.176.0/22 Valid RIR databaseRIPE 671 100% 67
2a00:1fd0:ecc2::/48 Valid RIR databaseRIPE 636 100% 67
2a00:1fd0:ec00::/48 Valid RIR databaseRIPE 635 100% 68
2a00:1fd0:ecc0::/48 Valid RIR databaseRIPE 635 100% 67
2a00:1fd0:ecc1::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS29033's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • Route object: not announced11

Route objects not announced

Route objects with origin AS29033 whose prefix no peer sees AS29033 announce. Many are kept on purpose (backup routes, space announced only in some places).

81.20.40.0/24RIPEValid
81.20.41.0/24RIPEValid
81.20.42.0/24RIPEInvalid: maxLength
81.20.43.0/24RIPEInvalid: maxLength
185.129.177.0/24RIPEInvalid: maxLength
185.129.178.0/24RIPEInvalid: maxLength
2a00:1fd0::/29RIPENo ROA
2a00:1fd0::/32RIPENo ROA
2a00:1fd0:ae00::/40RIPEValid
2a00:1fd0:ae41::/48RIPEValid
2a00:1fd0:ae42::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.