Network · data from 2026-11-12
AS20101 MICHWAVE - Michwave Technologies, Inc.
Registry name: MICHWAVE - Michwave Technologies, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20101, 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.
| 216.18.240.0/24 | Valid | Nonecovered by 216.18.240.0/21 | 671 100% |
| 216.18.242.0/24 | Valid | Nonecovered by 216.18.240.0/21 | 671 100% |
| 216.18.247.0/24 | Valid | Nonecovered by 216.18.240.0/21 | 671 100% |
| 216.18.250.0/24 | Valid | Nonecovered by 216.18.240.0/20 | 671 100% |
| 199.192.180.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.192.181.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.192.182.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.192.183.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.18.240.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.18.253.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS20101 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 12 are in fix.csv.
- Route object: none4
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 216.18.240.0/24 | No route object for it. A route object for 216.18.240.0/21 with origin AS20101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20101 in the RIR database for the space. |
| Route object: none | 216.18.242.0/24 | No route object for it. A route object for 216.18.240.0/21 with origin AS20101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20101 in the RIR database for the space. |
| Route object: none | 216.18.247.0/24 | No route object for it. A route object for 216.18.240.0/21 with origin AS20101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20101 in the RIR database for the space. |
| Route object: none | 216.18.250.0/24 | No route object for it. A route object for 216.18.240.0/20 with origin AS20101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20101 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20101 whose prefix no peer sees AS20101 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.118.3.0/24 | RADB | No ROA |
| 199.192.180.0/22 | ARIN, RADB | Valid |
| 216.18.240.0/21 | ARIN | Valid |
| 216.18.243.0/24 | ARIN | Valid |
| 216.18.244.0/24 | ARIN | Valid |
| 216.18.248.0/24 | ARIN | Valid |
| 216.18.252.0/24 | ARIN | Valid |
| 216.18.254.0/24 | ARIN | 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.