bgpreport

Network · data from 2026-11-12

AS203963 RubikDC SPDNet Telekomunikasyon Hizmetleri Bilgi Teknolojileri Taahhut Sanayi Ve Ticaret A.S.

Registry name: RubikDC SPDNet Telekomunikasyon Hizmetleri Bilgi Teknolojileri Taahhut Sanayi Ve Ticaret A.S., TR · not in PeeringDB

25IPv4 routes 80.0% RPKI valid · 64.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 9 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS203963, seen from no peer

Announced routes

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

206.168.88.0/24 No ROA None 673 100% 67
206.168.89.0/24 No ROA None 673 100% 67
206.168.90.0/24 No ROA None 673 100% 67
206.168.91.0/24 No ROA None 673 100% 67
103.125.147.0/24 No ROA Other origin only 2 0%low visibility 2
31.133.88.0/24 Valid Nonecovered by 31.133.88.0/22 672 100% 67
31.133.89.0/24 Valid Nonecovered by 31.133.88.0/22 672 100% 67
31.133.90.0/24 Valid Nonecovered by 31.133.88.0/22 672 100% 67
31.133.91.0/24 Valid Nonecovered by 31.133.88.0/22 672 100% 67
31.133.80.0/22 Valid RIR databaseRIPE 673 100% 67
103.31.209.0/24 Valid RIR databaseAPNIC 673 100% 67
141.195.124.0/24 Valid RIR databaseARIN 673 100% 67
176.46.142.0/24 Valid RIR databaseRIPE 673 100% 67
176.103.224.0/22 Valid RIR databaseRIPE 673 100% 67
209.145.42.0/24 Valid RIR databaseARIN 673 100% 67
216.24.223.0/24 Valid RIR databaseARIN 673 100% 67
91.228.12.0/24 Valid RIR databaseRIPE 672 100% 67
91.228.14.0/24 Valid RIR databaseRIPE 672 100% 67
91.228.15.0/24 Valid RIR databaseRIPE 672 100% 67
94.154.37.0/24 Valid RIR databaseRIPE 672 100% 67
94.154.38.0/24 Valid RIR databaseRIPE 672 100% 67
94.154.41.0/24 Valid RIR databaseRIPE 672 100% 67
94.154.44.0/24 Valid RIR databaseRIPE 672 100% 67
195.211.188.0/24 Valid RIR databaseRIPE 672 100% 67
167.253.50.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS203963 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 31 are in fix.csv.

  • ROA: none5
  • Route object: none9
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none206.168.88.0/24No ROA covers it. Add a ROA for AS203963, maxLength 24.673 of 673
Route object: none206.168.88.0/24No route object for it. Add a route object with origin AS203963 in the RIR database for the space.673 of 673
ROA: none206.168.89.0/24No ROA covers it. Add a ROA for AS203963, maxLength 24.673 of 673
Route object: none206.168.89.0/24No route object for it. Add a route object with origin AS203963 in the RIR database for the space.673 of 673
ROA: none206.168.90.0/24No ROA covers it. Add a ROA for AS203963, maxLength 24.673 of 673
Route object: none206.168.90.0/24No route object for it. Add a route object with origin AS203963 in the RIR database for the space.673 of 673
ROA: none206.168.91.0/24No ROA covers it. Add a ROA for AS203963, maxLength 24.673 of 673
Route object: none206.168.91.0/24No route object for it. Add a route object with origin AS203963 in the RIR database for the space.673 of 673
ROA: none103.125.147.0/24No ROA covers it. Add a ROA for AS203963, maxLength 24.2 of 673
Route object: none103.125.147.0/24Route objects for it name AS834. Add a route object with origin AS203963 in the RIR database for the space.2 of 673
Route object: none31.133.88.0/24No route object for it. A route object for 31.133.88.0/22 with origin AS203963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203963 in the RIR database for the space.672 of 673
Route object: none31.133.89.0/24No route object for it. A route object for 31.133.88.0/22 with origin AS203963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203963 in the RIR database for the space.672 of 673
Route object: none31.133.90.0/24No route object for it. A route object for 31.133.88.0/22 with origin AS203963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203963 in the RIR database for the space.672 of 673
Route object: none31.133.91.0/24No route object for it. A route object for 31.133.88.0/22 with origin AS203963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203963 in the RIR database for the space.672 of 673

Route objects not announced

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

31.133.88.0/22RIPEValid
64.190.213.0/24ARINInvalid: origin
94.74.156.0/24RIPEValid
94.74.159.0/24RIPEValid
139.177.145.0/24ARINInvalid: origin
139.177.151.0/24ARINInvalid: origin
149.19.197.0/24ARINInvalid: origin
162.33.163.0/24ARINInvalid: origin
162.33.166.0/24ARINInvalid: origin
176.46.136.0/24RIPEValid
176.46.150.0/24RIPEValid
200.229.22.0/24ARINInvalid: origin
212.134.128.0/22RIPEInvalid: origin
212.134.136.0/22RIPEInvalid: origin
212.134.144.0/22RIPEInvalid: origin
212.134.152.0/22RIPEInvalid: origin
212.134.160.0/22RIPEInvalid: origin

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.