Network · data from 2026-11-12
AS60638 ISC-Net Informatics Services PJSC
Registry name: ISC-Net Informatics Services PJSC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60638, 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.
| 94.184.140.0/23 | Valid | Nonecovered by 94.184.140.0/22 | 671 100% |
| 94.184.141.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.184.140.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 94.184.140.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS60638 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 3 are in fix.csv.
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 94.184.140.0/23 | No route object for it. A route object for 94.184.140.0/22 with origin AS60638 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60638 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60638 whose prefix no peer sees AS60638 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.184.143.0/24 | RIPE | Valid |
| 2001:14e8:b::/48 | RIPE | 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.