diff --git a/apps/company-website/src/pages/blog/real-cost-of-holiday-feature-freeze.mdx b/apps/company-website/src/pages/blog/real-cost-of-holiday-feature-freeze.mdx
index eed60fd..d28b236 100644
--- a/apps/company-website/src/pages/blog/real-cost-of-holiday-feature-freeze.mdx
+++ b/apps/company-website/src/pages/blog/real-cost-of-holiday-feature-freeze.mdx
@@ -47,7 +47,7 @@ That said, I don’t have any internal insight into Sentry’s operations beyond
 Pull requests don’t stop coming in just because deployments pause. Instead, they pile up, waiting for the freeze to lift.
 
 <iframe 
-    src="https://metrics.dxta.dev/getsentry/sentry?chart=MRsOpened&team=1&width=1100&height=360&lines=value&theme=light&dashboard=sentry-feature-freeze" 
+    src="https://metrics.dxta.dev/getsentry/sentry?chart=MRsOpened&team=1&weeks=2024-W48,2024-W49,2024-W50,2024-W51,2024-W52,2025-W01,2025-W02,2025-W03,2025-W04,2025-W05,2025-W06,2025-W07&width=1100&height=360&lines=value&theme=light&dashboard=sentry-feature-freeze" 
     height="360" 
     style={{border: "none", width: "100%", overflowY: "hidden"}}
 >
@@ -59,7 +59,7 @@ The only significant dip occurs in Week 52 (Dec 23 – Dec 29), but activity reb
 Since PRs aren’t being merged and deployed, the time from PR creation to deployment explodes. What was once a smooth, continuous flow turns into a backlog nightmare.
 
 <iframe 
-    src="https://metrics.dxta.dev/getsentry/sentry?chart=DeployTime&team=1&width=1100&height=360&lines=median&theme=light&dashboard=sentry-feature-freeze" 
+    src="https://metrics.dxta.dev/getsentry/sentry?chart=DeployTime&team=1&weeks=2024-W48,2024-W49,2024-W50,2024-W51,2024-W52,2025-W01,2025-W02,2025-W03,2025-W04,2025-W05,2025-W06,2025-W07&width=1100&height=360&lines=median&theme=light&dashboard=sentry-feature-freeze" 
     height="360" 
     style={{border: "none", width: "100%", overflowY: "hidden"}}
     >
@@ -75,7 +75,7 @@ The backlog didn’t clear up as expected—new spikes in Weeks 02, 03, and 04 i
 Once the freeze lifts, everything hits production at once. Instead of small, iterative changes, you get a flood of deployments, increasing the risk of failures.
 
 <iframe 
-    src="https://metrics.dxta.dev/getsentry/sentry?chart=DeployFreq&team=1&width=1100&height=360&lines=value&theme=light&dashboard=sentry-feature-freeze" 
+    src="https://metrics.dxta.dev/getsentry/sentry?chart=DeployFreq&team=1&weeks=2024-W48,2024-W49,2024-W50,2024-W51,2024-W52,2025-W01,2025-W02,2025-W03,2025-W04,2025-W05,2025-W06,2025-W07&width=1100&height=360&lines=value&theme=light&dashboard=sentry-feature-freeze" 
     width="1100" 
     height="360" 
     style={{border: "none", width: "100%", overflowY: "hidden"}}
@@ -96,7 +96,7 @@ Now, the team is dealing with the aftermath; stabilizing, fixing issues, and get
 When pressure mounts, teams are more likely to merge PRs without full reviews. This is a natural reaction to large backlogs but introduces long-term quality concerns.
 
 <iframe 
-    src="https://metrics.dxta.dev/getsentry/sentry?chart=MRsWoReview&team=1&width=1100&height=360&lines=value&theme=light&dashboard=sentry-feature-freeze" 
+    src="https://metrics.dxta.dev/getsentry/sentry?chart=MRsWoReview&team=1&weeks=2024-W48,2024-W49,2024-W50,2024-W51,2024-W52,2025-W01,2025-W02,2025-W03,2025-W04,2025-W05,2025-W06,2025-W07&width=1100&height=360&lines=value&theme=light&dashboard=sentry-feature-freeze" 
     width="1100" 
     height="360" 
     style={{border: "none", width: "100%", overflowY: "hidden"}}