bgpreport

Network · data from 2026-11-12

AS201021 OnurBilisim-AS Ahmet Onur Guney trading as Onur Bilisim Ve Yazilim Hizmetleri

Registry name: OnurBilisim-AS Ahmet Onur Guney trading as Onur Bilisim Ve Yazilim Hizmetleri, TR · not in PeeringDB

61IPv4 routes 73.8% RPKI valid · 72.1% with a route object
0IPv6 routes
12RPKI invalid 12 origin · 0 maxLength
4No ROA 17 with no route object for this origin
17Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS201021, seen from no peer

Announced routes

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

46.38.141.0/24 Invalid: origin Other origin only 2 0%low visibility 2
77.81.100.0/24 Invalid: origin None 2 0%low visibility 2
89.37.194.0/24 Invalid: origin None 2 0%low visibility 2
89.43.62.0/24 Invalid: origin Other origin only 2 0%low visibility 2
89.45.162.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.143.75.0/24 Invalid: origin Other origin only 2 0%low visibility 2
193.124.200.0/24 Invalid: origin Other origin only 2 0%low visibility 2
193.124.202.0/24 Invalid: origin None 2 0%low visibility 2
194.135.18.0/24 Invalid: origin Other origin only 2 0%low visibility 2
195.58.60.0/24 Invalid: origin Other origin only 2 0%low visibility 2
212.193.12.0/24 Invalid: origin Other origin only 2 0%low visibility 2
212.193.13.0/24 Invalid: origin Other origin only 2 0%low visibility 2
77.81.88.0/24 No ROA Other origin only 2 0%low visibility 2
89.39.125.0/24 No ROA None 2 0%low visibility 2
93.90.75.0/24 No ROA Other origin only 2 0%low visibility 2
188.241.137.0/24 No ROA None 2 0%low visibility 2
212.16.85.0/24 Valid Other origin only 2 0%low visibility 2
185.28.62.0/24 Valid RIR databaseRIPE 671 100% 67
185.84.183.0/24 Valid RIR databaseRIPE 671 100% 66
13.143.211.0/24 Valid RIR databaseRIPE 670 100% 67
13.143.218.0/24 Valid RIR databaseRIPE 670 100% 67
13.143.226.0/24 Valid RIR databaseRIPE 670 100% 67
13.143.238.0/24 Valid RIR databaseRIPE 670 100% 67
13.143.250.0/24 Valid RIR databaseRIPE 670 100% 67
31.77.58.0/24 Valid RIR databaseRIPE 670 100% 67
78.17.182.0/24 Valid RIR databaseRIPE 670 100% 67
78.17.255.0/24 Valid RIR databaseRIPE 670 100% 67
89.125.20.0/24 Valid RIR databaseRIPE 670 100% 67
89.125.252.0/24 Valid RIR databaseRIPE 670 100% 67
104.143.203.0/24 Valid RIR databaseRIPE 670 100% 67
104.143.216.0/24 Valid RIR databaseRIPE 670 100% 67
132.243.72.0/24 Valid RIR databaseRIPE 670 100% 67
132.243.75.0/24 Valid RIR databaseRIPE 670 100% 67
162.35.226.0/24 Valid RIR databaseRIPE 670 100% 67
162.35.228.0/24 Valid RIR databaseRIPE 670 100% 67
163.5.39.0/24 Valid RIR databaseRIPE 670 100% 67
163.5.66.0/24 Valid RIR databaseRIPE 670 100% 67
163.5.182.0/24 Valid RIR databaseRIPE 670 100% 67
163.5.246.0/24 Valid RIR databaseRIPE 670 100% 67
185.28.60.0/24 Valid RIR databaseRIPE 670 100% 67
185.28.63.0/24 Valid RIR databaseRIPE 670 100% 67
185.103.196.0/24 Valid RIR databaseRIPE 670 100% 67
185.103.197.0/24 Valid RIR databaseRIPE 670 100% 67
185.103.199.0/24 Valid RIR databaseRIPE 670 100% 67
185.106.20.0/24 Valid RIR databaseRIPE 670 100% 67
185.176.95.0/24 Valid RIR databaseRIPE 670 100% 67
192.124.188.0/24 Valid RIR databaseRIPE 670 100% 67
194.87.75.0/24 Valid RIR databaseRIPE 670 100% 67
194.87.229.0/24 Valid RIR databaseRIPE 670 100% 67
195.133.43.0/24 Valid RIR databaseRIPE 670 100% 67
195.133.95.0/24 Valid RIR databaseRIPE 670 100% 67
201.10.81.0/24 Valid RIR databaseRIPE 670 100% 67
201.10.95.0/24 Valid RIR databaseRIPE 670 100% 67
212.192.10.0/24 Valid RIR databaseRIPE 670 100% 67
212.192.209.0/24 Valid RIR databaseRIPE 670 100% 67
185.103.198.0/24 Valid RIR databaseRIPE 666 99% 67
185.106.21.0/24 Valid RIR databaseRIPE 666 99% 67
185.28.61.0/24 Valid RIR databaseRIPE 665 99% 67
185.106.23.0/24 Valid RIR databaseRIPE 664 99% 67
185.106.22.0/24 Valid RIR databaseRIPE 663 99% 67
163.5.237.0/24 Valid RIR databaseRIPE 651 97% 67

AS-SET

AS201021 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 33 are in fix.csv.

  • ROA: origin12
  • ROA: none4
  • Route object: none17
ChangePrefix or setDetailFull-table peers
ROA: origin46.38.141.0/24ROAs covering it name AS198566, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none46.38.141.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin77.81.100.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none77.81.100.0/24No route object for it. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin89.37.194.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none89.37.194.0/24No route object for it. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin89.43.62.0/24ROAs covering it name AS198566, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none89.43.62.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin89.45.162.0/24ROAs covering it name AS198566, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none89.45.162.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin185.143.75.0/24ROAs covering it name AS198566, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none185.143.75.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin193.124.200.0/24ROAs covering it name AS218568, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none193.124.200.0/24Route objects for it name AS218568. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin193.124.202.0/24ROAs covering it name AS198566, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none193.124.202.0/24No route object for it. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin194.135.18.0/24ROAs covering it name AS198566, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none194.135.18.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin195.58.60.0/24ROAs covering it name AS214647, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none195.58.60.0/24Route objects for it name AS214647. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin212.193.12.0/24ROAs covering it name AS214647, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none212.193.12.0/24Route objects for it name AS214647. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: origin212.193.13.0/24ROAs covering it name AS214647, not AS201021. If AS201021 should announce it, add a ROA for AS201021.2 of 673
Route object: none212.193.13.0/24Route objects for it name AS214647. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: none77.81.88.0/24No ROA covers it. Add a ROA for AS201021, maxLength 24.2 of 673
Route object: none77.81.88.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: none89.39.125.0/24No ROA covers it. Add a ROA for AS201021, maxLength 24.2 of 673
Route object: none89.39.125.0/24No route object for it. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: none93.90.75.0/24No ROA covers it. Add a ROA for AS201021, maxLength 24.2 of 673
Route object: none93.90.75.0/24Route objects for it name AS133731. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
ROA: none188.241.137.0/24No ROA covers it. Add a ROA for AS201021, maxLength 24.2 of 673
Route object: none188.241.137.0/24No route object for it. Add a route object with origin AS201021 in the RIR database for the space.2 of 673
Route object: none212.16.85.0/24Route objects for it name AS198566. Add a route object with origin AS201021 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS201021 is announced.

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.