Network · data from 2026-11-12
AS215925 VPSVAULTHOST
Registry name: VPSVAULTHOST VPSVAULT.HOST LTD, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215925, 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.
| 154.90.70.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 45.198.224.0/24 | Valid | RIR databaseAFRINIC, RADB | 666 99% |
| 154.80.128.0/24 | Valid | RIR databaseAFRINIC, RADB | 666 99% |
| 45.194.92.0/24 | Valid | RIR databaseAFRINIC, RADB | 658 98% |
AS-SET
PeeringDB's irr_as_set for AS215925: AS215925:AS-VPSVAULT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS215925 isn't in the set, or no route object for AS215925 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS215925 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS215925:AS-VPSVAULT | In no IRR database read today. | |||||
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 5 are in fix.csv.
- ROA: origin1
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.90.70.0/24 | ROAs covering it name AS17561, AS47764, not AS215925. If AS215925 should announce it, add a ROA for AS215925. |
| AS-SET: not found | AS215925:AS-VPSVAULT | PeeringDB names AS215925:AS-VPSVAULT; no IRR database read has it. |
Route objects not announced
Route objects with origin AS215925 whose prefix no peer sees AS215925 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.194.67.0/24 | AFRINIC | Invalid: origin |
| 45.205.1.0/24 | AFRINIC | Invalid: origin |
| 2a13:c8c4:ff00::/40 | RIPE | Valid |
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.