bgpreport

Network · data from 2026-11-12

AS10011 Advanscope

Registry name: ADVAN - advanscope inc., JP · PeeringDB

7IPv4 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 AS10011, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS10011, 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.
24.41.112.0/20 Valid Other IRR onlyJPIRR 671 100% 67
61.121.224.0/20 Valid Other IRR onlyJPIRR 671 100% 67
124.108.56.0/21 Valid Other IRR onlyJPIRR 671 100% 67
219.106.176.0/20 Valid Other IRR onlyJPIRR 671 100% 67
223.27.72.0/21 Valid Other IRR onlyJPIRR 670 100% 67
103.13.60.0/22 Valid Other IRR onlyJPIRR 669 99% 67
219.100.68.0/22 Valid Other IRR onlyJPIRR 669 99% 67
2402:2840::/32 Valid Other IRR onlyJPIRR 635 100% 70

AS-SET

AS10011'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: RIR24.41.112.0/20Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR61.121.224.0/20Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR124.108.56.0/21Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR219.106.176.0/20Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR223.27.72.0/21Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
Route object: RIR103.13.60.0/22Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR219.100.68.0/22Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR2402:2840::/32Route object only in JPIRR. Add it in the RIR database for the space.635 of 636

Route objects not announced

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