bgpreport

Network · data from 2026-11-12

AS198417 DSM-AS DSM Grup Danismanlik Iletisim ve Satis Ticaret Anonim Sirketi

Registry name: DSM-AS DSM Grup Danismanlik Iletisim ve Satis Ticaret Anonim Sirketi, TR · not in PeeringDB

16IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
28Route objects not announced registered with origin AS198417, seen from no peer

Announced routes

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

89.32.124.0/24 Valid RIR databaseRIPE 673 100% 67
89.32.128.0/24 Valid RIR databaseRIPE 673 100% 67
89.41.30.0/24 Valid RIR databaseRIPE 673 100% 67
89.43.39.0/24 Valid RIR databaseRIPE 673 100% 67
92.114.99.0/24 Valid RIR databaseRIPE 673 100% 67
93.114.250.0/24 Valid RIR databaseRIPE 673 100% 67
94.177.119.0/24 Valid RIR databaseRIPE 673 100% 67
159.20.113.0/24 Valid RIR databaseRIPE 673 100% 67
159.20.114.0/24 Valid RIR databaseRIPE 673 100% 67
89.40.131.0/24 Valid RIR databaseRIPE 671 100% 67
89.42.34.0/24 Valid RIR databaseRIPE 671 100% 67
92.114.34.0/24 Valid RIR databaseRIPE 671 100% 67
94.177.64.0/24 Valid RIR databaseRIPE 671 100% 67
188.208.18.0/24 Valid RIR databaseRIPE 671 100% 67
188.240.16.0/24 Valid RIR databaseRIPE 671 100% 67
188.240.46.0/24 Valid RIR databaseRIPE 671 100% 67
2a10:3ec0:32::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS198417 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 28 are in fix.csv.

  • Route object: not announced28

Route objects not announced

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

31.14.64.0/24RIPEValid
31.14.218.0/24RIPEValid
31.14.232.0/24RIPEValid
31.14.253.0/24RIPEValid
37.153.137.0/24RIPEValid
86.105.194.0/24RIPEValid
86.105.197.0/24RIPEValid
86.106.21.0/24RIPEValid
86.106.82.0/24RIPEValid
86.106.178.0/24RIPEValid
86.107.188.0/24RIPEValid
89.32.201.0/24RIPEValid
89.32.205.0/24RIPEValid
89.39.151.0/24RIPENo ROA
89.46.128.0/24RIPEValid
89.46.129.0/24RIPEValid
89.46.130.0/24RIPEValid
89.47.35.0/24RIPEValid
93.113.88.0/24RIPEValid
93.113.108.0/24RIPEValid
93.114.141.0/24RIPEValid
159.20.115.0/24RIPEValid
159.20.116.0/24RIPEValid
188.215.40.0/24RIPEValid
188.215.41.0/24RIPEValid
188.215.42.0/24RIPEValid
188.215.43.0/24RIPEValid
2a10:3ec0::/29RIPEValid

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.