Network · data from 2026-11-12
AS30407 VELCOM - Velcom
Registry name: VELCOM - Velcom, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30407, 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.234.216.0/24 | No ROA | Other origin only | 11 2%low visibility |
| 104.234.223.0/24 | No ROA | Other origin only | 11 2%low visibility |
| 98.142.255.0/24 | No ROA | RIR databaseARIN | 11 2%low visibility |
AS-SET
AS30407 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 31 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.234.216.0/24 | No ROA covers it. Add a ROA for AS30407, maxLength 24. |
| Route object: none | 104.234.216.0/24 | Route objects for it name AS30236. Add a route object with origin AS30407 in the RIR database for the space. |
| ROA: none | 104.234.223.0/24 | No ROA covers it. Add a ROA for AS30407, maxLength 24. |
| Route object: none | 104.234.223.0/24 | Route objects for it name AS30236. Add a route object with origin AS30407 in the RIR database for the space. |
| ROA: none | 98.142.255.0/24 | No ROA covers it. Add a ROA for AS30407, maxLength 24. |
Route objects not announced
Route objects with origin AS30407 whose prefix no peer sees AS30407 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 98.142.240.0/20 | ARIN | No ROA |
| 98.142.240.0/24 | ARIN | Invalid: origin |
| 98.142.242.0/24 | ARIN | Invalid: origin |
| 98.142.243.0/24 | ARIN | Invalid: origin |
| 98.142.244.0/24 | ARIN | Invalid: origin |
| 98.142.245.0/24 | ARIN | Invalid: origin |
| 98.142.246.0/24 | ARIN | Invalid: origin |
| 98.142.247.0/24 | ARIN | Invalid: origin |
| 98.142.249.0/24 | ARIN | Invalid: origin |
| 98.142.250.0/24 | ARIN | Invalid: origin |
| 98.142.251.0/24 | ARIN | Invalid: origin |
| 98.142.252.0/24 | ARIN | Invalid: origin |
| 98.142.253.0/24 | ARIN | Invalid: origin |
| 98.142.254.0/24 | ARIN | Invalid: origin |
| 206.53.48.0/20 | ARIN | No ROA |
| 206.53.48.0/24 | ARIN | Invalid: origin |
| 206.53.50.0/24 | ARIN | Invalid: origin |
| 206.53.51.0/24 | ARIN | No ROA |
| 206.53.54.0/24 | ARIN | Invalid: origin |
| 206.53.55.0/24 | ARIN | Invalid: origin |
| 206.53.56.0/24 | ARIN | Invalid: origin |
| 206.53.59.0/24 | ARIN | Invalid: origin |
| 206.53.60.0/24 | ARIN | Invalid: origin |
| 206.53.61.0/24 | ARIN | Invalid: origin |
| 206.53.62.0/24 | ARIN | Invalid: origin |
| 206.53.63.0/24 | ARIN | Invalid: origin |
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.