Network · data from 2026-11-12
AS26396 MidwayNet, LLC.
Registry name: MIDWAYNET-ASN - MidwayNet, LLC., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26396, 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.
| 67.238.112.0/21 | No ROA | None | 673 100% |
| 67.238.124.0/24 | No ROA | None | 673 100% |
| 67.238.122.0/24 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS26396'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 13 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 67.238.112.0/21 | No ROA covers it. Add a ROA for AS26396, maxLength 21. |
| Route object: none | 67.238.112.0/21 | No route object for it. Add a route object with origin AS26396 in the RIR database for the space. |
| ROA: none | 67.238.124.0/24 | No ROA covers it. Add a ROA for AS26396, maxLength 24. |
| Route object: none | 67.238.124.0/24 | No route object for it. Add a route object with origin AS26396 in the RIR database for the space. |
| ROA: none | 67.238.122.0/24 | No ROA covers it. Add a ROA for AS26396, maxLength 24. |
Route objects not announced
Route objects with origin AS26396 whose prefix no peer sees AS26396 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.238.112.0/24 | ARIN | No ROA |
| 67.238.113.0/24 | ARIN | No ROA |
| 67.238.114.0/24 | ARIN | No ROA |
| 67.238.115.0/24 | ARIN | No ROA |
| 67.238.116.0/24 | ARIN | No ROA |
| 67.238.117.0/24 | ARIN | No ROA |
| 67.238.118.0/24 | ARIN | No ROA |
| 67.238.119.0/24 | ARIN | No 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.