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 36 min ago. Last stored result reached it in 232 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 128 ms | 0 |
| Tue 04 | 0 | 0.0 | 97 ms | 0 |
| Tue 06 | 0 | 0.0 | 114 ms | 0 |
| Tue 08 | 0 | 0.0 | 57 ms | 0 |
| Tue 10 | 0 | 0.0 | 155 ms | 0 |
| Tue 12 | 0 | 0.0 | 70 ms | 0 |
| Tue 15 | 0 | 0.0 | 79 ms | 0 |
| Tue 17 | 0 | 0.0 | 60 ms | 0 |
| Tue 19 | 0 | 0.0 | 79 ms | 0 |
| Tue 21 | 0 | 0.0 | 232 ms | 0 |
| Wed 00 | 0 | 0.0 | 81 ms | 0 |
| Wed 02 | 0 | 0.0 | 83 ms | 0 |
| Wed 04 | 0 | 0.0 | 87 ms | 0 |
| Wed 06 | 0 | 0.0 | 47 ms | 0 |
| Wed 09 | 0 | 0.0 | 34 ms | 0 |
| Wed 11 | 0 | 0.0 | 101 ms | 0 |
| Wed 13 | 0 | 0.0 | 30 ms | 0 |
| Wed 15 | 0 | 0.0 | 337 ms | 0 |
| Wed 17 | 0 | 0.0 | 394 ms | 0 |
| Wed 19 | 0 | 0.0 | 457 ms | 0 |
| Wed 22 | 0 | 0.0 | 441 ms | 0 |
| Thu 00 | 0 | 0.0 | 251 ms | 0 |
| Thu 02 | 0 | 0.0 | 368 ms | 0 |
| Thu 04 | 0 | 0.0 | 255 ms | 0 |
| Thu 06 | 0 | 0.0 | 280 ms | 0 |
| Thu 08 | 0 | 0.0 | 282 ms | 0 |
| Thu 10 | 0 | 0.0 | 265 ms | 0 |
| Thu 12 | 0 | 0.0 | 209 ms | 0 |
| Thu 14 | 0 | 0.0 | 254 ms | 0 |
| Thu 16 | 0 | 0.0 | 410 ms | 0 |
| Thu 18 | 0 | 0.0 | 317 ms | 0 |
| Thu 20 | 0 | 0.0 | 305 ms | 0 |
| Thu 22 | 0 | 0.0 | 233 ms | 0 |
| Fri 00 | 0 | 0.0 | 195 ms | 0 |
| Fri 02 | 0 | 0.0 | 324 ms | 0 |
| Fri 05 | 0 | 0.0 | 224 ms | 0 |
| Fri 07 | 0 | 0.0 | 199 ms | 0 |
| Fri 09 | 0 | 0.0 | 236 ms | 0 |
| Fri 10 | 0 | 0.0 | 231 ms | 0 |
| Fri 11 | 0 | 0.0 | 224 ms | 0 |
| Fri 14 | 0 | 0.0 | 377 ms | 0 |
| Fri 15 | 0 | 0.0 | 192 ms | 0 |
| Fri 17 | 0 | 0.0 | 262 ms | 0 |
| Fri 19 | 0 | 0.0 | 368 ms | 0 |
| Fri 21 | 0 | 0.0 | 244 ms | 0 |
| Fri 23 | 0 | 0.0 | 266 ms | 0 |
| Sat 01 | 0 | 0.0 | 212 ms | 0 |
| Sat 03 | 0 | 0.0 | 232 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 Emissary 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 Emissary goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Emissary alerts to Slack, Discord or a webhook — free.
We track Emissary (emissary.ai) as part of the AI group. Text recruiting software and recruiting automation tools. Integrate SMS, AI recruiting software and recruiting chatbots into any ATS platform.
Emissary publishes an official status page at status.emissary.ai; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 249 ms average, 192–377 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 Emissary incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
249 ms on average over the last 24 hours (192–377 ms).
Yes, at https://status.emissary.ai.
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 Emissary here at once, the problem is on Emissary'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 Emissary. 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.