bgpreport

Network · data from 2026-11-12

AS55899 IROB - irob Ltd.

Registry name: IROB - irob Ltd., JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55899, 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.
103.171.16.0/23 No ROA Other IRR onlyJPIRR 672 100% 67
183.182.32.0/19 No ROA Other IRR onlyJPIRR 672 100% 67
183.182.32.0/21 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
183.182.40.0/22 No ROA Other IRR onlyJPIRR 672 100% 67
183.182.44.0/22 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
183.182.48.0/21 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
2401:2540::/32 No ROA Other IRR onlyJPIRR 636 100% 68
2407:bc40::/32 No ROA Other IRR onlyJPIRR 636 100% 68

AS-SET

AS55899 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 19 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none103.171.16.0/23No ROA covers it. Add a ROA for AS55899, maxLength 23.672 of 673
Route object: RIR103.171.16.0/23Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none183.182.32.0/19No ROA covers it. Add a ROA for AS55899, maxLength 19.672 of 673
Route object: RIR183.182.32.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none183.182.32.0/21No ROA covers it. Add a ROA for AS55899, maxLength 21.672 of 673
Route object: RIR183.182.32.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none183.182.40.0/22No ROA covers it. Add a ROA for AS55899, maxLength 22.672 of 673
Route object: RIR183.182.40.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none183.182.44.0/22No ROA covers it. Add a ROA for AS55899, maxLength 22.672 of 673
Route object: RIR183.182.44.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none183.182.48.0/21No ROA covers it. Add a ROA for AS55899, maxLength 21.672 of 673
Route object: RIR183.182.48.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2401:2540::/32No ROA covers it. Add a ROA for AS55899, maxLength 32.636 of 636
Route object: RIR2401:2540::/32Route object only in JPIRR. Add it in the RIR database for the space.636 of 636
ROA: none2407:bc40::/32No ROA covers it. Add a ROA for AS55899, maxLength 32.636 of 636
Route object: RIR2407:bc40::/32Route object only in JPIRR. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

183.182.56.0/22JPIRRNo ROA
183.182.61.0/24JPIRRNo ROA
219.100.220.0/22JPIRRNo 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.