Network · data from 2026-11-12
AS13337 EVWI-NET-01 - e-vergent.com LLC
Registry name: EVWI-NET-01 - e-vergent.com LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13337, 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.
| 137.83.100.0/24 | No ROA | None | 670 100% |
| 137.83.101.0/24 | No ROA | None | 670 100% |
| 66.96.0.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 199.30.168.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 208.82.224.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 208.84.128.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 208.84.130.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 208.88.92.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 209.225.96.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 209.251.80.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS13337 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 34 are in fix.csv.
- ROA: none10
- Route object: none2
- Route object: RIR8
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 137.83.100.0/24 | No ROA covers it. Add a ROA for AS13337, maxLength 24. |
| Route object: none | 137.83.100.0/24 | No route object for it. Add a route object with origin AS13337 in the RIR database for the space. |
| ROA: none | 137.83.101.0/24 | No ROA covers it. Add a ROA for AS13337, maxLength 24. |
| Route object: none | 137.83.101.0/24 | No route object for it. Add a route object with origin AS13337 in the RIR database for the space. |
| ROA: none | 66.96.0.0/20 | No ROA covers it. Add a ROA for AS13337, maxLength 20. |
| Route object: RIR | 66.96.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.30.168.0/21 | No ROA covers it. Add a ROA for AS13337, maxLength 21. |
| Route object: RIR | 199.30.168.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.82.224.0/22 | No ROA covers it. Add a ROA for AS13337, maxLength 22. |
| Route object: RIR | 208.82.224.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.84.128.0/23 | No ROA covers it. Add a ROA for AS13337, maxLength 23. |
| Route object: RIR | 208.84.128.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.84.130.0/23 | No ROA covers it. Add a ROA for AS13337, maxLength 23. |
| Route object: RIR | 208.84.130.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.88.92.0/22 | No ROA covers it. Add a ROA for AS13337, maxLength 22. |
| Route object: RIR | 208.88.92.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.225.96.0/20 | No ROA covers it. Add a ROA for AS13337, maxLength 20. |
| Route object: RIR | 209.225.96.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.251.80.0/20 | No ROA covers it. Add a ROA for AS13337, maxLength 20. |
| Route object: RIR | 209.251.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13337 whose prefix no peer sees AS13337 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.161.148.0/23 | RADB | No ROA |
| 12.161.152.0/21 | RADB | No ROA |
| 143.246.224.0/20 | RADB | No ROA |
| 199.5.193.0/24 | RADB | No ROA |
| 209.225.96.0/22 | RADB | No ROA |
| 209.225.100.0/22 | RADB | No ROA |
| 209.225.104.0/24 | RADB | No ROA |
| 209.225.105.0/24 | RADB | No ROA |
| 209.225.106.0/24 | RADB | No ROA |
| 209.225.107.0/24 | RADB | No ROA |
| 209.225.108.0/24 | RADB | No ROA |
| 209.225.109.0/24 | RADB | No ROA |
| 209.225.110.0/24 | RADB | No ROA |
| 209.225.111.0/24 | RADB | 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.