bgpreport

Network · data from 2026-11-12

AS212128 HORIZON LLC "HORIZON"

Registry name: HORIZON LLC "HORIZON", RU · not in PeeringDB

8IPv4 routes 62.5% RPKI valid · 100.0% with a route object
19IPv6 routes 47.4% RPKI valid · 94.7% with a route object
1RPKI invalid 1 origin · 0 maxLength
12No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
24Route objects not announced registered with origin AS212128, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS212128, 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.
2a09:54c6:a100::/48 Invalid: origin None 4 1%low visibility 2
91.195.132.0/23 No ROA RIR databaseRIPE 673 100% 66
91.220.157.0/24 No ROA RIR databaseRIPE 673 100% 66
194.165.2.0/23 No ROA RIR databaseRIPE 673 100% 66
2a09:6906::/32 No ROA RIR databaseRIPE 635 100% 67
2a11:bcc0::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc1::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc2::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc3::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc4::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc5::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc6::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:bcc7::/32 No ROA RIR databaseRIPE 633 100% 67
46.161.4.0/22 Valid RIR databaseRIPE 673 100% 66
89.19.219.0/24 Valid RIR databaseRIPE 673 100% 66
147.45.128.0/22 Valid RIR databaseRIPE 673 100% 66
176.103.83.0/24 Valid RIR databaseRIPE 673 100% 66
81.19.138.0/24 Valid RIR databaseRIPE 672 100% 66
2a0f:6284:9::/48 Valid RIR databaseRIPE 635 100% 67
2a10:cbc0::/32 Valid RIR databaseRIPE 633 100% 67
2a10:cbc1::/32 Valid RIR databaseRIPE 633 100% 67
2a10:cbc5::/32 Valid RIR databaseRIPE 633 100% 67
2a10:cbc7::/32 Valid RIR databaseRIPE 633 100% 67
2a11:e380::/32 Valid RIR databaseRIPE 633 100% 67
2a11:e382::/32 Valid RIR databaseRIPE 633 100% 67
2a11:e387::/32 Valid RIR databaseRIPE 633 100% 67
2a13:7e03::/32 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS212128 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 38 are in fix.csv.

  • ROA: origin1
  • ROA: none12
  • Route object: none1
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: origin2a09:54c6:a100::/48ROAs covering it name AS402970, not AS212128. If AS212128 should announce it, add a ROA for AS212128.4 of 636
Route object: none2a09:54c6:a100::/48No route object for it. Add a route object with origin AS212128 in the RIR database for the space.4 of 636
ROA: none91.195.132.0/23No ROA covers it. Add a ROA for AS212128, maxLength 23.673 of 673
ROA: none91.220.157.0/24No ROA covers it. Add a ROA for AS212128, maxLength 24.673 of 673
ROA: none194.165.2.0/23No ROA covers it. Add a ROA for AS212128, maxLength 23.673 of 673
ROA: none2a09:6906::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.635 of 636
ROA: none2a11:bcc0::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc1::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc2::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc3::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc4::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc5::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc6::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636
ROA: none2a11:bcc7::/32No ROA covers it. Add a ROA for AS212128, maxLength 32.633 of 636

Route objects not announced

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

2a10:cbc2::/32RIPEValid
2a10:cbc3::/32RIPEValid
2a10:cbc4::/32RIPEValid
2a10:cbc6::/32RIPEValid
2a11:e381::/32RIPEValid
2a11:e383::/32RIPEValid
2a11:e384::/32RIPEValid
2a11:e385::/32RIPEValid
2a11:e386::/32RIPEValid
2a12:70c0::/32RIPEValid
2a12:70c1::/32RIPEValid
2a12:70c2::/32RIPEValid
2a12:70c3::/32RIPEValid
2a12:70c4::/32RIPEValid
2a12:70c5::/32RIPEValid
2a12:70c6::/32RIPEValid
2a12:70c7::/32RIPEValid
2a13:7e00::/32RIPEValid
2a13:7e01::/32RIPEValid
2a13:7e02::/32RIPEValid
2a13:7e04::/32RIPEValid
2a13:7e05::/32RIPEValid
2a13:7e06::/32RIPEValid
2a13:7e07::/32RIPEValid

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.