bgpreport

Network · data from 2026-11-12

AS4717 AI3 - WIDE Project

Registry name: AI3 - WIDE Project, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4717, 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.

202.249.24.0/24 Invalid: origin None 4 1%low visibility 2
202.249.25.0/24 Invalid: origin None 4 1%low visibility 2
202.249.26.0/25 Invalid: origin None 3 0%low visibility 2
2001:d30::/32 Valid None 633 100% 68
2001:d30::/34 Valid None 6 1%low visibility 6

AS-SET

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

  • ROA: origin3
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin202.249.24.0/24ROAs covering it name AS2500, not AS4717. If AS4717 should announce it, add a ROA for AS4717.4 of 673
Route object: none202.249.24.0/24No route object for it. Add a route object with origin AS4717 in the RIR database for the space.4 of 673
ROA: origin202.249.25.0/24ROAs covering it name AS2500, not AS4717. If AS4717 should announce it, add a ROA for AS4717.4 of 673
Route object: none202.249.25.0/24No route object for it. Add a route object with origin AS4717 in the RIR database for the space.4 of 673
ROA: origin202.249.26.0/25ROAs covering it name AS2500, not AS4717. If AS4717 should announce it, add a ROA for AS4717.3 of 673
Route object: none202.249.26.0/25No route object for it. Add a route object with origin AS4717 in the RIR database for the space.3 of 673
Route object: none2001:d30::/32No route object for it. Add a route object with origin AS4717 in the RIR database for the space.633 of 636
Route object: none2001:d30::/34No route object for it. Add a route object with origin AS4717 in the RIR database for the space.6 of 636

Route objects not announced

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

202.249.47.0/24RADBValid

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.