Network · data from 2026-11-12
AS26932 HUBNET - BRAVO TELECOM
Registry name: HUBNET - BRAVO TELECOM, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26932, 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.
| 104.192.124.0/22 | Invalid: origin | None | 2 0%low visibility |
| 23.133.220.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.251.32.0/20 | Valid | RIR databaseARIN | 673 100% |
| 199.83.160.0/21 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS26932 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 104.192.124.0/22 | ROAs covering it name AS395071, not AS26932. If AS26932 should announce it, add a ROA for AS26932. |
| Route object: none | 104.192.124.0/22 | No route object for it. Add a route object with origin AS26932 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26932 whose prefix no peer sees AS26932 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 149.119.64.0/18 | ARIN | 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.