bgpreport

Network · data from 2026-11-12

AS328585 MegaMore Wireless Broadband

Registry name: MegaMore Wireless Broadband Limited - MegaMore Wireless Broadband Limited, NG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328585, 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.23.164.0/24 Valid Nonecovered by 102.23.164.0/22 673 100% 67
102.23.165.0/24 Valid Nonecovered by 102.23.164.0/22 673 100% 67
102.23.167.0/24 Valid Nonecovered by 102.23.164.0/22 671 100% 67
102.23.166.0/24 Valid Other IRR onlyRADB 671 100% 69
102.206.136.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.206.137.0/24 Valid RIR databaseAFRINIC 671 100% 68
102.216.193.0/24 Valid RIR databaseAFRINIC 671 100% 68
102.216.194.0/24 Valid RIR databaseAFRINIC 671 100% 68
102.216.195.0/24 Valid RIR databaseAFRINIC 671 100% 68
102.206.138.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.216.192.0/24 Valid RIR databaseAFRINIC 669 99% 68
2c0f:26c0::/28 Valid RIR databaseAFRINIC 635 100% 69
2c0f:e920::/32 Valid RIR databaseAFRINIC 635 100% 69
102.206.139.0/24 Valid RIR databaseAFRINIC 2 0%low visibility 3

AS-SET

AS328585'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 5 are in fix.csv.

  • Route object: none3
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none102.23.164.0/24No route object for it. A route object for 102.23.164.0/22 with origin AS328585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328585 in the RIR database for the space.673 of 673
Route object: none102.23.165.0/24No route object for it. A route object for 102.23.164.0/22 with origin AS328585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328585 in the RIR database for the space.673 of 673
Route object: none102.23.167.0/24No route object for it. A route object for 102.23.164.0/22 with origin AS328585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328585 in the RIR database for the space.671 of 673
Route object: RIR102.23.166.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

102.23.164.0/22AFRINICNo 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.