Network · data from 2026-11-12
AS32034 NEWCOM-INTL - SPEEDCAST LATAM INC.
Registry name: NEWCOM-INTL - SPEEDCAST LATAM INC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32034, 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.
| 190.26.204.0/24 | Invalid: origin | None | 1 0%low visibility |
| 192.23.64.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.23.62.0/24 | No ROA | Other IRR onlyRADB | 35 5%low visibility |
| 143.208.66.0/24 | Valid | Nonecovered by 143.208.64.0/22 | 673 100% |
| 70.35.146.0/24 | Valid | RIR databaseARIN | 673 100% |
| 70.35.147.0/24 | Valid | RIR databaseARIN | 673 100% |
| 70.35.148.0/24 | Valid | RIR databaseARIN | 673 100% |
| 70.35.149.0/24 | Valid | RIR databaseARIN | 673 100% |
| 70.35.150.0/24 | Valid | RIR databaseARIN | 673 100% |
| 70.35.151.0/24 | Valid | RIR databaseARIN | 673 100% |
| 70.35.158.0/24 | Valid | RIR databaseARIN | 673 100% |
| 138.36.144.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 138.36.145.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 181.199.128.0/20 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 186.64.124.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 204.14.40.0/24 | Valid | RIR databaseARIN | 673 100% |
| 204.14.41.0/24 | Valid | RIR databaseARIN | 673 100% |
| 204.14.42.0/24 | Valid | RIR databaseARIN | 673 100% |
| 204.14.43.0/24 | Valid | RIR databaseARIN | 673 100% |
| 204.14.44.0/24 | Valid | RIR databaseARIN | 673 100% |
| 204.14.46.0/24 | Valid | RIR databaseARIN | 673 100% |
| 207.241.185.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.226.64.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.226.65.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.226.66.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.14.45.0/24 | Valid | RIR databaseARIN | 672 100% |
| 181.199.141.0/24 | Valid | RIR databaseLACNIC | 671 100% |
AS-SET
AS32034 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 36 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: none2
- Route object: RIR2
- Route object: not announced29
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.26.204.0/24 | ROAs covering it name AS19429, not AS32034. If AS32034 should announce it, add a ROA for AS32034. |
| Route object: none | 190.26.204.0/24 | No route object for it. Add a route object with origin AS32034 in the RIR database for the space. |
| ROA: none | 192.23.64.0/24 | No ROA covers it. Add a ROA for AS32034, maxLength 24. |
| Route object: RIR | 192.23.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.23.62.0/24 | No ROA covers it. Add a ROA for AS32034, maxLength 24. |
| Route object: RIR | 192.23.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 143.208.66.0/24 | No route object for it. A route object for 143.208.64.0/22 with origin AS32034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32034 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32034 whose prefix no peer sees AS32034 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.225.152.0/24 | RADB | No ROA |
| 65.200.135.0/24 | RADB | No ROA |
| 65.212.126.0/24 | RADB | No ROA |
| 65.246.150.0/24 | RADB | No ROA |
| 143.208.64.0/22 | RADB | Valid |
| 200.3.176.0/21 | RADB | No ROA |
| 200.3.176.0/22 | RADB | No ROA |
| 200.3.176.0/23 | RADB | No ROA |
| 200.3.176.0/24 | RADB | No ROA |
| 200.3.177.0/24 | RADB | No ROA |
| 200.3.178.0/23 | RADB | No ROA |
| 200.3.178.0/24 | RADB | No ROA |
| 200.3.179.0/24 | RADB | No ROA |
| 200.3.180.0/22 | RADB | No ROA |
| 200.3.180.0/23 | RADB | No ROA |
| 200.3.180.0/24 | RADB | No ROA |
| 200.3.181.0/24 | RADB | No ROA |
| 200.3.182.0/23 | RADB | No ROA |
| 200.3.182.0/24 | RADB | No ROA |
| 200.3.183.0/24 | RADB | No ROA |
| 200.6.80.0/21 | RADB | No ROA |
| 200.105.224.0/19 | RADB | No ROA |
| 201.158.52.0/22 | LACNIC, RADB | Valid |
| 204.14.40.0/21 | RIPE-NONAUTH | No ROA |
| 206.113.96.0/20 | RADB | No ROA |
| 208.138.20.0/24 | RADB | No ROA |
| 216.226.64.0/20 | RIPE-NONAUTH | No ROA |
| 216.226.79.0/24 | RIPE-NONAUTH | No ROA |
| 2001:4960::/32 | ALTDB | 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.