User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Transkribus 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 → transkribus.org—
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 2 hr ago. Last stored result reached it in 499 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 |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 411 ms | 0 |
| Tue 02 | 0 | 0.0 | 484 ms | 0 |
| Tue 04 | 0 | 0.0 | 451 ms | 0 |
| Tue 06 | 0 | 0.0 | 502 ms | 0 |
| Tue 08 | 0 | 0.0 | 516 ms | 0 |
| Tue 10 | 0 | 0.0 | 580 ms | 0 |
| Tue 12 | 0 | 0.0 | 459 ms | 0 |
| Tue 14 | 0 | 0.0 | 264 ms | 0 |
| Tue 17 | 0 | 0.0 | 531 ms | 0 |
| Tue 19 | 0 | 0.0 | 503 ms | 0 |
| Tue 21 | 0 | 0.0 | 285 ms | 0 |
| Wed 00 | 0 | 0.0 | 558 ms | 0 |
| Wed 02 | 0 | 0.0 | 260 ms | 0 |
| Wed 04 | 0 | 0.0 | 406 ms | 0 |
| Wed 06 | 0 | 0.0 | 430 ms | 0 |
| Wed 08 | 0 | 0.0 | 423 ms | 0 |
| Wed 11 | 0 | 0.0 | 474 ms | 0 |
| Wed 13 | 0 | 0.0 | 185 ms | 0 |
| Wed 15 | 0 | 0.0 | 570 ms | 0 |
| Wed 17 | 0 | 0.0 | 567 ms | 0 |
| Wed 19 | 0 | 0.0 | 321 ms | 0 |
| Wed 22 | 0 | 0.0 | 261 ms | 0 |
| Thu 00 | 0 | 0.0 | 431 ms | 0 |
| Thu 03 | 0 | 0.0 | 462 ms | 0 |
| Thu 04 | 0 | 0.0 | 452 ms | 0 |
| Thu 06 | 0 | 0.0 | 473 ms | 0 |
| Thu 08 | 0 | 0.0 | 559 ms | 0 |
| Thu 10 | 0 | 0.0 | 430 ms | 0 |
| Thu 13 | 0 | 0.0 | 470 ms | 0 |
| Thu 15 | 0 | 0.0 | 439 ms | 0 |
| Thu 17 | 0 | 0.0 | 383 ms | 0 |
| Thu 19 | 0 | 0.0 | 486 ms | 0 |
| Thu 21 | 0 | 0.0 | 433 ms | 0 |
| Thu 23 | 0 | 0.0 | 439 ms | 0 |
| Fri 01 | 0 | 0.0 | 545 ms | 0 |
| Fri 03 | 0 | 0.0 | 524 ms | 0 |
| Fri 05 | 0 | 0.0 | 378 ms | 0 |
| Fri 07 | 0 | 0.0 | 421 ms | 0 |
| Fri 08 | 0 | 0.0 | 472 ms | 0 |
| Fri 09 | 0 | 0.0 | 467 ms | 0 |
| Fri 10 | 0 | 0.0 | 404 ms | 0 |
| Fri 12 | 0 | 0.0 | 409 ms | 0 |
| Fri 14 | 0 | 0.0 | 490 ms | 0 |
| Fri 16 | 0 | 0.0 | 557 ms | 0 |
| Fri 18 | 0 | 0.0 | 438 ms | 0 |
| Fri 20 | 0 | 0.0 | 481 ms | 0 |
| Fri 21 | 0 | 0.0 | 466 ms | 0 |
| Fri 23 | 0 | 0.0 | 499 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 Transkribus 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 Transkribus yet. Outages of 10 minutes or more get their own page here.
Having trouble with Transkribus?
One report per service every 10 minutes from this network. No account.
Follow Transkribus
Get an email when Transkribus goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Transkribus alerts to Slack, Discord or a webhook — free.
About Transkribus
We track Transkribus (transkribus.org) as part of the AI group. The leading AI platform that turns handwritten documents into searchable, interactive knowledge. Trusted by archives, built for everyone.
Transkribus publishes an official status page at status.transkribus.org; 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: 470 ms average, 378–560 ms range across 17 successful checks.
Questions
Is Transkribus down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Transkribus last down?
We have not recorded a public Transkribus incident since monitoring began 8 days ago.
What is Transkribus's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Transkribus respond?
470 ms on average over the last 24 hours (378–560 ms).
Does Transkribus have an official status page?
Yes, at https://status.transkribus.org.
Transkribus 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 Transkribus here at once, the problem is on Transkribus'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 Transkribus. 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.