Network · data from 2026-11-12
AS60118 CyberSmartSolutions-AS INVITE Systems SRL
Registry name: CyberSmartSolutions-AS INVITE Systems SRL, RO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60118, 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.
| 185.150.17.0/24 | Invalid: origin | Other origin only | 14 2%low visibility |
| 89.42.26.0/24 | Invalid: origin | None | 0 0%low visibility |
| 80.96.144.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 176.126.236.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 2a02:59e0::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS60118 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.150.17.0/24 | ROAs covering it name AS211462, not AS60118. If AS60118 should announce it, add a ROA for AS60118. |
| Route object: none | 185.150.17.0/24 | Route objects for it name AS211462. Add a route object with origin AS60118 in the RIR database for the space. |
| ROA: origin | 89.42.26.0/24 | ROAs covering it name AS205275, not AS60118. If AS60118 should announce it, add a ROA for AS60118. |
| Route object: none | 89.42.26.0/24 | No route object for it. Add a route object with origin AS60118 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS60118 is announced.
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.