Network · data from 2026-11-12
AS11115 ONLINE-TECH-LLC - Otava, LLC
Registry name: ONLINE-TECH-LLC - Otava, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11115, 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.
| 192.103.131.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 2606:5200:c000::/36 | No ROA | Other IRR onlyRADB | 635 100% |
| 205.145.128.0/21 | Valid | Nonecovered by 205.145.128.0/20 | 672 100% |
| 205.145.136.0/21 | Valid | Nonecovered by 205.145.128.0/20 | 672 100% |
| 72.13.8.0/21 | Valid | Nonecovered by 72.13.0.0/20 | 670 100% |
| 72.13.0.0/21 | Valid | Nonecovered by 72.13.0.0/20 | 667 99% |
| 64.9.194.0/24 | Valid | RIR databaseARIN | 670 100% |
| 72.13.0.0/20 | Valid | RIR databaseARIN | 670 100% |
| 205.145.128.0/20 | Valid | RIR databaseARIN | 670 100% |
| 216.71.161.0/24 | Valid | RIR databaseARIN | 670 100% |
| 216.71.164.0/24 | Valid | RIR databaseARIN | 670 100% |
| 216.71.186.0/24 | Valid | RIR databaseARIN | 670 100% |
| 216.71.188.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS11115 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 13 are in fix.csv.
- ROA: none2
- Route object: none4
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.103.131.0/24 | No ROA covers it. Add a ROA for AS11115, maxLength 24. |
| Route object: RIR | 192.103.131.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2606:5200:c000::/36 | No ROA covers it. Add a ROA for AS11115, maxLength 36. |
| Route object: RIR | 2606:5200:c000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 205.145.128.0/21 | No route object for it. A route object for 205.145.128.0/20 with origin AS11115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11115 in the RIR database for the space. |
| Route object: none | 205.145.136.0/21 | No route object for it. A route object for 205.145.128.0/20 with origin AS11115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11115 in the RIR database for the space. |
| Route object: none | 72.13.8.0/21 | No route object for it. A route object for 72.13.0.0/20 with origin AS11115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11115 in the RIR database for the space. |
| Route object: none | 72.13.0.0/21 | No route object for it. A route object for 72.13.0.0/20 with origin AS11115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11115 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11115 whose prefix no peer sees AS11115 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.9.192.0/19 | NTTCOM | No ROA |
| 64.9.208.0/20 | NTTCOM | No ROA |
| 69.67.192.0/20 | RADB | No ROA |
| 74.121.144.0/22 | RADB | No ROA |
| 198.212.7.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.