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 111 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 326 ms | 0 |
| Mon 17 | 0 | 0.0 | 200 ms | 0 |
| Mon 19 | 0 | 0.0 | 100 ms | 0 |
| Mon 21 | 0 | 0.0 | 335 ms | 0 |
| Mon 23 | 0 | 0.0 | 190 ms | 0 |
| Tue 02 | 0 | 0.0 | 111 ms | 0 |
| Tue 04 | 0 | 0.0 | 154 ms | 0 |
| Tue 06 | 0 | 0.0 | 117 ms | 0 |
| Tue 08 | 0 | 0.0 | 127 ms | 0 |
| Tue 10 | 0 | 0.0 | 147 ms | 0 |
| Tue 12 | 0 | 0.0 | 180 ms | 0 |
| Tue 14 | 0 | 0.0 | 192 ms | 0 |
| Tue 17 | 0 | 0.0 | 300 ms | 0 |
| Tue 19 | 0 | 0.0 | 133 ms | 0 |
| Tue 21 | 0 | 0.0 | 377 ms | 0 |
| Tue 23 | 0 | 0.0 | 97 ms | 0 |
| Wed 01 | 0 | 0.0 | 110 ms | 0 |
| Wed 04 | 0 | 0.0 | 199 ms | 0 |
| Wed 06 | 0 | 0.0 | 241 ms | 0 |
| Wed 08 | 0 | 0.0 | 118 ms | 0 |
| Wed 10 | 0 | 0.0 | 121 ms | 0 |
| Wed 13 | 0 | 0.0 | 153 ms | 0 |
| Wed 15 | 0 | 0.0 | 78 ms | 0 |
| Wed 17 | 0 | 0.0 | 151 ms | 0 |
| Wed 19 | 0 | 0.0 | 279 ms | 0 |
| Wed 21 | 0 | 0.0 | 129 ms | 0 |
| Wed 23 | 0 | 0.0 | 139 ms | 0 |
| Thu 02 | 0 | 0.0 | 136 ms | 0 |
| Thu 04 | 0 | 0.0 | 97 ms | 0 |
| Thu 06 | 0 | 0.0 | 133 ms | 0 |
| Thu 08 | 0 | 0.0 | 127 ms | 0 |
| Thu 10 | 0 | 0.0 | 199 ms | 0 |
| Thu 12 | 0 | 0.0 | 296 ms | 0 |
| Thu 14 | 0 | 0.0 | 248 ms | 0 |
| Thu 16 | 0 | 0.0 | 545 ms | 0 |
| Thu 18 | 0 | 0.0 | 103 ms | 0 |
| Thu 20 | 0 | 0.0 | 137 ms | 0 |
| Thu 22 | 0 | 0.0 | 262 ms | 0 |
| Fri 00 | 0 | 0.0 | 114 ms | 0 |
| Fri 02 | 0 | 0.0 | 125 ms | 0 |
| Fri 04 | 0 | 0.0 | 110 ms | 0 |
| Fri 06 | 0 | 0.0 | 177 ms | 0 |
| Fri 09 | 0 | 0.0 | 109 ms | 0 |
| Fri 10 | 0 | 0.0 | 261 ms | 0 |
| Fri 11 | 0 | 0.0 | 80 ms | 0 |
| Fri 12 | 0 | 0.0 | 89 ms | 0 |
| Fri 14 | 0 | 0.0 | 140 ms | 0 |
| Fri 16 | 0 | 0.0 | 111 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 AgentMail 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 AgentMail goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AgentMail alerts to Slack, Discord or a webhook — free.
AgentMail is listed in our AI category and checked at agentmail.to. Give your agent an inbox of its own. AgentMail is the email infrastructure built for AI agents: send, receive and act on email at scale.
AgentMail publishes an official status page at status.agentmail.to; 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: 146 ms average, 80–338 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 AgentMail incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
146 ms on average over the last 24 hours (80–338 ms).
Yes, at https://status.agentmail.to.
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 AgentMail here at once, the problem is on AgentMail'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 AgentMail. 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.