Network · data from 2026-11-12
AS36515 Allens Communications
Registry name: ASN-ALLENS - Allens Communications, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36515, 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.
| 65.126.112.0/21 | No ROA | RIR databaseARIN | 670 100% |
| 199.68.56.0/21 | Valid | RIR databaseARIN | 670 100% |
| 209.240.48.0/20 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS36515'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 17 are in fix.csv.
- ROA: none1
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 65.126.112.0/21 | No ROA covers it. Add a ROA for AS36515, maxLength 21. |
Route objects not announced
Route objects with origin AS36515 whose prefix no peer sees AS36515 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.240.48.0/24 | ARIN | Invalid: maxLength |
| 209.240.49.0/24 | ARIN | Invalid: maxLength |
| 209.240.50.0/24 | ARIN | Invalid: maxLength |
| 209.240.51.0/24 | ARIN | Invalid: maxLength |
| 209.240.52.0/24 | ARIN | Invalid: maxLength |
| 209.240.53.0/24 | ARIN | Invalid: maxLength |
| 209.240.54.0/24 | ARIN | Invalid: maxLength |
| 209.240.55.0/24 | ARIN | Invalid: maxLength |
| 209.240.56.0/24 | ARIN | Invalid: maxLength |
| 209.240.57.0/24 | ARIN | Invalid: maxLength |
| 209.240.58.0/24 | ARIN | Invalid: maxLength |
| 209.240.59.0/24 | ARIN | Invalid: maxLength |
| 209.240.60.0/24 | ARIN | Invalid: maxLength |
| 209.240.61.0/24 | ARIN | Invalid: maxLength |
| 209.240.62.0/24 | ARIN | Invalid: maxLength |
| 209.240.63.0/24 | ARIN | Invalid: maxLength |
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.