Network · data from 2026-11-12
AS29319 Informational-measuring systems
Registry name: ASN-IMSYS Informational-measuring systems Ltd., RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29319, 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.
| 217.70.18.0/24 | Valid | Nonecovered by 217.70.16.0/20 | 670 100% |
| 84.23.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 84.23.40.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 84.23.44.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 217.70.16.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 217.70.16.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS29319'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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.70.18.0/24 | No route object for it. A route object for 217.70.16.0/20 with origin AS29319 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29319 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29319 whose prefix no peer sees AS29319 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a03:96c0::/32 | RIPE | 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.