Zefort Outage History
Zefort is up right nowPingoru has recorded 12 incidents for Zefort: 2 in the last 12 months and 2 in the last 90 days.
Incidents, newest first
Minor October 1, 2026 Possible delays in document processing 6h 26m Document AI
Started Oct 01, 2026, 08:45 AM UTC· resolved Oct 01, 2026, 03:12 PM UTC
- identified Oct 01, 2026, 10:02 AM UTC
Due to an ongoing outage at our cloud services provider, some accounts may experience delays in document processing. While the provider is actively working to resolve the issue, we are moving affected accounts to alternative systems.
- identified Oct 01, 2026, 10:56 AM UTC
Changes are being deployed to bring alternative resources and processing paths into use. Newly submitted documents should start processing normally shortly.
- monitoring Oct 01, 2026, 12:26 PM UTC
Additional capacity has been deployed, and new documents are now processing normally. Documents that may have remained queued during the outage are being processed.
- resolved Oct 01, 2026, 04:01 PM UTC
All remaining queued documents have now been processed. We apologize for the disruption and any inconvenience caused.
Major September 7, 2026 Delays in completing electronic signatures 1h 7m Zefort Sign
Started Sep 07, 2026, 04:39 AM UTC· resolved Sep 07, 2026, 05:46 AM UTC
- identified Sep 07, 2026, 04:39 AM UTC
An ongoing issue with our signing provider is delaying the creation of final signed documents. Signers can still authenticate, review documents, and submit signatures normally. Some signing requests may remain in processing after all parties have signed. Affected final documents will be created once the provider issue is resolved. No action is required from signing request owners.
- resolved Sep 07, 2026, 05:46 AM UTC
The issue with our signing provider has been resolved. Affected final signed documents are now being created automatically. We apologize for the inconvenience.
Minor April 15, 2025 my.zefort.com unresponsive 14m my.zefort.com
Started Apr 15, 2025, 10:04 AM UTC· resolved Apr 15, 2025, 10:18 AM UTC
- identified Apr 15, 2025, 10:12 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 15, 2025, 10:16 AM UTC
The application is back to working normally. We are monitoring the situation.
- resolved Apr 15, 2025, 10:18 AM UTC
This incident has been resolved.
Major February 5, 2025 Users may not able to access binders and contracts shared to them 5h 23m my.zefort.com
Started Feb 05, 2025, 07:21 AM UTC· resolved Feb 05, 2025, 12:45 PM UTC
- investigating Feb 05, 2025, 07:21 AM UTC
We are currently investigating an issue with binder visibility. Users may not have access to all binders and contracts that they have been given permission to.
- investigating Feb 05, 2025, 07:22 AM UTC
We are continuing to investigate this issue.
- investigating Feb 05, 2025, 07:42 AM UTC
We have identified the issue and are working on a fix to restore user access to binders and contracts.
- investigating Feb 05, 2025, 09:10 AM UTC
A fix is being deployed and users should start seeing their access to binders and contracts restored.
- monitoring Feb 05, 2025, 10:35 AM UTC
Access to all users has been restored. We are still monitoring the situation closely.
- resolved Feb 05, 2025, 12:45 PM UTC
This incident has been resolved.
- postmortem Feb 13, 2025, 09:04 AM UTC
## Summary We encountered an issue where duplicate or overlapping permission entries in our database were causing complexity and performance concerns. To improve efficiency, we performed a cleanup to remove these duplicates. However, due to a logic error in the update process, some valid permission entries were mistakenly removed. Despite our testing, we did not catch this issue before deployment. **Impact:** As a result, many users temporarily lost access to some content they should have had access to. No data was lost, only the ability to view or manage certain content was affected. ## Resolution Once the issue was identified, we restored affected permissions from backups. Our team conducted a thorough review, including going through logs, to ensure all permissions were correctly reinstated. We also took steps to ensure that contracts received via email during the incident, which may have been affected by missing permissions, were properly ingested. ## Next Steps To prevent similar incidents in the future, we are: * Enhancing automated tests to better detect unintended data modifications. * Improving our review processes for database migrations and cleanup operations. We sincerely apologize for any inconvenience this may have caused. We remain committed to improving our processes to provide a more reliable service. If you have any concerns or need assistance, please contact our support team.
Minor December 15, 2024 Data Processing Delays - Zefort Sign and background tasks on my.zefort.com affected 13h
Started Dec 15, 2024, 11:30 PM UTC· resolved Dec 16, 2024, 12:30 PM UTC
- resolved Dec 16, 2024, 01:51 PM UTC
The background processing queues for my.zefort.com filled up, and the system was not able to keep up with the pace. This was due to unexpected timeouts and slowness in 3rd-party APIs some customers use for AI batch processing tasks. This affected many functionalities causing them to be unusually slow or appear to not work at all. Affected functionalities included Zefort Sign, strong authentications, and bulk actions. Additional processing capacity has been deployed, and a system update has been deployed to isolate potentially slow tasks and separate processing resources to avoid congestion.