Skip to main content

Is DocHub Down?

No — DocHub is up

Reachable from all 8 checked regions

Average response time: 1183ms

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
877ms
Avg response, 30 days

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

30-day history

30-day clean streak
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, 32 checks
Aug 24: 100.00% uptime, 32 checks
Aug 25: 100.00% uptime, 32 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 24 checks
Sep 4: 100.00% uptime, 27 checks
Sep 5: 100.00% uptime, 29 checks
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 15 checks
Sep 8: 100.00% uptime, 31 checks
Sep 9: 100.00% uptime, 38 checks
Sep 10: no data
Aug 12 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
1050ms
DNS 20ms TCP 2ms TLS 10ms TTFB 1038ms
arn
1440ms
DNS 131ms TCP 1ms TLS 7ms TTFB 1329ms
bom
2074ms
DNS 136ms TCP 1ms TLS 9ms TTFB 2062ms
ord
530ms
DNS 33ms TCP 2ms TLS 10ms TTFB 512ms
sin
2016ms
DNS 109ms TCP 1ms TLS 8ms TTFB 1766ms
sjc
765ms
DNS 12ms TCP 1ms TLS 7ms TTFB 696ms
syd
1171ms
DNS 190ms TCP 1ms TLS 7ms TTFB 1162ms
yyz
420ms
DNS 22ms TCP 1ms TLS 7ms TTFB 411ms

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 up to 18 cities across three 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 — the most recent check ran from 8 of them.
  • 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 up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required