bgpreport

Network · data from 2026-11-12

AS37286 Nigeria ICT Forum of Partnership Institutions

Registry name: Nigeria ICT Forum of Partnership Institutions - Nigeria ICT Forum of Partnership Institutions, NG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37286, 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.76.248.0/24 No ROA RIR databaseAFRINIC 671 100% 68
41.76.249.0/24 No ROA RIR databaseAFRINIC 671 100% 68
41.76.250.0/24 No ROA RIR databaseAFRINIC 671 100% 68
41.76.251.0/24 No ROA RIR databaseAFRINIC 671 100% 68
41.76.252.0/24 No ROA RIR databaseAFRINIC 671 100% 68
2c0f:ff20::/32 No ROA RIR databaseAFRINIC 636 100% 69
41.76.254.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 199 30% 50
41.76.255.0/24 No ROA RIR databaseAFRINIC 11 2%low visibility 7

AS-SET

PeeringDB's irr_as_set for AS37286: AS-37286_AS-328825. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS37286 isn't in the set, or no route object for AS37286 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS37286 in itNot covered
AS-37286_AS-328825 AFRINIC 4119 Yes 0

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

  • ROA: none8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none41.76.248.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.671 of 673
ROA: none41.76.249.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.671 of 673
ROA: none41.76.250.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.671 of 673
ROA: none41.76.251.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.671 of 673
ROA: none41.76.252.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.671 of 673
ROA: none2c0f:ff20::/32No ROA covers it. Add a ROA for AS37286, maxLength 32.636 of 636
ROA: none41.76.254.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.199 of 673
ROA: none41.76.255.0/24No ROA covers it. Add a ROA for AS37286, maxLength 24.11 of 673

Route objects not announced

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

41.76.248.0/21AFRINICNo ROA
41.76.253.0/24AFRINICNo ROA
102.220.96.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.