bgpreport

Network · data from 2026-11-12

AS197450 SUNUCUN

Registry name: SUNUCUN Sunucun Bilgi Iletisim Teknolojileri ve Ticaret Ltd. Sti., TR · PeeringDB

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

Announced routes

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

212.135.180.0/23 Invalid: origin Other origin only 16 2%low visibility 16
103.205.180.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.205.181.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.205.182.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.205.183.0/24 Invalid: origin Other origin only 2 0%low visibility 2
59.152.60.0/24 Invalid: origin Other origin only 1 0%low visibility 1
59.152.61.0/24 Invalid: origin Other origin only 1 0%low visibility 1
212.135.12.0/23 Invalid: origin RIR databaseRIPE 1 0%low visibility 2
84.37.142.0/23 Valid Other origin only 671 100% 67
185.221.64.0/24 Valid None 671 100% 67
212.64.201.0/24 Valid Other origin only 671 100% 67
212.64.202.0/24 Valid Other origin only 671 100% 67
212.64.210.0/24 Valid Other origin only 671 100% 67
212.64.211.0/24 Valid Other origin only 671 100% 67
212.64.216.0/24 Valid Other origin only 671 100% 67
213.201.220.0/23 Valid None 671 100% 67
23.26.107.0/24 Valid RIR databaseARIN 671 100% 67
23.26.231.0/24 Valid RIR databaseARIN 671 100% 67
50.114.99.0/24 Valid RIR databaseARIN 671 100% 67
50.114.243.0/24 Valid RIR databaseARIN 671 100% 67
64.64.103.0/24 Valid RIR databaseARIN 671 100% 67
84.37.0.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.6.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.18.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.26.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.30.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.60.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.72.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.76.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.88.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.92.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.96.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.152.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.156.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.160.0/23 Valid RIR databaseRIPE 671 100% 67
84.37.164.0/23 Valid RIR databaseRIPE 671 100% 67
108.165.75.0/24 Valid RIR databaseARIN 671 100% 67
108.165.161.0/24 Valid RIR databaseARIN 671 100% 67
108.165.227.0/24 Valid RIR databaseARIN 671 100% 67
166.0.153.0/24 Valid RIR databaseARIN 671 100% 67
166.0.230.0/24 Valid RIR databaseARIN 671 100% 67
166.0.249.0/24 Valid RIR databaseARIN 671 100% 67
185.113.223.0/24 Valid RIR databaseRIPE 671 100% 67
185.133.32.0/24 Valid RIR databaseRIPE 671 100% 67
188.132.232.0/24 Valid RIR databaseRIPE 671 100% 67
195.178.137.0/24 Valid RIR databaseRIPE 671 100% 67
195.178.138.0/24 Valid RIR databaseRIPE 671 100% 67
201.7.20.0/23 Valid RIR databaseRIPE 671 100% 67
212.64.199.0/24 Valid RIR databaseRIPE 671 100% 67
212.64.215.0/24 Valid RIR databaseRIPE 671 100% 67
213.201.150.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.152.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.156.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.160.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.164.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.168.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.172.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.176.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.180.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.184.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.188.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.192.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.212.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.216.0/23 Valid RIR databaseRIPE 671 100% 67
213.201.232.0/23 Valid RIR databaseRIPE 671 100% 67
216.109.180.0/24 Valid RIR databaseARIN 671 100% 67
216.109.181.0/24 Valid RIR databaseARIN 671 100% 67
216.109.182.0/24 Valid RIR databaseARIN 671 100% 67
216.109.183.0/24 Valid RIR databaseARIN 671 100% 67
45.128.233.0/24 Valid RIR databaseRIPE 670 100% 67
45.138.180.0/24 Valid RIR databaseRIPE 670 100% 67
2a12:e681::/32 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS197450'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 48 are in fix.csv.

  • ROA: origin8
  • Route object: none15
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: origin212.135.180.0/23ROAs covering it name AS216213, not AS197450. If AS197450 should announce it, add a ROA for AS197450.16 of 673
Route object: none212.135.180.0/23Route objects for it name AS216213. Add a route object with origin AS197450 in the RIR database for the space.16 of 673
ROA: origin103.205.180.0/24ROAs covering it name AS152605, not AS197450. If AS197450 should announce it, add a ROA for AS197450.2 of 673
Route object: none103.205.180.0/24Route objects for it name AS152605. Add a route object with origin AS197450 in the RIR database for the space.2 of 673
ROA: origin103.205.181.0/24ROAs covering it name AS152605, not AS197450. If AS197450 should announce it, add a ROA for AS197450.2 of 673
Route object: none103.205.181.0/24Route objects for it name AS152605. Add a route object with origin AS197450 in the RIR database for the space.2 of 673
ROA: origin103.205.182.0/24ROAs covering it name AS152605, not AS197450. If AS197450 should announce it, add a ROA for AS197450.2 of 673
Route object: none103.205.182.0/24Route objects for it name AS152605. Add a route object with origin AS197450 in the RIR database for the space.2 of 673
ROA: origin103.205.183.0/24ROAs covering it name AS152605, not AS197450. If AS197450 should announce it, add a ROA for AS197450.2 of 673
Route object: none103.205.183.0/24Route objects for it name AS152605. Add a route object with origin AS197450 in the RIR database for the space.2 of 673
ROA: origin59.152.60.0/24ROAs covering it name AS152605, not AS197450. If AS197450 should announce it, add a ROA for AS197450.1 of 673
Route object: none59.152.60.0/24Route objects for it name AS152605. Add a route object with origin AS197450 in the RIR database for the space.1 of 673
ROA: origin59.152.61.0/24ROAs covering it name AS152605, not AS197450. If AS197450 should announce it, add a ROA for AS197450.1 of 673
Route object: none59.152.61.0/24Route objects for it name AS152605. Add a route object with origin AS197450 in the RIR database for the space.1 of 673
ROA: origin212.135.12.0/23ROAs covering it name AS9009, not AS197450. If AS197450 should announce it, add a ROA for AS197450.1 of 673
Route object: none84.37.142.0/23Route objects for it name AS396356. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none185.221.64.0/24No route object for it. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none212.64.201.0/24Route objects for it name AS210099. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none212.64.202.0/24Route objects for it name AS210099. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none212.64.210.0/24Route objects for it name AS210099. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none212.64.211.0/24Route objects for it name AS210099. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none212.64.216.0/24Route objects for it name AS210099. Add a route object with origin AS197450 in the RIR database for the space.671 of 673
Route object: none213.201.220.0/23No route object for it. Add a route object with origin AS197450 in the RIR database for the space.671 of 673

Route objects not announced

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

84.37.56.0/23RIPEValid
84.37.100.0/23RIPEValid
84.37.128.0/23RIPEValid
84.37.172.0/23RIPEValid
156.233.71.0/24AFRINICInvalid: origin
213.201.152.0/22RIPEValid
213.201.164.0/22RIPEValid
213.201.172.0/22RIPEValid
213.201.180.0/22RIPEValid
213.201.192.0/22RIPEValid
213.201.212.0/22RIPEValid
213.201.218.0/23RIPEInvalid: origin
213.201.232.0/22RIPEValid
2a12:e680::/48RIPEValid
2a12:e680:1::/48RIPEValid
2a12:e680:2::/48RIPEValid
2a12:e680:3::/48RIPEValid
2a12:e680:4::/48RIPEValid
2a12:e680:5::/48RIPEValid
2a12:e680:6::/48RIPEValid
2a12:e680:7::/48RIPEValid
2a12:e680:8::/48RIPEValid
2a12:e680:9::/48RIPEValid
2a12:e680:b::/48RIPENo ROA
2a12:e682::/32RIPEValid

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.