Network · data from 2026-11-12
AS19152 IBMCCH-TOR - IBM
Registry name: IBMCCH-TOR - IBM, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19152, 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.
| 129.33.162.0/24 | No ROA | Nonecovered by 129.33.160.0/21 | 2 0%low visibility |
| 170.226.56.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS19152 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 52 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced48
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 129.33.162.0/24 | No ROA covers it. Add a ROA for AS19152, maxLength 24. |
| Route object: none | 129.33.162.0/24 | No route object for it. A route object for 129.33.160.0/21 with origin AS19152 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19152 in the RIR database for the space. |
| ROA: none | 170.226.56.0/24 | No ROA covers it. Add a ROA for AS19152, maxLength 24. |
| Route object: RIR | 170.226.56.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19152 whose prefix no peer sees AS19152 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 32.97.80.0/21 | BELL | No ROA |
| 32.97.84.0/22 | BELL | No ROA |
| 32.97.86.0/24 | BELL | No ROA |
| 129.33.160.0/19 | BELL | No ROA |
| 129.33.160.0/21 | RADB | No ROA |
| 129.33.160.0/25 | BELL | No ROA |
| 129.33.168.0/22 | RADB | No ROA |
| 129.33.172.0/23 | RADB | No ROA |
| 129.33.174.0/23 | RADB | No ROA |
| 129.33.176.0/24 | RADB | No ROA |
| 129.33.177.0/24 | RADB | No ROA |
| 129.33.179.0/24 | RADB | No ROA |
| 129.33.180.0/24 | RADB | No ROA |
| 129.33.181.0/24 | RADB | No ROA |
| 129.33.182.0/23 | RADB | No ROA |
| 129.33.184.0/21 | RADB | No ROA |
| 129.33.189.0/24 | BELL | No ROA |
| 129.33.191.0/25 | BELL | No ROA |
| 129.41.192.0/20 | BELL | No ROA |
| 129.41.208.0/20 | BELL | No ROA |
| 149.131.32.0/24 | RADB | No ROA |
| 149.131.49.0/24 | BELL, RADB | No ROA |
| 170.224.210.0/24 | RADB | No ROA |
| 170.225.240.0/24 | BELL, RADB | No ROA |
| 170.226.0.0/22 | BELL, RADB | No ROA |
| 170.226.4.0/24 | BELL | No ROA |
| 192.75.120.0/22 | BELL | No ROA |
| 192.91.193.0/24 | RADB | No ROA |
| 198.20.8.0/24 | BELL, RADB | No ROA |
| 198.20.9.0/24 | BELL, RADB | No ROA |
| 198.20.14.0/24 | BELL | No ROA |
| 198.20.15.0/24 | BELL | No ROA |
| 198.235.140.0/24 | BELL | No ROA |
| 198.235.141.0/24 | BELL | No ROA |
| 198.235.142.0/24 | BELL | No ROA |
| 198.235.143.0/24 | BELL, RADB | No ROA |
| 199.185.26.0/24 | BELL, RADB | No ROA |
| 199.185.27.0/24 | BELL | No ROA |
| 204.101.198.0/23 | BELL | Invalid: origin |
| 204.101.199.0/26 | BELL | Invalid: origin |
| 205.233.176.0/24 | BELL | No ROA |
| 206.47.128.0/22 | BELL, RADB | No ROA |
| 206.47.218.0/23 | BELL | No ROA |
| 207.61.42.0/24 | BELL | Invalid: origin |
| 207.164.134.0/23 | BELL | Invalid: origin |
| 207.236.97.96/27 | BELL | Invalid: origin |
| 216.208.175.0/24 | BELL, RADB | Valid |
| 216.208.176.0/24 | BELL, RADB | 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.