bgpreport

Network · data from 2026-11-12

AS37323 Netpage Company

Registry name: Netpage Company Limited - Netpage Company Limited, GM · PeeringDB

23IPv4 routes 87.0% 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
4No ROA 0 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS37323, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS37323, 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.203.168.0/24 No ROA RIR databaseAFRINIC 673 100% 67
102.203.170.0/24 No ROA RIR databaseAFRINIC 671 100% 68
102.203.171.0/24 No ROA RIR databaseAFRINIC 2 0%low visibility 2
2c0f:fcb8::/32 No ROA RIR databaseAFRINIC 1 0%low visibility 1
102.211.244.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.211.245.0/24 Valid RIR databaseAFRINIC 673 100% 67
197.255.194.0/24 Valid RIR databaseAFRINIC 673 100% 67
197.255.195.0/24 Valid RIR databaseAFRINIC 673 100% 67
197.255.196.0/24 Valid RIR databaseAFRINIC 673 100% 67
197.255.203.0/24 Valid RIR databaseAFRINIC 673 100% 67
197.255.204.0/24 Valid RIR databaseAFRINIC 673 100% 67
197.255.207.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.211.247.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.193.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.197.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.198.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.199.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.200.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.205.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.206.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.255.201.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.255.202.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.211.246.0/24 Valid RIR databaseAFRINIC 2 0%low visibility 2
197.255.192.0/20 Valid RIR databaseAFRINIC 2 0%low visibility 2

AS-SET

AS37323'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 8 are in fix.csv.

  • ROA: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none102.203.168.0/24No ROA covers it. Add a ROA for AS37323, maxLength 24.673 of 673
ROA: none102.203.170.0/24No ROA covers it. Add a ROA for AS37323, maxLength 24.671 of 673
ROA: none102.203.171.0/24No ROA covers it. Add a ROA for AS37323, maxLength 24.2 of 673
ROA: none2c0f:fcb8::/32No ROA covers it. Add a ROA for AS37323, maxLength 32.1 of 636

Route objects not announced

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

102.203.168.0/22AFRINIC, RADBNo ROA
102.203.169.0/24AFRINICNo ROA
102.211.244.0/22AFRINICValid
197.255.192.0/24AFRINICValid

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.