Network · data from 2026-11-12
AS62145 Bango BANGO.NET Ltd
Registry name: Bango BANGO.NET Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62145, 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.
| 185.35.88.0/24 | No ROA | RIR databaseRADB, RIPE | 671 100% |
| 185.35.89.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.35.90.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.35.91.0/24 | No ROA | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS62145 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 9 are in fix.csv.
- ROA: none4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.35.88.0/24 | No ROA covers it. Add a ROA for AS62145, maxLength 24. |
| ROA: none | 185.35.89.0/24 | No ROA covers it. Add a ROA for AS62145, maxLength 24. |
| ROA: none | 185.35.90.0/24 | No ROA covers it. Add a ROA for AS62145, maxLength 24. |
| ROA: none | 185.35.91.0/24 | No ROA covers it. Add a ROA for AS62145, maxLength 24. |
Route objects not announced
Route objects with origin AS62145 whose prefix no peer sees AS62145 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.35.88.0/22 | RADB | No ROA |
| 193.104.9.0/24 | RIPE | Valid |
| 193.109.236.0/24 | RIPE | Valid |
| 195.66.154.0/23 | RIPE | Valid |
| 195.234.129.0/24 | RIPE | Valid |
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.