bgpreport

Network · data from 2026-11-12

AS203804 VDSGLOBAL VDS GLOBAL YAZILIM ARGE GELISTIRME LIMITED SIRKETI

Registry name: VDSGLOBAL VDS GLOBAL YAZILIM ARGE GELISTIRME LIMITED SIRKETI, TR · not in PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
39Route objects not announced registered with origin AS203804, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203804, 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.

2.56.108.0/24 Valid RIR databaseRIPE 671 100% 66
2.56.109.0/24 Valid RIR databaseRIPE 671 100% 66
31.58.251.0/24 Valid RIR databaseRIPE 671 100% 66
45.81.113.0/24 Valid RIR databaseRIPE 671 100% 67
85.209.120.0/24 Valid RIR databaseRIPE 671 100% 66
193.164.5.0/24 Valid RIR databaseRIPE 671 100% 66
194.15.52.0/24 Valid RIR databaseRIPE 671 100% 66
45.81.115.0/24 Valid RIR databaseRIPE 670 100% 66
45.88.139.0/24 Valid RIR databaseRIPE 670 100% 66
45.151.2.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.130.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.165.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.202.0/24 Valid RIR databaseRIPE 670 100% 67
193.57.41.0/24 Valid RIR databaseRIPE 670 100% 66
45.132.181.0/24 Valid RIR databaseRIPE 666 99% 66

AS-SET

AS203804 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 39 are in fix.csv.

  • Route object: not announced39

Route objects not announced

Route objects with origin AS203804 whose prefix no peer sees AS203804 announce. Many are kept on purpose (backup routes, space announced only in some places).

31.58.247.0/24RIPEValid
31.58.250.0/24RIPEValid
66.208.92.0/24ARINValid
66.208.93.0/24ARINValid
66.208.94.0/24ARINValid
66.208.95.0/24ARINValid
185.7.242.0/24RIPEValid
185.81.153.0/24RIPEValid
2406:840:f230::/44APNICValid
2406:840:f230::/45APNICValid
2406:840:f230::/46APNICValid
2406:840:f230::/47APNICValid
2406:840:f230::/48APNICValid
2406:840:f231::/48APNICValid
2406:840:f232::/47APNICValid
2406:840:f232::/48APNICValid
2406:840:f233::/48APNICValid
2406:840:f234::/46APNICValid
2406:840:f234::/47APNICValid
2406:840:f234::/48APNICValid
2406:840:f235::/48APNICValid
2406:840:f236::/47APNICValid
2406:840:f236::/48APNICValid
2406:840:f237::/48APNICValid
2406:840:f238::/45APNICValid
2406:840:f238::/46APNICValid
2406:840:f238::/47APNICValid
2406:840:f238::/48APNICValid
2406:840:f239::/48APNICValid
2406:840:f23a::/47APNICValid
2406:840:f23a::/48APNICValid
2406:840:f23b::/48APNICValid
2406:840:f23c::/46APNICValid
2406:840:f23c::/47APNICValid
2406:840:f23c::/48APNICValid
2406:840:f23d::/48APNICValid
2406:840:f23e::/47APNICValid
2406:840:f23e::/48APNICValid
2406:840:f23f::/48APNICValid

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.