Azure Region Pulse Assessment
Azure placement & network assessment

Measure first.
Place workloads smarter.

Azure region assessment using repeated HTTPS RTT samples, median, p95, timing variation, reliability and workload-aware scoring. By default, the tool runs a Quick test across European Azure regions using the General Azure workload profile. You can change the scope to another geography or Global at any time.

Your location
Not detected
Optional · only used for distance/map.
Test ID
—
Reference for reports.
Completed
0
No test running.
Browser downlink
—
Connection API estimate only.
Previous winner
—
No local history yet.
Last test
—
Local browser time.
Ready to assess.

Geographic view

Actual country/coastline context with latency-coded candidate regions.

<50 ms50–99 ms100–149 ms150+ msNo result
Lines show geographic relationship only — they do not represent the actual ISP/BGP or Microsoft backbone route.

Azure region ranking

For AVD, the lowest healthy median RTT wins globally. p95 and stability are used only when calculated medians are exactly equal. Other profiles use the broader workload score.

AVD profileDeep test
RankRegionDistanceMedianp95VariationSuccessStabilityScoreWorkloadZonesPaired regionSamples
No test results yet.

Local history

Up to 8 assessment summaries are stored only in this browser. This lets you compare changes across time without a backend.

No history yet.

Client report

Add optional labels before using Print / PDF. Your browser's print dialog can save the assessment as a PDF.

Throughput validation

Latency probes use tiny files and cannot honestly measure bandwidth. For a real Azure throughput check, use a sequential 100 MiB Azure Blob download. Parallel region tests would divide your connection and distort results.

Run this after the latency assessment against your top 1–3 shortlisted regions.
Manual coordinates / privacy / assessment notes
Privacy: browser geolocation is used only in this page to calculate geographic distance. It is not uploaded by the tool. Latency requests go to public Azure Storage probe endpoints. The RTT probes use opaque no-CORS HEAD requests so the measurement does not depend on the website's Origin being whitelisted by each Azure Storage account. Each current AzureSpeed storage endpoint is validated first with a HEAD request and a 2-second timeout. Timed-out probes are dropped immediately, and a responsive probe is dropped if it later fails twice consecutively. IP/ISP information is fetched only when you press the network button. History uses browser localStorage. Export, copy, share-link and print actions happen only when you request them.
AVD: Microsoft recommends client-to-host-pool-region RTT below 150 ms, and AVD Insights describes interaction below 100 ms as generally ideal. This tool measures HTTPS RTT to Azure Storage in the region, so it is a regional proxy rather than an end-to-end AVD session-host test. RDP Shortpath/UDP and actual session-host performance still require validation in the deployed AVD environment. For AVD ranking, the lowest healthy median RTT wins. p95 and stability are used only when calculated medians are exactly equal; the composite network-quality score is informational and cannot make a slower-median AVD region win. Stability uses median-centred robust variation so an isolated slow browser/network sample does not collapse the stability score.
Service availability: region placement must also consider service availability, cost, compliance, data residency and resilience. The workload selector changes scoring and guidance; it does not claim that every selected Azure product is available in every region.
Build: 2026-08-14 global v6.5 · shared assessment view · Metadata snapshot verified against Microsoft Azure public region documentation on 14 Aug 2026 (availability zones, pair, geography and programmatic name). AVD latency guidance: Microsoft Learn AVD prerequisites / Insights. Latency probe infrastructure: the current azurespeed.com Azure Storage convention (s8<regionId>.blob.core.windows.net/public/latency-test.json), using the same regional storage-account family as the reference latency test. Throughput validation recommendation: sequential 100 MiB Azure Blob download methodology used by AzureSpeed.com.