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 1 hr ago. Last stored result reached it in 220 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 216 ms | 0 |
| Tue 04 | 0 | 0.0 | 708 ms | 0 |
| Tue 07 | 0 | 0.0 | 128 ms | 0 |
| Tue 09 | 0 | 0.0 | 312 ms | 0 |
| Tue 11 | 0 | 0.0 | 215 ms | 0 |
| Tue 13 | 0 | 0.0 | 106 ms | 0 |
| Tue 15 | 0 | 0.0 | 169 ms | 0 |
| Tue 17 | 0 | 0.0 | 323 ms | 0 |
| Tue 20 | 0 | 0.0 | 329 ms | 0 |
| Tue 22 | 0 | 0.0 | 717 ms | 0 |
| Wed 00 | 0 | 0.0 | 477 ms | 0 |
| Wed 02 | 0 | 0.0 | 208 ms | 0 |
| Wed 05 | 0 | 0.0 | 266 ms | 0 |
| Wed 07 | 0 | 0.0 | 421 ms | 0 |
| Wed 09 | 0 | 0.0 | 225 ms | 0 |
| Wed 11 | 0 | 0.0 | 481 ms | 0 |
| Wed 13 | 0 | 0.0 | 1434 ms | 0 |
| Wed 15 | 0 | 0.0 | 220 ms | 0 |
| Wed 18 | 0 | 0.0 | 149 ms | 0 |
| Wed 20 | 0 | 0.0 | 178 ms | 0 |
| Wed 22 | 0 | 0.0 | 399 ms | 0 |
| Thu 00 | 0 | 0.0 | 325 ms | 0 |
| Thu 02 | 0 | 0.0 | 499 ms | 0 |
| Thu 04 | 0 | 0.0 | 210 ms | 0 |
| Thu 06 | 0 | 0.0 | 225 ms | 0 |
| Thu 08 | 0 | 0.0 | 338 ms | 0 |
| Thu 10 | 0 | 0.0 | 336 ms | 0 |
| Thu 13 | 0 | 0.0 | 346 ms | 0 |
| Thu 15 | 0 | 0.0 | 330 ms | 0 |
| Thu 17 | 0 | 0.0 | 270 ms | 0 |
| Thu 19 | 0 | 0.0 | 254 ms | 0 |
| Thu 21 | 0 | 0.0 | 230 ms | 0 |
| Thu 23 | 0 | 0.0 | 269 ms | 0 |
| Fri 01 | 0 | 0.0 | 226 ms | 0 |
| Fri 04 | 0 | 0.0 | 1032 ms | 0 |
| Fri 06 | 0 | 0.0 | 286 ms | 0 |
| Fri 08 | 0 | 0.0 | 426 ms | 0 |
| Fri 10 | 0 | 0.0 | 227 ms | 0 |
| Fri 11 | 0 | 0.0 | 208 ms | 0 |
| Fri 12 | 0 | 0.0 | 212 ms | 0 |
| Fri 14 | 0 | 0.0 | 483 ms | 0 |
| Fri 16 | 0 | 0.0 | 256 ms | 0 |
| Fri 17 | 0 | 0.0 | 954 ms | 0 |
| Fri 18 | 0 | 0.0 | 348 ms | 0 |
| Fri 19 | 0 | 0.0 | 506 ms | 0 |
| Fri 20 | 0 | 0.0 | 377 ms | 0 |
| Fri 22 | 0 | 0.0 | 304 ms | 0 |
| Fri 23 | 0 | 0.0 | 220 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.
FlexiCapture Cloud AU - Scheduled Maintenance on Nov 21, 2026 00:30 AEDT
ABBYY has scheduled a maintenance window to upgrade FlexiCapture Cloud AU Infra on Friday, Nov 20 2026. Scheduled time: Start: 00:30 AEDT on Nov 21/ 13:30 UTC on Nov 20 End: 08:30 AEDT on Nov 21 / 21:30 UTC on Nov 20 During the maintenance window, access to ABBYY FlexiCapture Cloud AU will be temporarily unavailable. Please be assured that your tenant and all associated data will remain fully…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for ABBYY 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 ABBYY goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ABBYY alerts to Slack, Discord or a webhook — free.
ABBYY, at abbyy.com, is one of the AI services we monitor. ABBYY helps enterprises gain a complete understanding of their business processes to accelerate digital transformation with a platform enabled with AI, NLP and OCR.
ABBYY publishes an official status page at status.abbyy.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 404 ms average, 208–1032 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 ABBYY incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
404 ms on average over the last 24 hours (208–1032 ms).
Yes, at https://status.abbyy.com.
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 ABBYY here at once, the problem is on ABBYY'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 ABBYY. 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.