bgpreport

Network · data from 2026-11-12

AS329191 Nilmage Two4Seven Limited

Registry name: Nilmage Two4Seven Limited - Nilmage Two4Seven Limited, NG · 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 AS329191, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS329191, 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.
102.214.124.0/24 No ROA RIR databaseAFRINIC 673 100% 66
102.214.125.0/24 No ROA RIR databaseAFRINIC 673 100% 66

AS-SET

AS329191'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 3 are in fix.csv.

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none102.214.124.0/24No ROA covers it. Add a ROA for AS329191, maxLength 24.673 of 673
ROA: none102.214.125.0/24No ROA covers it. Add a ROA for AS329191, maxLength 24.673 of 673

Route objects not announced

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

102.214.124.0/23AFRINICNo 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.