Network · data from 2026-11-12
AS48645 Solvinity
Registry name: SOLVINITY-NL-2 Solvinity B.V., NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48645, 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.63.23.0/24 | Valid | Nonecovered by 185.63.22.0/23 | 673 100% |
| 94.143.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.20.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 94.143.208.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 94.143.212.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.63.20.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.63.22.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:27c8::/32 | Valid | RIR databaseRIPE | 636 100% |
| 94.143.208.0/23 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 94.143.210.0/23 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 94.143.212.0/23 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 94.143.214.0/23 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 185.63.20.0/24 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 185.63.21.0/24 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 185.63.22.0/24 | Valid | RIR databaseRIPE | 15 2%low visibility |
AS-SET
AS48645'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 1 are in fix.csv.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.63.23.0/24 | No route object for it. A route object for 185.63.22.0/23 with origin AS48645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48645 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS48645 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.