User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Echobox down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → echobox.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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.
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 1121 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 1210 ms | 0 |
| Mon 19 | 0 | 0.0 | 1260 ms | 0 |
| Mon 21 | 0 | 0.0 | 1292 ms | 0 |
| Mon 23 | 0 | 0.0 | 1214 ms | 0 |
| Tue 01 | 0 | 0.0 | 1133 ms | 0 |
| Tue 03 | 0 | 0.0 | 1140 ms | 0 |
| Tue 05 | 0 | 0.0 | 1185 ms | 0 |
| Tue 07 | 0 | 0.0 | 973 ms | 0 |
| Tue 10 | 0 | 0.0 | 1197 ms | 0 |
| Tue 12 | 0 | 0.0 | 1018 ms | 0 |
| Tue 14 | 0 | 0.0 | 1184 ms | 0 |
| Tue 16 | 0 | 0.0 | 1305 ms | 0 |
| Tue 18 | 0 | 0.0 | 1141 ms | 0 |
| Tue 21 | 0 | 0.0 | 1567 ms | 0 |
| Tue 23 | 0 | 0.0 | 1012 ms | 0 |
| Wed 01 | 0 | 0.0 | 1208 ms | 0 |
| Wed 03 | 0 | 0.0 | 1253 ms | 0 |
| Wed 06 | 0 | 0.0 | 1181 ms | 0 |
| Wed 08 | 0 | 0.0 | 1007 ms | 0 |
| Wed 10 | 0 | 0.0 | 1067 ms | 0 |
| Wed 12 | 0 | 0.0 | 1074 ms | 0 |
| Wed 13 | 0 | 0.0 | 1075 ms | 0 |
| Wed 15 | 0 | 0.0 | 937 ms | 0 |
| Wed 17 | 0 | 0.0 | 1374 ms | 0 |
| Wed 19 | 0 | 0.0 | 1147 ms | 0 |
| Wed 21 | 0 | 0.0 | 1141 ms | 0 |
| Thu 00 | 0 | 0.0 | 1129 ms | 0 |
| Thu 02 | 0 | 0.0 | 1165 ms | 0 |
| Thu 04 | 0 | 0.0 | 1236 ms | 0 |
| Thu 06 | 0 | 0.0 | 1127 ms | 0 |
| Thu 08 | 0 | 0.0 | 1197 ms | 0 |
| Thu 10 | 0 | 0.0 | 783 ms | 0 |
| Thu 12 | 0 | 0.0 | 1085 ms | 0 |
| Thu 14 | 0 | 0.0 | 1142 ms | 0 |
| Thu 16 | 0 | 0.0 | 1237 ms | 0 |
| Thu 18 | 0 | 0.0 | 1311 ms | 0 |
| Thu 20 | 0 | 0.0 | 1229 ms | 0 |
| Thu 22 | 0 | 0.0 | 1166 ms | 0 |
| Fri 00 | 0 | 0.0 | 1185 ms | 0 |
| Fri 03 | 0 | 0.0 | 1185 ms | 0 |
| Fri 04 | 0 | 0.0 | 1279 ms | 0 |
| Fri 07 | 0 | 0.0 | 1127 ms | 0 |
| Fri 09 | 0 | 0.0 | 1057 ms | 0 |
| Fri 10 | 0 | 0.0 | 1061 ms | 0 |
| Fri 11 | 0 | 0.0 | 1135 ms | 0 |
| Fri 13 | 0 | 0.0 | 1079 ms | 0 |
| Fri 15 | 0 | 0.0 | 1263 ms | 0 |
| Fri 17 | 0 | 0.0 | 1231 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Echobox 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 Echobox yet. Outages of 10 minutes or more get their own page here.
Having trouble with Echobox?
One report per service every 10 minutes from this network. No account.
Follow Echobox
Get an email when Echobox goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Echobox alerts to Slack, Discord or a webhook — free.
About Echobox
We track Echobox (echobox.com) as part of the AI group. Unify social publishing, newsletters, realtime analytics, benchmarking, reporting and creative production in one AI-powered platform built for publishers.
Echobox publishes an official status page at status.echobox.com; 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: 1169 ms average, 1055–1341 ms range across 15 successful checks.
Questions
Is Echobox down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Echobox last down?
We have not recorded a public Echobox incident since monitoring began 7 days ago.
What is Echobox's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Echobox respond?
1169 ms on average over the last 24 hours (1055–1341 ms).
Does Echobox have an official status page?
Yes, at https://status.echobox.com.
Echobox 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Echobox here at once, the problem is on Echobox'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 Echobox. 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.