Network · data from 2026-11-12
AS62533 Ascendum-IMS, LLC
Registry name: AIMS-VTP-US - Ascendum-IMS, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62533, 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.
| 198.178.145.0/24 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 104.219.70.0/23 | Valid | Nonecovered by 104.219.68.0/22 | 671 100% |
| 104.219.68.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 69.61.187.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.68.85.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS62533'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 9 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 198.178.145.0/24 | No ROA covers it. Add a ROA for AS62533, maxLength 24. |
| Route object: RIR | 198.178.145.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: none | 104.219.70.0/23 | No route object for it. A route object for 104.219.68.0/22 with origin AS62533 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62533 in the RIR database for the space. |
| Route object: RIR | 104.219.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62533 whose prefix no peer sees AS62533 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 50.59.56.0/24 | RADB | No ROA |
| 104.219.68.0/22 | ALTDB, RADB | No ROA |
| 104.219.69.0/24 | RADB | Valid |
| 192.195.109.0/24 | RADB | No ROA |
| 198.49.143.0/24 | ALTDB, RADB | 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.