bgpreport

Network · data from 2026-11-12

AS18148 FUKUOKA-U - Fukuoka University

Registry name: FUKUOKA-U - Fukuoka University, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18148, 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.
133.100.0.0/21 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 69
133.100.16.0/20 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 69
133.100.32.0/19 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 69
133.100.64.0/18 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 69
133.100.128.0/17 Valid Other IRR onlyJPIRR, NTTCOM 672 100% 69
133.100.8.0/24 Valid Other IRR onlyJPIRR, NTTCOM 670 100% 69
133.100.10.0/24 Valid Other IRR onlyJPIRR, NTTCOM 670 100% 69
133.100.12.0/22 Valid Other IRR onlyJPIRR, NTTCOM 670 100% 69
2405:be00::/32 Valid Other IRR onlyJPIRR, NTTCOM 634 100% 69

AS-SET

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

  • Route object: RIR9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR133.100.0.0/21Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR133.100.16.0/20Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR133.100.32.0/19Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR133.100.64.0/18Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR133.100.128.0/17Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR133.100.8.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR133.100.10.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR133.100.12.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR2405:be00::/32Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

133.100.0.0/16JPIRR, NTTCOMNo 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.