bgpreport

Network · data from 2026-11-12

AS211077 HO-LECN-DC01 UK Home Office (The Secretary of State for the Home Department)

Registry name: HO-LECN-DC01 UK Home Office (The Secretary of State for the Home Department), GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211077, 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.
51.64.9.0/24 No ROA RIR databaseRIPE 651 97% 67
51.64.254.0/24 No ROA RIR databaseRIPE 651 97% 67

AS-SET

AS211077 isn't in PeeringDB, where networks name their 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 3 are in fix.csv.

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none51.64.9.0/24No ROA covers it. Add a ROA for AS211077, maxLength 24.651 of 673
ROA: none51.64.254.0/24No ROA covers it. Add a ROA for AS211077, maxLength 24.651 of 673

Route objects not announced

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

51.64.0.0/16RIPENo ROA

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.