bgpreport

Network · data from 2026-11-12

AS63793 Japan OPS Better Co.

Registry name: OPSBETTER - Japan OPS Better Co., Ltd., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63793, 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.
212.74.61.0/24 Invalid: origin None 2 0%low visibility 2
103.179.160.0/23 No ROA Other IRR onlyRADB 672 100% 67
2400:4d60::/32 No ROA Other IRR onlyRADB 634 100% 67
202.237.95.0/24 Valid Nonecovered by 202.237.92.0/22 671 100% 67
202.237.93.0/24 Valid Nonecovered by 202.237.92.0/22 2 0%low visibility 2
202.237.92.0/24 Valid Other IRR onlyJPIRR 672 100% 67

AS-SET

AS63793'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 13 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin212.74.61.0/24ROAs covering it name AS834, not AS63793. If AS63793 should announce it, add a ROA for AS63793.2 of 673
Route object: none212.74.61.0/24No route object for it. Add a route object with origin AS63793 in the RIR database for the space.2 of 673
ROA: none103.179.160.0/23No ROA covers it. Add a ROA for AS63793, maxLength 23.672 of 673
Route object: RIR103.179.160.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2400:4d60::/32No ROA covers it. Add a ROA for AS63793, maxLength 32.634 of 636
Route object: RIR2400:4d60::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: none202.237.95.0/24No route object for it. A route object for 202.237.92.0/22 with origin AS63793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63793 in the RIR database for the space.671 of 673
Route object: none202.237.93.0/24No route object for it. A route object for 202.237.92.0/22 with origin AS63793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63793 in the RIR database for the space.2 of 673
Route object: RIR202.237.92.0/24Route object only in JPIRR. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

16.216.78.0/24ARINInvalid: origin
91.233.9.0/24RADBNo ROA
98.98.110.0/23RADBNo ROA
202.237.92.0/22JPIRRValid

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.