diff --git a/spec/datadog/profiling/validate_benchmarks_spec.rb b/spec/datadog/profiling/validate_benchmarks_spec.rb
index f91cbf06f15..5379fd2bb0f 100644
--- a/spec/datadog/profiling/validate_benchmarks_spec.rb
+++ b/spec/datadog/profiling/validate_benchmarks_spec.rb
@@ -1,7 +1,24 @@
 require "datadog/profiling/spec_helper"
 
 RSpec.describe "Profiling benchmarks", :memcheck_valgrind_skip do
-  before { skip_if_profiling_not_supported(self) }
+  before do
+    skip_if_profiling_not_supported(self)
+
+    # @ivoanjo: We've seen these tests be flaky especially on Ruby 2.6: https://github.com/DataDog/dd-trace-rb/pull/4947
+    # Even when trying to get a backtrace out of Ruby, all we saw was one of the Ruby threads sleeping
+    # e.g. https://github.com/DataDog/dd-trace-rb/actions/runs/19484921634/job/55765012312#step:5:8980 :
+    #
+    # -- Control frame information -----------------------------------------------
+    # c:0004 p:---- s:0014 e:000013 CFUNC  :sleep
+    # c:0003 p:0005 s:0010 e:000009 BLOCK  /__w/dd-trace-rb/dd-trace-rb/benchmarks/profiling_sample_loop_v2.rb:16
+    # c:0002 p:0011 s:0007 e:000006 BLOCK  /__w/dd-trace-rb/dd-trace-rb/spec/spec_helper.rb:290 [FINISH]
+    # c:0001 p:---- s:0003 e:000002 (none) [FINISH]
+    #
+    # Because the objective of this spec is making sure the benchmarks don't bitrot, and seeing as this flakiness seems
+    # to especially affect 2.6 but we have no indication otherwise that we have issues in Ruby 2.6, I decided to skip
+    # this for now and rely on this spec running on other Ruby versions to validate the benchmark is ok.
+    skip("Skipping on Ruby 2.6 as it's flaky and we couldn't figure out why yet") if RUBY_VERSION.start_with?("2.6")
+  end
 
   around do |example|
     ClimateControl.modify("VALIDATE_BENCHMARK" => "true") do