User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
wesalute.com · Cloud & developer
Is WeSalute down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with WeSalute.
What to try while WeSalute is having problems
Estimated fix: Not enough WeSalute history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → wesalute.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor 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.
Checks by region
Reachable from all 4 regions we check from.
US East · ORDReachable27 ms · 2 min ago
US West · SJCReachable26 ms · 2 min ago
Europe · AMSReachable31 ms · 2 min ago
Asia-Pacific · KIXReachable232 ms · 2 min ago
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 1 hr ago. Last stored result reached it in 80 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 60 ms | 0 |
| Tue 02 | 0 | 0.0 | 151 ms | 0 |
| Tue 04 | 0 | 0.0 | 55 ms | 0 |
| Tue 06 | 0 | 0.0 | 85 ms | 0 |
| Tue 08 | 0 | 0.0 | 16 ms | 0 |
| Tue 10 | 0 | 0.0 | 113 ms | 0 |
| Tue 12 | 0 | 0.0 | 66 ms | 0 |
| Tue 15 | 0 | 0.0 | 53 ms | 0 |
| Tue 17 | 0 | 0.0 | 72 ms | 0 |
| Tue 19 | 0 | 0.0 | 84 ms | 0 |
| Tue 21 | 0 | 0.0 | 78 ms | 0 |
| Wed 00 | 0 | 0.0 | 45 ms | 0 |
| Wed 02 | 0 | 0.0 | 83 ms | 0 |
| Wed 04 | 0 | 0.0 | 316 ms | 0 |
| Wed 06 | 0 | 0.0 | 18 ms | 0 |
| Wed 09 | 0 | 0.0 | 58 ms | 0 |
| Wed 11 | 0 | 0.0 | 21 ms | 0 |
| Wed 13 | 0 | 0.0 | 29 ms | 0 |
| Wed 15 | 0 | 0.0 | 72 ms | 0 |
| Wed 17 | 0 | 0.0 | 83 ms | 0 |
| Wed 20 | 0 | 0.0 | 96 ms | 0 |
| Wed 22 | 0 | 0.0 | 58 ms | 0 |
| Thu 00 | 0 | 0.0 | 51 ms | 0 |
| Thu 02 | 0 | 0.0 | 21 ms | 0 |
| Thu 04 | 0 | 0.0 | 46 ms | 0 |
| Thu 06 | 0 | 0.0 | 97 ms | 0 |
| Thu 08 | 0 | 0.0 | 79 ms | 0 |
| Thu 10 | 0 | 0.0 | 29 ms | 0 |
| Thu 12 | 0 | 0.0 | 104 ms | 0 |
| Thu 14 | 0 | 0.0 | 89 ms | 0 |
| Thu 17 | 0 | 0.0 | 54 ms | 0 |
| Thu 19 | 0 | 0.0 | 101 ms | 0 |
| Thu 21 | 0 | 0.0 | 32 ms | 0 |
| Thu 23 | 0 | 0.0 | 73 ms | 0 |
| Fri 01 | 0 | 0.0 | 79 ms | 0 |
| Fri 03 | 0 | 0.0 | 110 ms | 0 |
| Fri 05 | 0 | 0.0 | 58 ms | 0 |
| Fri 07 | 0 | 0.0 | 63 ms | 0 |
| Fri 08 | 0 | 0.0 | 30 ms | 0 |
| Fri 10 | 0 | 0.0 | 54 ms | 0 |
| Fri 11 | 0 | 0.0 | 90 ms | 0 |
| Fri 13 | 0 | 0.0 | 82 ms | 0 |
| Fri 15 | 0 | 0.0 | 133 ms | 0 |
| Fri 17 | 0 | 0.0 | 54 ms | 0 |
| Fri 19 | 0 | 0.0 | 29 ms | 0 |
| Fri 21 | 0 | 0.0 | 86 ms | 0 |
| Fri 22 | 0 | 0.0 | 34 ms | 0 |
| Sat 00 | 0 | 0.0 | 80 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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live WeSalute 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 WeSalute yet. Outages of 10 minutes or more get their own page here.
Having trouble with WeSalute?
One report per service every 10 minutes from this network. No account.
Follow WeSalute
Get an email when WeSalute goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WeSalute alerts to Slack, Discord or a webhook — free.
About WeSalute
WeSalute, at wesalute.com, is one of the Cloud & developer services we monitor. Military discount authentication and verification for exclusive rewards and discounts for Active Duty Military, Veterans, Retired, National Guard, Reserve, & families.
WeSalute publishes an official status page at status.wesalute.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 69 ms average, 29–133 ms range across 13 successful checks.
Questions
Is WeSalute down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was WeSalute last down?
We have not recorded a public WeSalute incident since monitoring began 9 days ago.
What is WeSalute's uptime?
From our own checks: 100% over 9 days of checks.
How fast does WeSalute respond?
69 ms on average over the last 24 hours (29–133 ms). Latest regional checks: US East 27 ms, US West 26 ms, Europe 31 ms, Asia-Pacific 232 ms.
Does WeSalute have an official status page?
Yes, at https://status.wesalute.com.
WeSalute 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report WeSalute here at once, the problem is on WeSalute'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 WeSalute. 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.