All-in-One: Native E-signature Experiencing Errors

What to do

• Check whether you use Ashby Recruiting, Dropbox Sign. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 5h 5m it lasted.

  Anything that failed between 2026-02-13 05:10 UTC and 2026-02-13 10:15 UTC may need a replay.

• Subscribe to Ashby's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=ashby works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ashby 4

1. investigatingFeb 13, 2026, 5:10 AM UTC

   There is an issue with an upstream provider. E-Signature requests may result in errors.

   provider

2. identifiedFeb 13, 2026, 6:26 AM UTC

   Native e-signatures are non-functional in Ashby due to an issue with an upstream provider. Ashby may display a success message, but the upstream provider will not be able to complete the e-signature process. We are working with the upstream provider to restore service. Until service is restored, customers will need to use our DocuSign integration or an e-signature service outside of Ashby. We will provide an update once we get more info from the upstream provider.

   provider

3. monitoringFeb 13, 2026, 9:22 AM UTC

   We're seeing signs of recovery with the upstream provider and are actively monitoring.

   provider

4. resolvedFeb 13, 2026, 10:15 AM UTC

   The issue has been resolved by the upstream provider.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.