User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft outage email
Source: the vendor's status page · We are not affiliated with Welocalize.
Estimated fix: Not enough Welocalize history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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.
Reachable from all 4 regions we check from.
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 hr ago. Last stored result reached it in 51 ms.
Major incident
Microsoft outage email Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:45 | 0 | 0.0 | 139 ms | 0 |
| 11:45 | 0 | 0.0 | 95 ms | 0 |
| 13:45 | 0 | 0.0 | 171 ms | 0 |
| 16:00 | 0 | 0.0 | 186 ms | 0 |
| 18:00 | 0 | 0.0 | 91 ms | 0 |
| 20:00 | 0 | 0.0 | 122 ms | 0 |
| 22:00 | 0 | 0.0 | 48 ms | 0 |
| 00:15 | 0 | 0.0 | 142 ms | 0 |
| 02:15 | 0 | 0.0 | 107 ms | 0 |
| 03:30 | 0 | 0.0 | 111 ms | 0 |
| 05:45 | 0 | 0.0 | 102 ms | 0 |
| 06:00 | 0 | 0.0 | 58 ms | 0 |
| 08:00 | 0 | 0.0 | 51 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Welocalize 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 Welocalize goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Welocalize alerts to Slack, Discord or a webhook — free.
We track Welocalize (welocalize.com) as part of the AI group. Bridging language & AI to power global success. Our expertise in localization & AI data ensures scalable solutions for businesses worldwide.
Welocalize publishes an official status page at status.welocalize.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 108 ms average, 48–186 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft outage email
We have not recorded a public Welocalize incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
108 ms on average over the last 24 hours (48–186 ms). Latest regional checks: US East 80 ms, US West 115 ms, Europe 64 ms, Asia-Pacific 188 ms.
Yes, at https://status.welocalize.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Welocalize here at once, the problem is on Welocalize'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 Welocalize. 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.