bgpreport

Network · data from 2026-11-12

AS7672 The Hokuden Information System Service Company

Registry name: FITWEB - Hokuden Information System Service Co.,Ltd., JP · PeeringDB

20IPv4 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
0Route objects not announced registered with origin AS7672, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7672, 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.
27.133.192.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
61.215.224.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
101.96.32.0/19 Valid Other IRR onlyJPIRR, RADB 672 100% 67
103.225.120.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
110.232.224.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
110.232.232.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
113.197.56.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
119.63.16.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
157.250.224.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.125.48.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
203.88.176.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
211.19.192.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
216.8.0.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
216.8.16.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
210.166.0.0/19 Valid Other IRR onlyJPIRR, RADB 671 100% 67
210.166.0.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
210.166.16.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
210.171.208.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
218.223.208.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
218.228.16.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
2404:200::/32 Valid Other IRR onlyJPIRR, RADB 636 100% 68

AS-SET

PeeringDB's irr_as_set for AS7672: RADB::AS-FITWEB. 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 (AS7672 isn't in the set, or no route object for AS7672 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 objectsAS7672 in itNot covered
RADB::AS-FITWEB RADB 1121 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 21 are in fix.csv.

  • Route object: RIR21
ChangePrefix or setDetailFull-table peers
Route object: RIR27.133.192.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.224.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR101.96.32.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.225.120.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.232.224.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.232.232.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.197.56.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.63.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.250.224.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.125.48.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.88.176.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.19.192.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR216.8.0.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR216.8.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.166.0.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.166.0.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.166.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.171.208.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.223.208.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.228.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2404:200::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS7672 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.