Network · data from 2026-11-12
AS18415 BWIZ - B-WIZ Technology
Registry name: BWIZ - B-WIZ Technology, TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18415, 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.
| 61.57.242.0/24 | Valid | Nonecovered by 61.57.240.0/22 | 671 100% |
| 61.57.244.0/24 | Valid | Nonecovered by 61.57.244.0/23 | 671 100% |
| 61.57.245.0/24 | Valid | Nonecovered by 61.57.244.0/23 | 671 100% |
| 61.57.246.0/24 | Valid | Nonecovered by 61.57.246.0/23 | 671 100% |
| 61.57.247.0/24 | Valid | Nonecovered by 61.57.246.0/23 | 671 100% |
| 61.57.248.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.249.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.250.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.251.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.252.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.253.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.254.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.255.0/24 | Valid | Nonecovered by 61.57.240.0/20 | 671 100% |
| 61.57.240.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 61.57.240.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 61.57.240.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 61.57.243.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 61.57.244.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
AS-SET
AS18415 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.
- Route object: none13
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 61.57.242.0/24 | No route object for it. A route object for 61.57.240.0/22 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.244.0/24 | No route object for it. A route object for 61.57.244.0/23 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.245.0/24 | No route object for it. A route object for 61.57.244.0/23 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.246.0/24 | No route object for it. A route object for 61.57.246.0/23 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.247.0/24 | No route object for it. A route object for 61.57.246.0/23 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.248.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.249.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.250.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.251.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.252.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.253.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.254.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: none | 61.57.255.0/24 | No route object for it. A route object for 61.57.240.0/20 with origin AS18415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18415 in the RIR database for the space. |
| Route object: RIR | 61.57.240.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.240.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.243.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.57.244.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18415 whose prefix no peer sees AS18415 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.57.246.0/23 | RADB | Valid |
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.