bgpreport

Network · data from 2026-11-12

AS63997 Tsukaeru.net AS63997

Registry name: TSUKAERUNET - Tsukaeru.net, Web Hosting Company, Japan, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63997, 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.112.104.0/21 No ROA RIR databaseAPNIC, JPIRR, RADB 673 100% 67
111.68.16.0/21 No ROA RIR databaseAPNIC, JPIRR, RADB 673 100% 67
175.45.136.0/21 No ROA RIR databaseAPNIC, JPIRR, RADB 673 100% 67
119.82.24.0/21 No ROA RIR databaseAPNIC, JPIRR, RADB 672 100% 67
121.50.40.0/21 No ROA RIR databaseAPNIC, JPIRR, RADB 672 100% 67
203.83.240.0/21 No ROA RIR databaseAPNIC, JPIRR, RADB 672 100% 67
45.124.136.0/22 No ROA RIR databaseAPNIC, JPIRR, RADB 671 100% 67
195.95.180.0/24 No ROA RIR databaseRIPE 671 100% 67
2400:6b00::/32 No ROA RIR databaseAPNIC, JPIRR, RADB 636 100% 67

AS-SET

AS63997'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 25 are in fix.csv.

  • ROA: none9
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none27.112.104.0/21No ROA covers it. Add a ROA for AS63997, maxLength 21.673 of 673
ROA: none111.68.16.0/21No ROA covers it. Add a ROA for AS63997, maxLength 21.673 of 673
ROA: none175.45.136.0/21No ROA covers it. Add a ROA for AS63997, maxLength 21.673 of 673
ROA: none119.82.24.0/21No ROA covers it. Add a ROA for AS63997, maxLength 21.672 of 673
ROA: none121.50.40.0/21No ROA covers it. Add a ROA for AS63997, maxLength 21.672 of 673
ROA: none203.83.240.0/21No ROA covers it. Add a ROA for AS63997, maxLength 21.672 of 673
ROA: none45.124.136.0/22No ROA covers it. Add a ROA for AS63997, maxLength 22.671 of 673
ROA: none195.95.180.0/24No ROA covers it. Add a ROA for AS63997, maxLength 24.671 of 673
ROA: none2400:6b00::/32No ROA covers it. Add a ROA for AS63997, maxLength 32.636 of 636

Route objects not announced

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

27.112.104.0/22APNICNo ROA
27.112.108.0/22APNICNo ROA
45.124.136.0/23APNICNo ROA
45.124.138.0/23APNICNo ROA
45.254.38.0/24APNICValid
111.68.16.0/22APNICNo ROA
111.68.20.0/22APNICNo ROA
119.82.24.0/22APNICNo ROA
119.82.28.0/22APNICNo ROA
121.50.40.0/22APNICNo ROA
121.50.44.0/22APNICNo ROA
175.45.136.0/22APNICNo ROA
175.45.140.0/22APNICNo ROA
203.83.240.0/22APNICNo ROA
203.83.244.0/22APNICNo ROA
2405:a280:33::/48APNIC, RADBValid

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.