bgpreport

Network · data from 2026-11-12

AS22354 -

Registry name: -, TZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22354, 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.
196.44.160.0/20 No ROA RIR databaseAFRINIC, ALTDB, RIPE-NONAUTH 671 100% 68
41.86.160.0/19 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 67
2c0f:f538::/32 No ROA RIR databaseAFRINIC 636 100% 67

AS-SET

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

  • ROA: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none196.44.160.0/20No ROA covers it. Add a ROA for AS22354, maxLength 20.671 of 673
ROA: none41.86.160.0/19No ROA covers it. Add a ROA for AS22354, maxLength 19.670 of 673
ROA: none2c0f:f538::/32No ROA covers it. Add a ROA for AS22354, maxLength 32.636 of 636

Route objects not announced

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

196.44.160.0/21RIPE-NONAUTHNo ROA
196.44.168.0/21RADBNo 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.