Share via

Sudden Latency Spikes on Azure Blob Storage When Serving Video Segments

juan perez 0 Reputation points
2025-11-28T18:03:21.1866667+00:00

Hi, I’m running a small streaming website (delivering HLS video segments), and I’m using Azure Blob Storage + Azure CDN to serve the media files. Everything works smoothly most of the time, but during traffic peaks (mostly evenings in Ecuador and Argentina), I’m noticing random latency spikes when retrieving .ts segment files.

Some details:

Storage tier: Hot

Redundancy: LRS

CDN: Azure Front Door (Classic)

Average segment request time: ~40–60 ms

Spike request times: 800 ms to 2 seconds

No errors or throttling messages in monitoring

Happens across multiple ISPs

I’m trying to figure out if this is:

Blob Storage request throttling, even though I don’t see 429s

Azure Front Door caching behavior (maybe forced revalidation?)

Inefficient directory structure for HLS segments

Network routing changes from Azure edge locations during peak hours

Questions:

  1. Is there a recommended way to monitor real-time per-request latency from Blob Storage to confirm whether throttling or backend issues are occurring?
  2. Should I switch to Azure CDN (Standard/Microsoft) or Front Door Premium for more stable edge caching of HLS segments?
  3. Does Azure have best-practice guidance for storing large numbers of small media files (HLS chunks) to reduce latency?
  4. Would enabling CDN compression or changing cache-control headers help reduce revalidation at peak times?

Any guidance or diagnostic steps would be greatly appreciated. I’m trying to determine whether my architecture needs redesigning or if this behavior is normal during regional traffic peaks.

Azure Storage
Azure Storage

Globally unique resources that provide access to data management services and serve as the parent namespace for the services.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2025-11-28T18:03:34.8233333+00:00

    To monitor real-time per-request latency from Azure Blob Storage, you can utilize Azure Storage Analytics logs. These logs provide insights into the performance of your storage requests, including latency metrics. You can download the logs and analyze them to identify any spikes in latency and correlate them with your traffic patterns. Additionally, using Azure Monitor can help you track performance metrics and set up alerts for unusual latency behavior.

    Regarding your CDN setup, switching to Azure CDN (Standard/Microsoft) or Front Door Premium could potentially offer more stable edge caching, which may help reduce latency spikes during peak traffic times. Both options provide advanced caching capabilities that can improve performance.

    For best practices in storing large numbers of small media files like HLS chunks, consider organizing your files efficiently to minimize retrieval times. This could involve optimizing your directory structure to reduce the number of requests needed to access segments.

    Enabling CDN compression and adjusting cache-control headers can also help reduce revalidation at peak times. Compression can decrease the size of the data being transferred, while proper cache-control settings can improve caching behavior and reduce unnecessary requests to your storage.

    In summary, monitoring your latency using Azure Storage Analytics, considering a CDN upgrade, optimizing your file storage, and adjusting caching strategies may help address the latency spikes you're experiencing during peak hours.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.