Network · data from 2026-11-12
AS39582 Vaultr Veri Merkezi Hizmetleri A.S.
Registry name: VAULTR Vaultr Veri Merkezi Hizmetleri Anonim Sirketi, TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39582, 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.231.109.0/24 | Valid | None | 673 100% |
| 2a02:4300::/29 | Valid | None | 634 100% |
| 37.77.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.4.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.6.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.10.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.135.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.17.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.77.24.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS39582'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 30 are in fix.csv.
- Route object: none2
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.231.109.0/24 | No route object for it. Add a route object with origin AS39582 in the RIR database for the space. |
| Route object: none | 2a02:4300::/29 | No route object for it. Add a route object with origin AS39582 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39582 whose prefix no peer sees AS39582 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.77.0.0/19 | RIPE | Valid |
| 37.77.0.0/24 | RIPE | Valid |
| 37.77.3.0/24 | RIPE | Valid |
| 37.77.7.0/24 | RIPE | Valid |
| 37.77.8.0/24 | RIPE | Valid |
| 37.77.11.0/24 | RIPE | Valid |
| 37.77.13.0/24 | RIPE | Valid |
| 37.77.14.0/24 | RIPE | Valid |
| 37.77.16.0/23 | RIPE | Valid |
| 37.77.16.0/24 | RIPE | Valid |
| 37.77.17.0/24 | RIPE | Valid |
| 37.77.18.0/23 | RIPE | Valid |
| 37.77.18.0/24 | RIPE | Valid |
| 37.77.19.0/24 | RIPE | Valid |
| 37.77.20.0/24 | RIPE | Valid |
| 37.77.22.0/24 | RIPE | Valid |
| 37.77.23.0/24 | RIPE | Valid |
| 37.77.25.0/24 | RIPE | Valid |
| 37.77.30.0/24 | RIPE | Valid |
| 91.142.142.0/24 | RIPE | Invalid: origin |
| 91.235.64.0/24 | RIPE | Invalid: origin |
| 185.10.243.0/24 | RIPE | Valid |
| 185.29.192.0/24 | RIPE | Valid |
| 185.29.193.0/24 | RIPE | Valid |
| 185.29.194.0/24 | RIPE | Valid |
| 185.29.195.0/24 | RIPE | Valid |
| 185.130.56.0/24 | RIPE | Valid |
| 2a02:4300::/32 | 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.