User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Welocalize down?
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.
What to try while Welocalize is having problems
Estimated fix: Not enough Welocalize history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → welocalize.com—
Your browser → us—
Our checksReaching it
Official · ReportsMajor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 47 min ago. Last stored result reached it in 131 ms.
Official status
Major incident
Microsoft outage email Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 85 ms | 0 |
| Tue 00 | 0 | 0.0 | 91 ms | 0 |
| Tue 03 | 0 | 0.0 | 61 ms | 0 |
| Tue 05 | 0 | 0.0 | 129 ms | 0 |
| Tue 07 | 0 | 0.0 | 58 ms | 0 |
| Tue 09 | 0 | 0.0 | 67 ms | 0 |
| Tue 11 | 0 | 0.0 | 117 ms | 0 |
| Tue 13 | 0 | 0.0 | 82 ms | 0 |
| Tue 15 | 0 | 0.0 | 173 ms | 0 |
| Tue 18 | 0 | 0.0 | 87 ms | 0 |
| Tue 20 | 0 | 0.0 | 44 ms | 0 |
| Tue 22 | 0 | 0.0 | 151 ms | 0 |
| Wed 00 | 0 | 0.0 | 79 ms | 0 |
| Wed 03 | 0 | 0.0 | 145 ms | 0 |
| Wed 05 | 0 | 0.0 | 112 ms | 0 |
| Wed 07 | 0 | 0.0 | 179 ms | 0 |
| Wed 09 | 0 | 0.0 | 113 ms | 0 |
| Wed 12 | 0 | 0.0 | 87 ms | 0 |
| Wed 14 | 0 | 0.0 | 86 ms | 0 |
| Wed 16 | 0 | 0.0 | 73 ms | 0 |
| Wed 18 | 0 | 0.0 | 47 ms | 0 |
| Wed 21 | 0 | 0.0 | 150 ms | 0 |
| Wed 23 | 0 | 0.0 | 115 ms | 0 |
| Thu 01 | 0 | 0.0 | 392 ms | 0 |
| Thu 03 | 0 | 0.0 | 146 ms | 0 |
| Thu 05 | 0 | 0.0 | 60 ms | 0 |
| Thu 07 | 0 | 0.0 | 116 ms | 0 |
| Thu 09 | 0 | 0.0 | 139 ms | 0 |
| Thu 11 | 0 | 0.0 | 95 ms | 0 |
| Thu 13 | 0 | 0.0 | 171 ms | 0 |
| Thu 16 | 0 | 0.0 | 186 ms | 0 |
| Thu 18 | 0 | 0.0 | 91 ms | 0 |
| Thu 20 | 0 | 0.0 | 122 ms | 0 |
| Thu 22 | 0 | 0.0 | 48 ms | 0 |
| Fri 00 | 0 | 0.0 | 142 ms | 0 |
| Fri 02 | 0 | 0.0 | 107 ms | 0 |
| Fri 03 | 0 | 0.0 | 111 ms | 0 |
| Fri 05 | 0 | 0.0 | 102 ms | 0 |
| Fri 06 | 0 | 0.0 | 58 ms | 0 |
| Fri 08 | 0 | 0.0 | 51 ms | 0 |
| Fri 10 | 0 | 0.0 | 108 ms | 0 |
| Fri 12 | 0 | 0.0 | 59 ms | 0 |
| Fri 14 | 0 | 0.0 | 44 ms | 0 |
| Fri 16 | 0 | 0.0 | 197 ms | 0 |
| Fri 18 | 0 | 0.0 | 111 ms | 0 |
| Fri 19 | 0 | 0.0 | 124 ms | 0 |
| Fri 21 | 0 | 0.0 | 55 ms | 0 |
| Fri 23 | 0 | 0.0 | 97 ms | 0 |
Reliability
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.
Embed this status: free live Welocalize badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Welocalize yet. Outages of 10 minutes or more get their own page here.
Having trouble with Welocalize?
One report per service every 10 minutes from this network. No account.
Follow Welocalize
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.
About Welocalize
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: 95 ms average, 38–197 ms range across 17 successful checks.
Questions
Is Welocalize down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft outage email
When was Welocalize last down?
We have not recorded a public Welocalize incident since monitoring began 7 days ago.
What is Welocalize's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Welocalize respond?
95 ms on average over the last 24 hours (38–197 ms).
Does Welocalize have an official status page?
Yes, at https://status.welocalize.com.
Welocalize not working for me but the status is fine. What now?
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.