bgpreport

Network · data from 2026-11-12

AS196962 ANTHEIA NSI (Holdings) Limited

Registry name: ANTHEIA NSI (Holdings) Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS196962, 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.
69.90.53.0/24 No ROA Other IRR onlyRADB 671 100% 67
69.90.60.0/23 No ROA Other IRR onlyRADB 671 100% 67
69.90.146.0/24 No ROA Other IRR onlyRADB 671 100% 67
2620:1e:a000::/48 No ROA Other IRR onlyRADB, RIPE-NONAUTH 633 100% 68
185.111.92.0/22 No ROA RIR databaseRADB, RIPE 671 100% 67
193.105.182.0/24 No ROA RIR databaseRADB, RIPE 671 100% 67
69.90.15.0/24 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

AS196962 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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none69.90.53.0/24No ROA covers it. Add a ROA for AS196962, maxLength 24.671 of 673
Route object: RIR69.90.53.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.90.60.0/23No ROA covers it. Add a ROA for AS196962, maxLength 23.671 of 673
Route object: RIR69.90.60.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.90.146.0/24No ROA covers it. Add a ROA for AS196962, maxLength 24.671 of 673
Route object: RIR69.90.146.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2620:1e:a000::/48No ROA covers it. Add a ROA for AS196962, maxLength 48.633 of 636
Route object: RIR2620:1e:a000::/48Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.633 of 636
ROA: none185.111.92.0/22No ROA covers it. Add a ROA for AS196962, maxLength 22.671 of 673
ROA: none193.105.182.0/24No ROA covers it. Add a ROA for AS196962, maxLength 24.671 of 673

Route objects not announced

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

69.90.60.0/24RADBNo ROA
69.90.61.0/24RADBNo ROA
185.111.92.0/24RADB, RIPENo ROA
185.111.93.0/24RADB, RIPENo ROA
185.111.94.0/24RADB, RIPENo ROA
185.111.95.0/24RADB, RIPENo 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.