User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 40 min ago. Last stored result reached it in 359 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 264 ms | 0 |
| Mon 17 | 0 | 0.0 | 259 ms | 0 |
| Mon 19 | 0 | 0.0 | 407 ms | 0 |
| Mon 22 | 0 | 0.0 | 90 ms | 0 |
| Tue 00 | 0 | 0.0 | 186 ms | 0 |
| Tue 02 | 0 | 0.0 | 225 ms | 0 |
| Tue 04 | 0 | 0.0 | 372 ms | 0 |
| Tue 06 | 0 | 0.0 | 78 ms | 0 |
| Tue 08 | 0 | 0.0 | 317 ms | 0 |
| Tue 10 | 0 | 0.0 | 354 ms | 0 |
| Tue 12 | 0 | 0.0 | 281 ms | 0 |
| Tue 15 | 0 | 0.0 | 208 ms | 0 |
| Tue 17 | 0 | 0.0 | 267 ms | 0 |
| Tue 19 | 0 | 0.0 | 119 ms | 0 |
| Tue 21 | 0 | 0.0 | 359 ms | 0 |
| Wed 00 | 0 | 0.0 | 114 ms | 0 |
| Wed 02 | 0 | 0.0 | 278 ms | 0 |
| Wed 04 | 0 | 0.0 | 105 ms | 0 |
| Wed 06 | 0 | 0.0 | 75 ms | 0 |
| Wed 09 | 0 | 0.0 | 527 ms | 0 |
| Wed 11 | 0 | 0.0 | 308 ms | 0 |
| Wed 13 | 0 | 0.0 | 96 ms | 0 |
| Wed 15 | 0 | 0.0 | 473 ms | 0 |
| Wed 17 | 0 | 0.0 | 96 ms | 0 |
| Wed 19 | 0 | 0.0 | 168 ms | 0 |
| Wed 22 | 0 | 0.0 | 137 ms | 0 |
| Thu 00 | 0 | 0.0 | 272 ms | 0 |
| Thu 02 | 0 | 0.0 | 251 ms | 0 |
| Thu 04 | 0 | 0.0 | 197 ms | 0 |
| Thu 06 | 0 | 0.0 | 115 ms | 0 |
| Thu 08 | 0 | 0.0 | 123 ms | 0 |
| Thu 10 | 0 | 0.0 | 94 ms | 0 |
| Thu 12 | 0 | 0.0 | 127 ms | 0 |
| Thu 14 | 0 | 0.0 | 99 ms | 0 |
| Thu 16 | 0 | 0.0 | 373 ms | 0 |
| Thu 18 | 0 | 0.0 | 161 ms | 0 |
| Thu 20 | 0 | 0.0 | 406 ms | 0 |
| Thu 23 | 0 | 0.0 | 85 ms | 0 |
| Fri 01 | 0 | 0.0 | 163 ms | 0 |
| Fri 03 | 0 | 0.0 | 351 ms | 0 |
| Fri 05 | 0 | 0.0 | 174 ms | 0 |
| Fri 07 | 0 | 0.0 | 237 ms | 0 |
| Fri 09 | 0 | 0.0 | 91 ms | 0 |
| Fri 10 | 0 | 0.0 | 348 ms | 0 |
| Fri 12 | 0 | 0.0 | 98 ms | 0 |
| Fri 14 | 0 | 0.0 | 237 ms | 0 |
| Fri 16 | 0 | 0.0 | 276 ms | 0 |
| Fri 18 | 0 | 0.0 | 359 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Mend 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 Mend goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mend alerts to Slack, Discord or a webhook — free.
We track Mend (mend.io) as part of the AI group. Traditional application security misses AI risk. Standalone AI security tools miss your code. Mend.io closes the gap with unified security for AppSec and AI.
Mend publishes an official status page at status.mend.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 226 ms average, 85–406 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 Mend incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
226 ms on average over the last 24 hours (85–406 ms).
Yes, at https://status.mend.io.
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 Mend here at once, the problem is on Mend'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 Mend. 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.