We started checking SignWell on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when SignWell reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what SignWell's own status page declared. Below it, any public chatter we saw about SignWell and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what SignWell's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about SignWell in the last 24 hours, which is not evidence that nothing is wrong.
SignWell's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is SignWell's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention SignWell next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
197
US-West
100.00%
156
Europe
100.00%
140
Asia-Pacific
100.00%
85
Their declared record
SignWell's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Investigating — Digital signature certification delayedPartial outage
Jul 23, 2026, 4:11 PM UTC to Jul 23, 2026, 6:54 PM UTC (2h 43m)resolved
their latest update (Jul 23, 2026, 6:54 PM UTC): This incident is resolved. The upstream issue with the third-party provider has been fixed, and digital signing is operating normally. All previously delayed documents have been signed with their embedded digital certificates. Thank you for your patience.
Email Sending DelaysMinor incident
Jun 4, 2026, 10:44 PM UTC to Jun 5, 2026, 12:54 AM UTC (2h 10m)resolved
their latest update (Jun 5, 2026, 12:54 AM UTC): Resolved: This incident has been fully resolved. Our email provider has confirmed recovery on their end, the backlog of queued messages has been delivered, and email sending has returned to normal performance. We've verified delivery is stable after an extended monitoring period.…
Document Generation APIMinor incident
Mar 30, 2026, 7:41 PM UTC to Mar 30, 2026, 8:09 PM UTC (28 min)resolved
their latest update (Mar 30, 2026, 8:09 PM UTC): This incident has been resolved.
Network interruptionsPartial outage
Nov 18, 2025, 12:14 PM UTC to Nov 18, 2025, 6:33 PM UTC (6h 19m)resolved
their latest update (Nov 18, 2025, 6:33 PM UTC): Our third-party provider has resolved their network issues and our services are operating normally. We're accepting traffic and processing signatures as usual. This incident is now closed.
Service Notice: AWS Outage Affecting Integrations and SupportAll systems operational
Oct 20, 2025, 4:38 PM UTC to Oct 21, 2025, 1:01 AM UTC (8h 23m)resolved
their latest update (Oct 21, 2025, 1:01 AM UTC): AWS has given the all-clear on their status page and affected third-party services have recovered. Support tickets are being processed normally and all SignWell services remained available throughout the incident.
This incident is now closed.
Document sending encountering temporary deliverability issuesAll systems operational
Sep 16, 2025, 8:45 PM UTC to Sep 16, 2025, 9:00 PM UTC (14 min)resolved
their latest update (Sep 16, 2025, 9:00 PM UTC): Our email service provider has resolved the issue, and all queued-up emails have been delivered.
Main Website Outage Due to High LoadPartial outage
Apr 3, 2025, 8:30 AM UTC to Apr 3, 2025, 8:30 AM UTC (0 min)resolved
their latest update (Apr 3, 2025, 8:30 AM UTC): We’re currently experiencing a temporary outage on our main website due to unusually high traffic. Our team is working to resolve the issue and restore full access as quickly as possible.
In the meantime, you can still access the main app directly at:
👉 https://www.signwell.com…
Document sending to microsoft mailboxes encountering temporary deliverability issuesMinor incident
Jul 10, 2024, 6:32 PM UTC to Jul 10, 2024, 7:11 PM UTC (39 min)resolved
their latest update (Jul 10, 2024, 7:11 PM UTC): Deliverability to microsoft email accounts has been re-established. Sorry for the inconvenience!
DDoS Related DowntimeMajor outage
Jan 24, 2024, 8:00 AM UTC to Jan 24, 2024, 8:45 AM UTC (45 min)resolved
their latest update (Jan 24, 2024, 8:45 AM UTC): DDoS attack mitigated and SignWell fully operational now. We're continuing to monitor.
Services Not AvailableMajor outage
Sep 18, 2023, 9:52 PM UTC to Sep 19, 2023, 3:39 AM UTC (5h 48m)resolved
their latest update (Sep 19, 2023, 3:39 AM UTC): Site is more stable and all services operational at this point. Performance should continue to improve over the next hour.
Showing the 10 most recent of 16 incidents SignWell has declared in the history we hold.
These entries are SignWell's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
SignWell's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.