Ziflow Outage History
Ziflow is up right nowPingoru has recorded 49 incidents for Ziflow: 10 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 2 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 5 of 507 (1%) |
Incidents, newest first
Minor October 21, 2026 Delays creating proofs from intake forms and workflows 4h 41m Proof Processing, Zibots
Started Oct 21, 2026, 04:59 PM UTC· resolved Oct 21, 2026, 09:41 PM UTC
- identified Oct 21, 2026, 04:59 PM UTC
We've identified the cause of delays affecting proof creation from intake forms and automated workflows. A backlog of queued requests is being processed, and proofs will be created as it clears; no action is needed from users and submissions do not need to be resent. Next update in approximately 60 minutes.
- identified Oct 21, 2026, 06:09 PM UTC
We’re continuing to work through delayed proof creation from intake forms and automated workflows. Part of the backlog has been cleared, and our team is actively addressing the remaining delayed requests. Submissions do not need to be resent; proofs will be created once processing completes. Next update in approximately 60 minutes, or sooner if there is a material change.
- monitoring Oct 21, 2026, 07:19 PM UTC
Our team continues to work through the backlog affecting proof creation from intake forms and automated workflows. Queues are steadily clearing, and new submissions are being processed in order as the backlog clears, so some delays will continue in the meantime. Submissions do not need to be resent. Next update in approximately 60 minutes.
- monitoring Oct 21, 2026, 08:17 PM UTC
Our team is deploying a fix to increase processing speed for the queued intake form requests, and proofs will be created as the backlog clears. Submissions do not need to be resent. Next update in approximately 60 minutes.
- resolved Oct 21, 2026, 09:41 PM UTC
This incident has been resolved. The issue was caused by a processing backlog that delayed proof creation from intake form submissions. A fix has been deployed, all delayed requests have been processed, and all affected systems are now operational.
Minor April 29, 2026 Proof Processing Performance Degradation 1h 22m Proof Processing
Started Apr 29, 2026, 06:52 PM UTC· resolved Apr 29, 2026, 08:15 PM UTC
- investigating Apr 29, 2026, 06:52 PM UTC
We are currently investigating degraded performance affecting proof processing. Some users may experience delays while text-based proof content is processed. Our team is actively reviewing the issue and working to restore normal processing performance. We’ll provide another update within 30 minutes or sooner if more information becomes available.
- resolved Apr 29, 2026, 08:15 PM UTC
This incident has been resolved. Proof processing performance has returned to normal, and all affected systems are now operational.
Minor March 4, 2026 Error Combining Non-Static Proofs 1h 57m Dashboard
Started Mar 04, 2026, 11:36 AM UTC· resolved Mar 04, 2026, 01:33 PM UTC
- investigating Mar 04, 2026, 11:36 AM UTC
We are currently investigating reports of an issue affecting the creation of combined proofs. Some users may experience an error when attempting to combine non-static files (such as GIFs, videos). We’ll provide an update within 30 minutes or sooner as more information becomes available.
- identified Mar 04, 2026, 12:01 PM UTC
We’ve identified the cause of the issue affecting comment attachments. Our team is implementing a fix now. Next update in approximately 60 minutes.
- resolved Mar 04, 2026, 01:33 PM UTC
This incident has been resolved. Please be sure to refresh you browser to see updates. If you continue to experience issues please notify our support team at [email protected].
Minor March 4, 2026 Inability to Access Comment Attachments 2h 24m Dashboard
Started Mar 04, 2026, 11:24 AM UTC· resolved Mar 04, 2026, 01:49 PM UTC
- investigating Mar 04, 2026, 11:24 AM UTC
We are currently investigating reports of an issue with comment attachments. Some users may experience an inability to open or download files attached to reviews. We’ll provide an update within 30 minutes or sooner as more information becomes available.
- identified Mar 04, 2026, 12:03 PM UTC
We’ve identified the cause of the issue affecting the creation of combined proofs. Our team is implementing a fix now. Next update in approximately 60 minutes.
- resolved Mar 04, 2026, 01:49 PM UTC
This incident has been resolved. If you continue to experience issues please contact our support team at [email protected].
Minor February 27, 2026 Issues with Proof Notification Delivery 1h 56m Dashboard
Started Feb 27, 2026, 05:11 PM UTC· resolved Feb 27, 2026, 07:08 PM UTC
- investigating Feb 27, 2026, 05:11 PM UTC
We are currently investigating reports of proof notifications not being delivered. Some users may not be receiving notifications for new proofs being created. We’ll provide an update within 30 minutes or sooner as more information becomes available.
- investigating Feb 27, 2026, 05:49 PM UTC
We are continuing to investigate this issue.
- identified Feb 27, 2026, 06:30 PM UTC
We’ve identified the cause of the issue affecting new proof notifications. New proof notifications are slightly delayed, but are now processing.
- monitoring Feb 27, 2026, 06:55 PM UTC
Proof Notification emails are now sending again. We’re continuing to monitor to ensure system stability.
- resolved Feb 27, 2026, 07:08 PM UTC
This incident has been resolved. All affected systems are now operational.
Minor February 27, 2026 Delayed Processing Speeds 52m Proof Processing
Started Feb 27, 2026, 03:19 PM UTC· resolved Feb 27, 2026, 04:12 PM UTC
- investigating Feb 27, 2026, 03:19 PM UTC
We are currently investigating reports of degraded processing performance within the platform. Some users may experience slower loading times for Proofs. Our engineering team is currently triaging the cause to restore full functionality.
- monitoring Feb 27, 2026, 03:42 PM UTC
A fix has been implemented and systems are recovering. We’re continuing to monitor to ensure system stability.
- resolved Feb 27, 2026, 04:12 PM UTC
This incident has been resolved.
Minor November 13, 2025 Flow slowness, Intake forms not processing 1h 13m Zibots
Started Nov 13, 2025, 06:59 PM UTC· resolved Nov 13, 2025, 08:13 PM UTC
- identified Nov 13, 2025, 06:59 PM UTC
We’ve identified the cause of the issue affecting the processing of Intake form submissions and overall slowness within flows Our team is implementing a fix now. Next update to follow in approximately 60 minutes.
- monitoring Nov 13, 2025, 07:07 PM UTC
A fix has been implemented, and systems are recovering. We’re continuing to monitor to ensure system stability.
- resolved Nov 13, 2025, 08:13 PM UTC
This incident has been resolved. All affected systems are now operational.
Minor November 7, 2025 Intake forms not processing 15m Zibots
Started Nov 07, 2025, 09:57 PM UTC· resolved Nov 07, 2025, 10:13 PM UTC
- investigating Nov 07, 2025, 09:57 PM UTC
We are currently investigating reports of Intake forms not processing. We’ll provide an update within 30 minutes or sooner as more information becomes available.
- resolved Nov 07, 2025, 10:13 PM UTC
This incident has been resolved. All affected systems are now operational.
Minor October 20, 2025 AWS Service Disruption Impacting Ziflow Access 7h 40m Dashboard, Proof Processing
Started Oct 20, 2025, 03:23 PM UTC· resolved Oct 20, 2025, 11:03 PM UTC
- investigating Oct 20, 2025, 03:23 PM UTC
We are currently investigating this issue.
- identified Oct 20, 2025, 03:53 PM UTC
We are currently experiencing degraded performance and limited access to the Ziflow platform due to a new service disruption affecting our hosting provider, Amazon Web Services (AWS), in the US-EAST-1 region. This issue follows a prior incident earlier today and is again related to instability within multiple AWS services, which may cause intermittent errors or prevent some users from accessing the platform. Our engineering team is actively monitoring the situation and working closely with AWS to restore full functionality as quickly as possible. We will continue to provide updates as more information becomes available.
- monitoring Oct 20, 2025, 06:21 PM UTC
Most Ziflow systems have now returned to normal operation following the AWS outage affecting the US-EAST-1 region earlier today. All key services, including Proof Viewer and account access, are now operational. However, due to the disruption, there is a backlog of proofs currently being processed, which may result in temporary delays as queued items complete. Additionally, video proofs may still experience slower processing times while AWS services continue to stabilize. Our team is monitoring progress closely and will provide another update once all processing queues have fully cleared and performance has returned to baseline.
- resolved Oct 20, 2025, 11:03 PM UTC
This incident has been resolved.
Major October 20, 2025 AWS Outage Impacting Proof Processing and Viewer Services 1h 57m
Started Oct 20, 2025, 07:30 AM UTC· resolved Oct 20, 2025, 09:27 AM UTC
- resolved Oct 20, 2025, 10:15 AM UTC
On October 20, 2025, our hosting provider Amazon Web Services (AWS) experienced a regional outage in US-EAST-1, leading to increased error rates and latency across multiple AWS services. This outage affected several of our systems, including Proof Processing and Proof Viewer, resulting in partial service disruption between 3:35 AM and 4:35 AM EDT (7:35 AM – 08:35 AM UTC). AWS identified the issue as related to DNS resolution failures impacting DynamoDB and dependent services. Mitigations were applied progressively, and AWS reported recovery signs around 5:27 AM EDT. Our systems resumed normal operations once AWS services stabilized. All our services are now operating normally, and we continue to monitor system performance to ensure full stability.
Minor June 17, 2025 Issue with adding users 1h 12m Dashboard
Started Jun 17, 2025, 01:45 PM UTC· resolved Jun 17, 2025, 02:57 PM UTC
- investigating Jun 17, 2025, 01:45 PM UTC
We are currently investigating this issue.
- identified Jun 17, 2025, 02:08 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 17, 2025, 02:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 17, 2025, 02:57 PM UTC
This incident has been resolved.
Minor June 5, 2025 Issues creating live website and rich media proofs 24m Proof Processing
Started Jun 05, 2025, 05:12 PM UTC· resolved Jun 05, 2025, 05:37 PM UTC
- investigating Jun 05, 2025, 05:12 PM UTC
Our team is currently investigating this issue.
- identified Jun 05, 2025, 05:19 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 05, 2025, 05:35 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 05, 2025, 05:37 PM UTC
This incident has been resolved.
Major March 19, 2025 Delayed Logins 1h 14m Dashboard
Started Mar 19, 2025, 03:29 PM UTC· resolved Mar 19, 2025, 04:43 PM UTC
- investigating Mar 19, 2025, 03:29 PM UTC
We are currently investigating this issue.
- investigating Mar 19, 2025, 03:30 PM UTC
We are continuing to investigate this issue.
- investigating Mar 19, 2025, 03:37 PM UTC
We are continuing to investigate this issue.
- identified Mar 19, 2025, 03:41 PM UTC
The issue has been identified and the team is working on a fix.
- monitoring Mar 19, 2025, 04:15 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 19, 2025, 04:16 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 19, 2025, 04:18 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 19, 2025, 04:43 PM UTC
This incident has been resolved.
Major December 3, 2024 Loading Dashboard Issue 29m Dashboard
Started Dec 03, 2024, 03:25 PM UTC· resolved Dec 03, 2024, 03:55 PM UTC
- investigating Dec 03, 2024, 03:25 PM UTC
We are currently investigating this issue.
- investigating Dec 03, 2024, 03:42 PM UTC
We are continuing to investigate this issue.
- identified Dec 03, 2024, 03:43 PM UTC
The issue has been identified and a fix is now being implemented.
- resolved Dec 03, 2024, 03:55 PM UTC
This incident has been resolved.