bgpreport

Network · data from 2026-11-12

AS45680 DOVA Corporation

Registry name: DOVA-NET - DOVA Corporation, JP · PeeringDB

9IPv4 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
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS45680, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45680, 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.
101.78.6.0/24 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
103.235.40.0/22 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
183.81.176.0/22 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
183.81.176.0/24 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
183.81.177.0/24 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
183.81.178.0/23 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
2401:5300::/32 Valid Other IRR onlyJPIRR, NTTCOM 635 100% 67
218.100.67.0/24 Valid Other IRR onlyJPIRR, NTTCOM 2 0%low visibility 2
103.30.240.0/22 Valid RIR databaseAPNIC 671 100% 67
157.250.176.0/20 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS45680's PeeringDB record names no 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 8 are in fix.csv.

  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: RIR101.78.6.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR103.235.40.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR183.81.176.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR183.81.176.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR183.81.177.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR183.81.178.0/23Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR2401:5300::/32Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.635 of 636
Route object: RIR218.100.67.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.2 of 673

Route objects not announced

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