bgpreport

Network · data from 2026-11-12

AS37506 Zinox Telecommunications Limited - Zinox Telecommunications Limited

Registry name: Zinox Telecommunications Limited - Zinox Telecommunications Limited, NG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37506, 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.
41.220.80.0/22 Valid Nonecovered by 41.220.80.0/20 672 100% 67
41.220.84.0/22 Valid Nonecovered by 41.220.80.0/20 672 100% 67
41.220.88.0/22 Valid Nonecovered by 41.220.80.0/20 672 100% 67
41.220.92.0/22 Valid Nonecovered by 41.220.80.0/20 672 100% 67
197.148.80.0/22 Valid Nonecovered by 197.148.80.0/21 672 100% 67
197.148.84.0/22 Valid Nonecovered by 197.148.80.0/21 672 100% 67
197.148.80.0/21 Valid RIR databaseAFRINIC 672 100% 67
41.220.80.0/20 Valid RIR databaseAFRINIC 670 100% 67
165.90.240.0/20 Valid RIR databaseAFRINIC 670 100% 67
2c0f:5380::/32 Valid RIR databaseAFRINIC 635 100% 67

AS-SET

AS37506 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 6 are in fix.csv.

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none41.220.80.0/22No route object for it. A route object for 41.220.80.0/20 with origin AS37506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37506 in the RIR database for the space.672 of 673
Route object: none41.220.84.0/22No route object for it. A route object for 41.220.80.0/20 with origin AS37506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37506 in the RIR database for the space.672 of 673
Route object: none41.220.88.0/22No route object for it. A route object for 41.220.80.0/20 with origin AS37506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37506 in the RIR database for the space.672 of 673
Route object: none41.220.92.0/22No route object for it. A route object for 41.220.80.0/20 with origin AS37506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37506 in the RIR database for the space.672 of 673
Route object: none197.148.80.0/22No route object for it. A route object for 197.148.80.0/21 with origin AS37506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37506 in the RIR database for the space.672 of 673
Route object: none197.148.84.0/22No route object for it. A route object for 197.148.80.0/21 with origin AS37506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37506 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS37506 is announced.

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.