User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is accessiBe 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 → accessibe.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 245 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 358 ms | 0 |
| Mon 21 | 0 | 0.0 | 195 ms | 0 |
| Mon 23 | 0 | 0.0 | 276 ms | 0 |
| Tue 02 | 0 | 0.0 | 200 ms | 0 |
| Tue 04 | 0 | 0.0 | 451 ms | 0 |
| Tue 06 | 0 | 0.0 | 445 ms | 0 |
| Tue 08 | 0 | 0.0 | 464 ms | 0 |
| Tue 10 | 0 | 0.0 | 470 ms | 0 |
| Tue 12 | 0 | 0.0 | 133 ms | 0 |
| Tue 14 | 0 | 0.0 | 319 ms | 0 |
| Tue 17 | 0 | 0.0 | 200 ms | 0 |
| Tue 19 | 0 | 0.0 | 438 ms | 0 |
| Tue 21 | 0 | 0.0 | 199 ms | 0 |
| Tue 23 | 0 | 0.0 | 454 ms | 0 |
| Wed 01 | 0 | 0.0 | 134 ms | 0 |
| Wed 04 | 0 | 0.0 | 406 ms | 0 |
| Wed 06 | 0 | 0.0 | 185 ms | 0 |
| Wed 08 | 0 | 0.0 | 470 ms | 0 |
| Wed 10 | 0 | 0.0 | 200 ms | 0 |
| Wed 13 | 0 | 0.0 | 415 ms | 0 |
| Wed 15 | 0 | 0.0 | 370 ms | 0 |
| Wed 17 | 0 | 0.0 | 213 ms | 0 |
| Wed 19 | 0 | 0.0 | 402 ms | 0 |
| Wed 21 | 0 | 0.0 | 431 ms | 0 |
| Wed 23 | 0 | 0.0 | 476 ms | 0 |
| Thu 01 | 0 | 0.0 | 284 ms | 0 |
| Thu 03 | 0 | 0.0 | 186 ms | 0 |
| Thu 05 | 0 | 0.0 | 467 ms | 0 |
| Thu 07 | 0 | 0.0 | 211 ms | 0 |
| Thu 09 | 0 | 0.0 | 456 ms | 0 |
| Thu 11 | 0 | 0.0 | 404 ms | 0 |
| Thu 13 | 0 | 0.0 | 397 ms | 0 |
| Thu 15 | 0 | 0.0 | 340 ms | 0 |
| Thu 17 | 0 | 0.0 | 336 ms | 0 |
| Thu 20 | 0 | 0.0 | 400 ms | 0 |
| Thu 22 | 0 | 0.0 | 462 ms | 0 |
| Fri 00 | 0 | 0.0 | 454 ms | 0 |
| Fri 02 | 0 | 0.0 | 381 ms | 0 |
| Fri 04 | 0 | 0.0 | 205 ms | 0 |
| Fri 06 | 0 | 0.0 | 494 ms | 0 |
| Fri 08 | 0 | 0.0 | 406 ms | 0 |
| Fri 10 | 0 | 0.0 | 391 ms | 0 |
| Fri 11 | 0 | 0.0 | 469 ms | 0 |
| Fri 12 | 0 | 0.0 | 137 ms | 0 |
| Fri 14 | 0 | 0.0 | 112 ms | 0 |
| Fri 16 | 0 | 0.0 | 408 ms | 0 |
| Fri 18 | 0 | 0.0 | 424 ms | 0 |
| Fri 19 | 0 | 0.0 | 245 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live accessiBe 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 accessiBe yet. Outages of 10 minutes or more get their own page here.
Having trouble with accessiBe?
One report per service every 10 minutes from this network. No account.
Follow accessiBe
Get an email when accessiBe goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send accessiBe alerts to Slack, Discord or a webhook — free.
About accessiBe
accessiBe, at accessibe.com, is one of the AI services we monitor. accessiBe combines AI, dev tools, and expert services to support ongoing web accessibility and ADA/EAA compliance in adherence to WCAG. See how it works.
accessiBe publishes an official status page at status.accessibe.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 361 ms average, 112–494 ms range across 14 successful checks.
Questions
Is accessiBe down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was accessiBe last down?
We have not recorded a public accessiBe incident since monitoring began 8 days ago.
What is accessiBe's uptime?
From our own checks: 100% over 8 days of checks.
How fast does accessiBe respond?
361 ms on average over the last 24 hours (112–494 ms).
Does accessiBe have an official status page?
Yes, at https://status.accessibe.com.
accessiBe 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 accessiBe here at once, the problem is on accessiBe'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 accessiBe. 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.