Resolved -
This incident has been resolved.
Nov 27, 03:19 EST
Monitoring -
We have identified the underlying cause of the network disruption observed earlier this evening. The incident affected connectivity between 23:38:34 and 23:44:25, during which customers may have experienced intermittent connectivity and/or elevated latency.
The issue has been isolated, and no further impact is expected at this time. We are continuing to monitor network stability to ensure normal operation remains fully restored.
Nov 27, 00:21 EST
Identified -
Status Page Incident Notice — Network Degradation
Overview We are currently experiencing network-related issues impacting system connectivity and service performance. Initial indicators suggest intermittent packet loss and elevated latency across portions of our infrastructure.
Current Status Our engineering and infrastructure teams have been engaged and are actively investigating the source of the disruption. Diagnostics are underway across all relevant systems, including upstream network paths and internal service dependencies.
Impact Customers may observe delayed responses, failed requests, or temporary inability to access certain services. Impact may vary depending on region and workload.
Next Steps We will continue working to isolate the root cause and apply corrective measures. Additional updates will be posted as soon as new information becomes available or when remediation steps begin.
We appreciate your patience while we work to restore full service stability.
A maintenance window has been scheduled to update and validate access-control components within the Edge Security Services platform. The scope is limited to authentication and authorization policies, role mappings, and enforcement controls. No inspection, routing logic, or application-layer configurations are being modified outside of standard policy synchronization.
Work will focus on ensuring access-control policies remain accurate and consistently enforced across all edge points. Momentary rerouting between primary and secondary network paths may occur during ACL propagation and control-plane failover validation.
No impact to customer transaction flows is anticipated.
Our Operations team will monitor authentication logs, access-evaluation outputs, and allow/deny patterns during the maintenance window. Post-maintenance verification will confirm synchronized ACLs, correct role mappings, and uniform enforcement before closing the event.
If you have any questions about this notice, please contact support@zift.io
Cloudflare has confirmed resolution of the upstream network disruption that affected a wide range of internet services earlier today.
Zift’s systems remained stable throughout the event. No internal networks, hosting providers, or upstream processing networks experienced service degradation. While Zift uses Cloudflare for select edge and delivery functions, our core infrastructure and transaction-processing pathways continued to operate normally without any interruptions.
This incident is now closed.
Thank you, Zift Team.
Nov 18, 13:02 EST
Update -
At 09:42 EST (11/18/2025) CloudFlare indicated that a fix has been implemented. Zift is continuing to monitor this issue.
If you have any issues using Zift services please let us know at support@zift.io
Summary Zift is observing intermittent connectivity inconsistencies affecting a subset of API requests and dashboard interactions. These symptoms align with a widespread global incident involving Cloudflare, a network and security provider that Zift uses for edge routing and content delivery.
Impact: > Occasional latency increases, possibly failed transaction attempts through API and terminals > Access to Merchant Portal Services > No data-integrity or security concerns have been identified.
Root Cause (Upstream) The behavior is linked to a global Cloudflare network disruption currently impacting many internet services. Because Zift relies on Cloudflare for key network functions, some downstream effects are occurring within our environment.
What Zift Is Doing > Monitoring Cloudflare’s recovery progress and applying internal mitigations as appropriate. > Validating routing, performance, and service behavior across all regions. > Maintaining elevated engineering and incident-response coverage until recovery is confirmed.
What This Means for You You may experience intermittent connectivity or API/Portal issues while Cloudflare completes remediation. While this may affect traffic to Zift, all Zift internal operations and upstream processing services remain operational.
Next Update: Further updates will be provided as Cloudflare releases new information or if service conditions change.