User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
clarity.microsoft.com · Cloud & developer
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 min ago. Last stored result reached it in 153 ms.
No status feed
Microsoft Clarity does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 14:15 | 0 | 0.0 | 142 ms | 0 |
| 14:30 | 0 | 0.0 | 87 ms | 0 |
| 14:45 | 0 | 0.0 | 141 ms | 0 |
| 15:00 | 0 | 0.0 | 127 ms | 0 |
| 15:15 | 0 | 0.0 | 191 ms | 0 |
| 15:30 | 0 | 0.0 | 233 ms | 0 |
| 15:45 | 0 | 0.0 | 180 ms | 0 |
| 16:00 | 0 | 0.0 | 94 ms | 0 |
| 16:15 | 0 | 0.0 | 148 ms | 0 |
| 16:30 | 0 | 0.0 | 114 ms | 0 |
| 16:45 | 0 | 0.0 | 191 ms | 0 |
| 17:00 | 0 | 0.0 | 154 ms | 0 |
| 17:15 | 0 | 0.0 | 183 ms | 0 |
| 17:30 | 0 | 0.0 | 133 ms | 0 |
| 17:45 | 0 | 0.0 | 171 ms | 0 |
| 18:00 | 0 | 0.0 | 174 ms | 0 |
| 18:15 | 0 | 0.0 | 172 ms | 0 |
| 18:30 | 0 | 0.0 | 119 ms | 0 |
| 18:45 | 0 | 0.0 | 106 ms | 0 |
| 19:00 | 0 | 0.0 | 141 ms | 0 |
| 19:15 | 0 | 0.0 | 230 ms | 0 |
| 19:30 | 0 | 0.0 | 134 ms | 0 |
| 19:45 | 0 | 0.0 | 192 ms | 0 |
| 20:00 | 0 | 0.0 | 223 ms | 0 |
| 20:15 | 0 | 0.0 | 167 ms | 0 |
| 20:30 | 0 | 0.0 | 195 ms | 0 |
| 20:45 | 0 | 0.0 | 188 ms | 0 |
| 21:00 | 0 | 0.0 | 170 ms | 0 |
| 21:15 | 0 | 0.0 | 156 ms | 0 |
| 21:30 | 0 | 0.0 | 166 ms | 0 |
| 21:45 | 0 | 0.0 | 171 ms | 0 |
| 22:00 | 0 | 0.0 | 169 ms | 0 |
| 22:15 | 0 | 0.0 | 164 ms | 0 |
| 22:30 | 0 | 0.0 | 166 ms | 0 |
| 22:45 | 0 | 0.0 | 188 ms | 0 |
| 23:00 | 0 | 0.0 | 117 ms | 0 |
| 23:15 | 0 | 0.0 | 168 ms | 0 |
| 23:30 | 0 | 0.0 | 128 ms | 0 |
| 23:45 | 0 | 0.0 | 174 ms | 0 |
| 00:00 | 0 | 0.0 | 216 ms | 0 |
| 00:15 | 0 | 0.0 | 160 ms | 0 |
| 00:30 | 0 | 0.0 | 124 ms | 0 |
| 00:45 | 0 | 0.0 | 152 ms | 0 |
| 01:00 | 0 | 0.0 | 169 ms | 0 |
| 01:15 | 0 | 0.0 | 180 ms | 0 |
| 01:30 | 0 | 0.0 | 155 ms | 0 |
| 01:45 | 0 | 0.0 | 173 ms | 0 |
| 02:00 | 0 | 0.0 | 160 ms | 0 |
99.87% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 5 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Microsoft Clarity yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Microsoft Clarity goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Microsoft Clarity, at clarity.microsoft.com, is one of the Cloud & developer services we monitor. Live checks and user reports.
Microsoft Clarity has no official status feed we can read, so this page relies on our own checks and user reports.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 99.87% over 5 days of checks. No public incidents logged since monitoring began 5 days ago.
Response time over the last 24 hours: 160 ms average, 60–342 ms range across 237 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Microsoft Clarity incident since monitoring began 5 days ago.
From our own checks: 99.87% over 5 days of checks.
160 ms on average over the last 24 hours (60–342 ms).
Not one we can read. This page uses independent checks of clarity.microsoft.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Microsoft Clarity here at once, the problem is on Microsoft Clarity's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Microsoft Clarity. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.