Skip to main content

Is DocHub Down?

No — DocHub is up

Reachable from all 8 checked regions

Average response time: 1065ms

Last checked · checks run every 6 hours

Official status page: https://status.dochub.com

DocHub uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
661ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: 100.00% uptime, 24 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 31 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
1166ms
DNS 15ms TCP 2ms TLS 10ms TTFB 1079ms
arn
1231ms
DNS 54ms TCP 1ms TLS 28ms TTFB 1204ms
bom
2036ms
DNS 191ms TCP 3ms TLS 11ms TTFB 2020ms
cdg
1007ms
DNS 25ms TCP 2ms TLS 8ms TTFB 997ms
dfw
497ms
DNS 46ms TCP 1ms TLS 9ms TTFB 487ms
ewr
403ms
DNS 40ms TCP 2ms TLS 8ms TTFB 389ms
sjc
503ms
DNS 32ms TCP 4ms TLS 11ms TTFB 488ms
syd
1776ms
DNS 124ms TCP 1ms TLS 9ms TTFB 1769ms
yyz
408ms
DNS 22ms TCP 1ms TLS 9ms TTFB 398ms

What DocHub does

DocHub is a browser-based PDF editor and signing service. Users annotate and fill documents, request signatures, and build reusable templates and fillable forms. It is used heavily inside Google Workspace, opening files directly from Gmail, Google Drive and Dropbox, which is why it shows up in school and small-office workflows where no separate document system exists.

What an outage looks like

Documents fail to open or save, the editor loads without the file, and sign requests are not delivered to recipients. Because DocHub reads files from Google Drive, a Drive or Google API fault produces the same symptom as a DocHub one: the document will not load. DocHub's status page tracks those upstream dependencies alongside its own site for exactly that reason.

What to do about it

Read status.dochub.com, which is unusually useful because it lists DocHub's dependencies as well as DocHub: Google Drive, Classroom and Gmail APIs, AWS, Cloudflare, Stripe and Twilio each have their own line. If dochub.com is operational but a Google API is not, the fix is to wait rather than to re-upload. Avoid re-sending a signature request until delivery is confirmed working.

Is it down for everyone, or just you?

If this page says DocHub is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

DocHub outage FAQ

Is DocHub down, or is it Google Drive?
The status page answers this directly, which is rare. DocHub lists Google Drive, Google Classroom and Gmail API components next to its own, so you can see whether the failure is DocHub's or an upstream dependency's. If a Google line is red and dochub.com is green, no amount of retrying inside DocHub will help until Google recovers.
Will I lose my edits if DocHub goes down while I am working?
Edits that have been saved back to the document are held by DocHub and are not lost by an outage. Unsaved changes in an open editor tab are the risk, as with any browser-based editor. If the page is still open, avoid refreshing it: the tab holds the only copy of anything not yet written, and a reload during an incident discards it.
Do sign requests still get delivered during an outage?
Not reliably. Delivery depends on the components DocHub lists separately, including the Gmail API and Twilio for text messaging, so a signature request can fail to reach the recipient while DocHub itself works. Check those lines before re-sending, because duplicate sign requests confuse the recipient and can produce two signed copies of the same document.
Can I still open DocHub files from Google Drive when DocHub is down?
The files themselves live in your Drive and remain accessible there, but they will open as plain PDFs without DocHub's editing and signing layer. That is enough to read or forward a document during an incident. Anything that needs annotation, form filling or a signature has to wait for the DocHub line on the status page to clear.

How we measure this

  • We request DocHub's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where DocHub publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when DocHub goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required