Network · data from 2026-11-12
AS262239 Speednet Communications
Registry name: AS262239 - Speednet Communications Limited, BZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262239, 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.
| 50.118.230.0/24 | Valid | Nonecovered by 50.118.230.0/23 | 673 100% |
| 50.118.231.0/24 | Valid | Nonecovered by 50.118.230.0/23 | 673 100% |
| 186.65.89.0/24 | Valid | Nonecovered by 186.65.88.0/23 | 673 100% |
| 186.65.90.0/24 | Valid | Nonecovered by 186.65.88.0/22 | 673 100% |
| 186.65.91.0/24 | Valid | Nonecovered by 186.65.88.0/22 | 673 100% |
| 190.211.146.0/24 | Valid | Nonecovered by 190.211.146.0/23 | 672 100% |
| 190.211.147.0/24 | Valid | Nonecovered by 190.211.146.0/23 | 672 100% |
| 186.65.88.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 50.118.230.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 186.65.88.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 190.211.145.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 190.211.146.0/23 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 190.211.148.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
AS-SET
AS262239'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 16 are in fix.csv.
- Route object: none7
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 50.118.230.0/24 | No route object for it. A route object for 50.118.230.0/23 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: none | 50.118.231.0/24 | No route object for it. A route object for 50.118.230.0/23 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: none | 186.65.89.0/24 | No route object for it. A route object for 186.65.88.0/23 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: none | 186.65.90.0/24 | No route object for it. A route object for 186.65.88.0/22 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: none | 186.65.91.0/24 | No route object for it. A route object for 186.65.88.0/22 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: none | 190.211.146.0/24 | No route object for it. A route object for 190.211.146.0/23 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: none | 190.211.147.0/24 | No route object for it. A route object for 190.211.146.0/23 with origin AS262239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262239 in the RIR database for the space. |
| Route object: RIR | 186.65.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262239 whose prefix no peer sees AS262239 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.65.88.0/23 | RADB | Valid |
| 191.97.80.0/21 | RADB | No ROA |
| 192.52.81.0/24 | RADB | No ROA |
| 196.52.81.0/24 | RADB | No ROA |
| 196.55.4.0/24 | RADB | No ROA |
| 2803:9a00::/32 | LACNIC, RADB | Valid |
| 2803:9a00:bb::/48 | LACNIC | Valid |
| 2803:9a00:17e::/47 | LACNIC | 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.