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 1 min ago. Last stored result reached it in 133 ms.
No status feed
Microsoft Clarity does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Thu 10 | 0 | 0.0 | 154 ms | 0 |
| Thu 11 | 0 | 0.0 | 147 ms | 0 |
| Thu 12 | 0 | 0.0 | 133 ms | 0 |
| Thu 13 | 0 | 0.0 | 140 ms | 0 |
| Thu 14 | 0 | 0.0 | 169 ms | 0 |
| Thu 15 | 0 | 0.0 | 194 ms | 0 |
| Thu 16 | 0 | 0.0 | 205 ms | 0 |
| Thu 17 | 0 | 0.0 | 205 ms | 0 |
| Thu 18 | 0 | 0.0 | 255 ms | 0 |
| Thu 19 | 0 | 0.0 | 245 ms | 0 |
| Thu 20 | 0 | 0.0 | 195 ms | 0 |
| Thu 21 | 0 | 0.0 | 206 ms | 0 |
| Thu 22 | 0 | 0.0 | 206 ms | 0 |
| Thu 23 | 0 | 0.0 | 177 ms | 0 |
| Fri 00 | 0 | 0.0 | 155 ms | 0 |
| Fri 01 | 0 | 0.0 | 166 ms | 0 |
| Fri 02 | 0 | 0.0 | 170 ms | 0 |
| Fri 03 | 0 | 0.0 | 167 ms | 0 |
| Fri 04 | 0 | 0.0 | 216 ms | 0 |
| Fri 05 | 0 | 0.0 | 183 ms | 0 |
| Fri 06 | 0 | 0.0 | 156 ms | 0 |
| Fri 07 | 0 | 0.0 | 181 ms | 0 |
| Fri 08 | 0 | 0.0 | 164 ms | 0 |
| Fri 09 | 0 | 0.0 | 146 ms | 0 |
| Fri 10 | 0 | 0.0 | 183 ms | 0 |
| Fri 11 | 0 | 0.0 | 191 ms | 0 |
| Fri 12 | 0 | 0.0 | 145 ms | 0 |
| Fri 13 | 0 | 0.0 | 180 ms | 0 |
| Fri 14 | 0 | 0.0 | 184 ms | 0 |
| Fri 15 | 0 | 0.0 | 236 ms | 0 |
| Fri 16 | 0 | 0.0 | 202 ms | 0 |
| Fri 17 | 0 | 0.0 | 212 ms | 0 |
| Fri 18 | 0 | 0.0 | 170 ms | 0 |
| Fri 19 | 0 | 0.0 | 167 ms | 0 |
| Fri 20 | 0 | 0.0 | 164 ms | 0 |
| Fri 21 | 0 | 0.0 | 163 ms | 0 |
| Fri 22 | 0 | 0.0 | 182 ms | 0 |
| Fri 23 | 0 | 0.0 | 144 ms | 0 |
| Sat 00 | 0 | 0.0 | 156 ms | 0 |
| Sat 01 | 0 | 0.0 | 161 ms | 0 |
| Sat 02 | 0 | 0.0 | 148 ms | 0 |
| Sat 03 | 0 | 0.0 | 148 ms | 0 |
100% 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 3 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 Microsoft Clarity alerts to Slack, Discord or a webhook — free.
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: 100% over 3 days of checks. No public incidents logged since monitoring began 3 days ago.
Response time over the last 24 hours: 178 ms average, 72–380 ms range across 201 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Microsoft Clarity incident since monitoring began 3 days ago.
From our own checks: 100% over 3 days of checks.
178 ms on average over the last 24 hours (72–380 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.