Network · data from 2026-11-12
AS205463 VDSGLOBAL Pembe Gul Isguzar Karagoz
Registry name: VDSGLOBAL Pembe Gul Isguzar Karagoz, TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205463, 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.
| 5.178.103.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 31.58.251.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 2.56.108.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 2.56.109.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 45.81.115.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 45.88.139.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 85.209.120.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 188.132.130.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 188.132.165.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 188.132.202.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 193.57.41.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 193.164.5.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 194.15.52.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS205463 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 11 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.178.103.0/24 | ROAs covering it name AS210980, not AS205463. If AS205463 should announce it, add a ROA for AS205463. |
| Route object: none | 5.178.103.0/24 | Route objects for it name AS210980. Add a route object with origin AS205463 in the RIR database for the space. |
| ROA: origin | 31.58.251.0/24 | ROAs covering it name AS203804, AS219521, not AS205463. If AS205463 should announce it, add a ROA for AS205463. |
| Route object: none | 31.58.251.0/24 | Route objects for it name AS203804, AS219521. Add a route object with origin AS205463 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205463 whose prefix no peer sees AS205463 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.58.236.0/24 | RIPE | Valid |
| 45.81.113.0/24 | RIPE | Valid |
| 45.132.181.0/24 | RIPE | Valid |
| 45.151.2.0/24 | RIPE | Valid |
| 45.192.19.0/24 | AFRINIC | Invalid: origin |
| 45.194.83.0/24 | AFRINIC | Invalid: origin |
| 185.81.153.0/24 | 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.