User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Utilities
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 30 min ago. Last stored result reached it in 152 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 01 | 0 | 0.0 | 141 ms | 0 |
| Wed 03 | 0 | 0.0 | 179 ms | 0 |
| Wed 06 | 0 | 0.0 | 178 ms | 0 |
| Wed 08 | 0 | 0.0 | 624 ms | 0 |
| Wed 10 | 0 | 0.0 | 230 ms | 0 |
| Wed 12 | 0 | 0.0 | 107 ms | 0 |
| Wed 14 | 0 | 0.0 | 246 ms | 0 |
| Wed 16 | 0 | 0.0 | 253 ms | 0 |
| Wed 19 | 0 | 0.0 | 115 ms | 0 |
| Wed 21 | 0 | 0.0 | 161 ms | 0 |
| Wed 23 | 0 | 0.0 | 235 ms | 0 |
| Thu 01 | 0 | 0.0 | 312 ms | 0 |
| Thu 03 | 0 | 0.0 | 152 ms | 0 |
| Thu 05 | 0 | 0.0 | 132 ms | 0 |
| Thu 07 | 0 | 0.0 | 246 ms | 0 |
| Thu 09 | 0 | 0.0 | 91 ms | 0 |
| Thu 11 | 0 | 0.0 | 194 ms | 0 |
| Thu 14 | 0 | 0.0 | 180 ms | 0 |
| Thu 16 | 0 | 0.0 | 178 ms | 0 |
| Thu 18 | 0 | 0.0 | 110 ms | 0 |
| Thu 20 | 0 | 0.0 | 222 ms | 0 |
| Thu 22 | 0 | 0.0 | 150 ms | 0 |
| Fri 00 | 0 | 0.0 | 219 ms | 0 |
| Fri 02 | 0 | 0.0 | 68 ms | 0 |
| Fri 04 | 0 | 0.0 | 298 ms | 0 |
| Fri 06 | 0 | 0.0 | 295 ms | 0 |
| Fri 08 | 0 | 0.0 | 383 ms | 0 |
| Fri 10 | 0 | 0.0 | 130 ms | 0 |
| Fri 11 | 0 | 0.0 | 216 ms | 0 |
| Fri 13 | 0 | 0.0 | 606 ms | 0 |
| Fri 15 | 0 | 0.0 | 301 ms | 0 |
| Fri 17 | 0 | 0.0 | 128 ms | 0 |
| Fri 19 | 0 | 0.0 | 112 ms | 0 |
| Fri 21 | 0 | 0.0 | 84 ms | 0 |
| Fri 23 | 0 | 0.0 | 169 ms | 0 |
| Sat 01 | 0 | 0.0 | 151 ms | 0 |
| Sat 03 | 0 | 0.0 | 172 ms | 0 |
| Sat 05 | 0 | 0.0 | 129 ms | 0 |
| Sat 07 | 0 | 0.0 | 190 ms | 0 |
| Sat 09 | 0 | 0.0 | 147 ms | 0 |
| Sat 11 | 0 | 0.0 | 305 ms | 0 |
| Sat 14 | 0 | 0.0 | 194 ms | 0 |
| Sat 16 | 0 | 0.0 | 101 ms | 0 |
| Sat 18 | 0 | 0.0 | 112 ms | 0 |
| Sat 21 | 0 | 0.0 | 220 ms | 0 |
| Sat 23 | 0 | 0.0 | 100 ms | 0 |
| Sun 01 | 0 | 0.0 | 236 ms | 0 |
| Sun 03 | 0 | 0.0 | 166 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 10 days of data so far, so the 90-day numbers fill in over time.
Vaisala Xweather Data API Update
API Release 1.45.1 - renewables/irradiance/archive - adding filter multipliers for api call consumption - renewables/irradiance/summary - Adding temporal cost headers for each calendar month queried - renewables/irradiance/monitoring - Adding 1 & 5 minute time step filters - convective/outlook - Adding language translation for the risk name - models - Adding 100m wind speed & GHI variables to…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Vaisala Xweather 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 Vaisala Xweather 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.
We track Vaisala Xweather (xweather.com) as part of the Utilities group. Weather API, lightning data, forecasts, and climate intelligence for developers and enterprises. Weather intelligence for energy, finance, insurance, and operations.
Vaisala Xweather publishes an official status page at status.xweather.com; when we can read it, its incident level is folded into the status shown here.
Common problems for utilities services: outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 163 ms average, 94–305 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Vaisala Xweather incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
163 ms on average over the last 24 hours (94–305 ms).
Yes, at https://status.xweather.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For utilities services, watch for outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems. If many people report Vaisala Xweather here at once, the problem is on Vaisala Xweather'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 Vaisala Xweather. 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.