Zingtree experienced a minor incident on July 20, 2026 affecting Zingtree, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 17, 2026, 09:42 AM UTC
We are currently experiencing a service disruption affecting Usage Reports. Our team is actively working to resolve the issue as quickly as possible.
- investigating Jul 17, 2026, 10:55 AM UTC
We are continuing to investigate the issue impacting our Usage Reports. We have engaged our service provider and are actively working to resolve the underlying backend disruption as quickly as possible.
- investigating Jul 17, 2026, 04:17 PM UTC
We are continuing to investigate the issue impacting our Usage Reports. We have engaged our service provider and are actively working with them to resolve the underlying backend disruption as quickly as possible. We remain closely engaged with our service provider and will share our next update as soon as we receive additional information or have meaningful progress to report. We appreciate your patience and understanding while we work toward a resolution.
- identified Jul 18, 2026, 09:48 AM UTC
We have identified the root cause of the issue and are actively working with our service provider to implement a resolution. Our team remains fully engaged and will continue working through the weekend to restore the service as quickly as possible. We will provide our next update as soon as we have additional information to share.
- identified Jul 18, 2026, 04:21 PM UTC
We have identified the source of the service disruption and are actively implementing the recovery plan. Our Technical Operations team is executing our established incident recovery process and working closely with our infrastructure partner to restore the affected service. If you require access to your data while restoration is in progress, please contact `[email protected]` for assistance. We will provide updates every four hours until service has been fully restored.
- identified Jul 18, 2026, 08:28 PM UTC
We are continuing work to restore the affected service. No new information is available at this time, but our Technical Operations team remains actively engaged. We will provide our next update in four hours, or sooner if one is available.
- identified Jul 19, 2026, 12:32 AM UTC
We are continuing work to restore the affected service. No new information is available at this time, but our Technical Operations team remains actively engaged. We will provide our next update in four hours, or sooner if one is available.
- identified Jul 19, 2026, 04:43 AM UTC
We are continuing work to restore the affected service. No new information is available at this time, but our Technical Operations team remains actively engaged. We will provide our next update in four hours, or sooner if one is available.
- identified Jul 19, 2026, 12:24 PM UTC
Our Technical Operations team remains actively engaged with our infrastructure partner to restore the affected service. Given the nature of this recovery process, updates at four-hour intervals no longer reflect meaningful progress milestones. We will provide our next update by 10:00 PM EDT Sunday, or sooner if one is available. If you require access to your data while restoration is in progress, please contact [email protected] for assistance.
- identified Jul 20, 2026, 04:07 PM UTC
Our Technical Operations team remains actively engaged with our infrastructure partner to restore the affected service. If you require access to your data while restoration is in progress, please contact mailto:[email protected] for assistance.
- monitoring Jul 20, 2026, 05:27 PM UTC
Usage Reports have been restored and are operating normally. We are continuing to monitor the service closely and will confirm full resolution once stability has been verified. We will provide our next update by 5:00PM CDT, or sooner if needed.
- resolved Jul 20, 2026, 09:52 PM UTC
Usage Reports have been fully restored and are operating normally. The disruption originated with an external infrastructure dependency and was resolved by our Technical Operations team through our established recovery process. We appreciate your patience during this incident. If you have questions about your report data during the affected period, please contact [[email protected]](mailto:[email protected]).