User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
weguard.ai · Cloud & developer
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 2 hr ago. Last stored result reached it in 152 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 157 ms | 0 |
| Mon 15 | 0 | 0.0 | 146 ms | 0 |
| Mon 17 | 0 | 0.0 | 159 ms | 0 |
| Mon 19 | 0 | 0.0 | 156 ms | 0 |
| Mon 22 | 0 | 0.0 | 242 ms | 0 |
| Tue 00 | 0 | 0.0 | 157 ms | 0 |
| Tue 02 | 0 | 0.0 | 177 ms | 0 |
| Tue 04 | 0 | 0.0 | 302 ms | 0 |
| Tue 06 | 0 | 0.0 | 164 ms | 0 |
| Tue 08 | 0 | 0.0 | 171 ms | 0 |
| Tue 10 | 0 | 0.0 | 194 ms | 0 |
| Tue 12 | 0 | 0.0 | 171 ms | 0 |
| Tue 15 | 0 | 0.0 | 178 ms | 0 |
| Tue 17 | 0 | 0.0 | 181 ms | 0 |
| Tue 19 | 0 | 0.0 | 176 ms | 0 |
| Tue 21 | 0 | 0.0 | 287 ms | 0 |
| Wed 00 | 0 | 0.0 | 299 ms | 0 |
| Wed 02 | 0 | 0.0 | 365 ms | 0 |
| Wed 04 | 0 | 0.0 | 223 ms | 0 |
| Wed 06 | 0 | 0.0 | 111 ms | 0 |
| Wed 09 | 0 | 0.0 | 280 ms | 0 |
| Wed 11 | 0 | 0.0 | 355 ms | 0 |
| Wed 13 | 0 | 0.0 | 307 ms | 0 |
| Wed 15 | 0 | 0.0 | 196 ms | 0 |
| Wed 17 | 0 | 0.0 | 330 ms | 0 |
| Wed 20 | 0 | 0.0 | 276 ms | 0 |
| Wed 22 | 0 | 0.0 | 157 ms | 0 |
| Thu 00 | 0 | 0.0 | 181 ms | 0 |
| Thu 02 | 0 | 0.0 | 248 ms | 0 |
| Thu 04 | 0 | 0.0 | 259 ms | 0 |
| Thu 06 | 0 | 0.0 | 176 ms | 0 |
| Thu 08 | 0 | 0.0 | 135 ms | 0 |
| Thu 10 | 0 | 0.0 | 181 ms | 0 |
| Thu 12 | 0 | 0.0 | 223 ms | 0 |
| Thu 14 | 0 | 0.0 | 152 ms | 0 |
| Thu 16 | 0 | 0.0 | 200 ms | 0 |
| Thu 18 | 0 | 0.0 | 129 ms | 0 |
| Thu 20 | 0 | 0.0 | 149 ms | 0 |
| Thu 22 | 0 | 0.0 | 275 ms | 0 |
| Fri 00 | 0 | 0.0 | 352 ms | 0 |
| Fri 02 | 0 | 0.0 | 185 ms | 0 |
| Fri 05 | 0 | 0.0 | 168 ms | 0 |
| Fri 07 | 0 | 0.0 | 116 ms | 0 |
| Fri 08 | 0 | 0.0 | 156 ms | 0 |
| Fri 10 | 0 | 0.0 | 186 ms | 0 |
| Fri 11 | 0 | 0.0 | 158 ms | 0 |
| Fri 13 | 0 | 0.0 | 275 ms | 0 |
| Fri 14 | 0 | 0.0 | 152 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 WeGuard 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 WeGuard goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WeGuard alerts to Slack, Discord or a webhook — free.
WeGuard, at weguard.ai, is one of the Cloud & developer services we monitor. WeGuard is an enterprise Unified Endpoint Management (UEM) platform to manage, secure, and monitor Android, iOS, Windows, and macOS devices from a single console. Start your free trial today.
WeGuard publishes an official status page at status.weguard.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 187 ms average, 53–352 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public WeGuard incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
187 ms on average over the last 24 hours (53–352 ms).
Yes, at https://status.weguard.ai.
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 WeGuard here at once, the problem is on WeGuard'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 WeGuard. 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.