Network · data from 2026-11-12
AS11847 OTT - GoNetSpeed
Registry name: OTT - GoNetSpeed, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11847, 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.
| 199.191.0.0/20 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.97.168.0/21 | Valid | RIR databaseARIN, RADB | 672 100% |
| 64.135.128.0/22 | Valid | RIR databaseARIN | 672 100% |
| 64.135.136.0/21 | Valid | RIR databaseARIN | 672 100% |
| 66.181.112.0/20 | Valid | RIR databaseARIN | 672 100% |
| 66.252.32.0/21 | Valid | RIR databaseARIN | 672 100% |
| 66.252.44.0/22 | Valid | RIR databaseARIN | 672 100% |
| 66.252.48.0/21 | Valid | RIR databaseARIN | 672 100% |
| 66.252.56.0/22 | Valid | RIR databaseARIN | 672 100% |
| 66.252.60.0/23 | Valid | RIR databaseARIN | 672 100% |
| 68.68.224.0/24 | Valid | RIR databaseARIN | 672 100% |
| 68.68.226.0/24 | Valid | RIR databaseARIN | 672 100% |
| 68.68.229.0/24 | Valid | RIR databaseARIN | 672 100% |
| 68.68.232.0/23 | Valid | RIR databaseARIN | 672 100% |
| 68.68.234.0/24 | Valid | RIR databaseARIN | 672 100% |
| 68.68.236.0/22 | Valid | RIR databaseARIN | 672 100% |
| 97.107.144.0/21 | Valid | RIR databaseARIN | 672 100% |
| 97.107.153.0/24 | Valid | RIR databaseARIN | 672 100% |
| 97.107.154.0/24 | Valid | RIR databaseARIN | 672 100% |
| 216.220.224.0/21 | Valid | RIR databaseARIN | 672 100% |
| 216.220.232.0/23 | Valid | RIR databaseARIN | 672 100% |
| 216.220.234.0/24 | Valid | RIR databaseARIN | 672 100% |
| 216.220.236.0/23 | Valid | RIR databaseARIN | 672 100% |
| 216.220.240.0/20 | Valid | RIR databaseARIN | 672 100% |
| 216.220.239.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2607:4a00:2000::/36 | Valid | RIR databaseARIN | 636 100% |
| 2607:4a00:3000::/36 | Valid | RIR databaseARIN | 636 100% |
| 2607:f718::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
AS11847 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 8 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.191.0.0/20 | No ROA covers it. Add a ROA for AS11847, maxLength 20. |
| Route object: RIR | 199.191.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11847 whose prefix no peer sees AS11847 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.87.208.0/24 | RADB | No ROA |
| 167.8.34.0/24 | RADB | No ROA |
| 198.133.167.0/24 | RADB | No ROA |
| 198.200.10.0/23 | RADB | No ROA |
| 2607:4a00::/32 | RADB | No ROA |
| 2607:5a80::/32 | 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.