Data443 Outage History
Data443 partial outage View live status →Pingoru has recorded 9 incidents for Data443: 9 in the last 12 months and 0 in the last 90 days.
Incidents, newest first
Major May 12, 2026 Primary Firewall at one of the DCs has stopped responding 49m Cyren by Data443 API and Feed Services (cyren-api-gateway-trdu.data443.io), Cyren by Data443 Mail Relay Gateway - Premium (Premium Mail Gateway Service), Cyren by Data443 Anti-Spam Resolvers (asres-1.data443.io), Cyren by Data443 Anti-Spam Resolvers (asres-2.data443.io) and 5 more
Started May 12, 2026, 05:11 PM UTC· resolved May 12, 2026, 06:01 PM UTC
- investigating May 12, 2026, 05:11 PM UTC
Technician in on the way to invesigate.
- resolved May 12, 2026, 06:01 PM UTC
The incident has been resolved.
Notice April 28, 2026 Postgresql cluster for DHCP is read-only 2h 29m
Started Apr 28, 2026, 06:50 PM UTC· resolved Apr 28, 2026, 09:20 PM UTC
- investigating Apr 28, 2026, 06:50 PM UTC
The database replicas have desync due time drift. Shared NTP server is functioning correctly, the team is investigating further, while the database replicas resync.
- investigating Apr 28, 2026, 07:05 PM UTC
The databases are resynced. We are still investigating the NTP issue.
- investigating Apr 28, 2026, 07:48 PM UTC
The resynced replicas left the data in an unresolvable state to the application. We are rolling back to an earlier backup.
- monitoring Apr 28, 2026, 07:55 PM UTC
DHCP is again fully operational. We are monitoring the DHCP reservations roll out.
- monitoring Apr 28, 2026, 09:10 PM UTC
Services are mostly recovered. We're monitoring the last of the HAPairs come up.
- resolved Apr 28, 2026, 09:20 PM UTC
The incident has been resolved.
Major March 20, 2026 DNS Services - Flapping 2d 19h Cyren by Data443 API and Feed Services (CTWSD API Check), Cyren by Data443 API and Feed Services (Cyren FTP)
Started Mar 20, 2026, 08:07 PM UTC· resolved Mar 23, 2026, 03:17 PM UTC
- investigating Mar 20, 2026, 08:07 PM UTC
An issue has been acknowledged and we are investigating further.
- resolved Mar 23, 2026, 03:17 PM UTC
The incident has been resolved.
Major March 6, 2026 Network Flap 5m Breezemail.ai, Office365 Inbox Protection Manager, Sensitive Content Manager - DRM, Cyren by Data443 API and Feed Services (CTWSD API Check) and 14 more
Started Mar 06, 2026, 09:10 AM UTC· resolved Mar 06, 2026, 09:16 AM UTC
- resolved Mar 06, 2026, 09:16 AM UTC
A short outage occurred due to a CARP demotion event on the primary firewall node , which triggered a failover within the HA firewall pair. The failover temporarily interrupted network traffic while the secondary node assumed the master role. Root Cause The demotion was triggered by firewall link-state monitoring safety mechanism . Evidence indicates the link-state flap was likely caused by hardware-layer issues: Resolution High Availability (HA) functioned as designed: The secondary firewall automatically took over as the CARP master Network services were restored once failover completed Total impact time was approximately 6 minutes
Major January 28, 2026 Partial outage due to storage congestion 6h Cyren by Data443 API and Feed Services (CTWSD API Check), Cyren by Data443 API and Feed Services (api.ctmail - Health), Cyren by Data443 API and Feed Services (cyren-api-gateway-trdu.data443.io), Cyren by Data443 API and Feed Services (Cyren FTP) and 11 more
Started Jan 28, 2026, 05:00 AM UTC· resolved Jan 28, 2026, 11:00 AM UTC
- resolved Jan 28, 2026, 11:00 AM UTC
Automated backups forced congestion on the storage network, impact performance on critical services causing flapping and temporary outages while the backups are ongoing. All services have been recovered, and the team is addressing the oversight in the backup policy, limiting the bandwidth available.
Major January 12, 2026 api.ctmail.com is down 12m Cyren by Data443 API and Feed Services (api.ctmail - Health), Cyren by Data443 API and Feed Services (cyren-api-gateway-trdu.data443.io)
Started Jan 12, 2026, 07:43 PM UTC· resolved Jan 12, 2026, 07:56 PM UTC
- investigating Jan 12, 2026, 07:43 PM UTC
We are aware of an issue impacting the licensing api. The team has determined the cause to be a failed synchronization between a primary and a secondary DNS zone for the backing database server. We are currently working on remediating the issue, and expect services to return to normal once the zone synchronization is completed.
- resolved Jan 12, 2026, 07:56 PM UTC
The DNS zone has been successfully synchronized and the licensing API is restored.
Major November 24, 2025 Edge Firewall Power Loss - TRDU (Tierpoint Raleigh-Durham Datacenter) 7m
Started Nov 24, 2025, 08:09 PM UTC· resolved Nov 24, 2025, 08:16 PM UTC
- resolved Nov 24, 2025, 08:16 PM UTC
Incident Summary A firewall experienced an unexpected power loss due to its primary power cable becoming disconnected from the PDU (hybrid port connector) during movement of other equipment between cabinets in our Tierpoint RDU data center. The secondary power supply to a different PDU was loose due to heat expansion over time (and hybrid port). This resulted in a complete device outage. Contributing Factors Use of hybrid power cables and connectors that are susceptible to not being locked deeply enough. Lack of strain relief or securing mechanisms (e.g., Velcro ties, locking connectors). Corrective Actions Over the next few weeks: Complete replacement of existing power cables with versions that provide more secure, locking-style connections where possible. Re-apply Velcro/strap-based cable management to ensure all power cords are strain-relieved and anchored better than vendor supplied approaches. Increase physical verification and re-seating of both primary and secondary power supplies on a more frequent basis. Update documentation and review cable-handling procedures with onsite staff. Preventive Actions Implement a standard for using locking or retention-capable power cords for all critical devices. Add periodic checks during maintenance windows to ensure all power connections remain secure. Improve physical cable management around PDUs to minimize accidental contact. --DC Ops Team
Major November 24, 2025 Cyren API Services 7h 52m
Started Nov 24, 2025, 02:07 AM UTC· resolved Nov 24, 2025, 10:00 AM UTC
- resolved Nov 24, 2025, 10:00 AM UTC
Overview On the evening of November 23 , services relying on AntiSpamDB experienced intermittent disruptions due to an issue within one of our SQL Server availability groups. A session responsible for database replication became stuck for several hours, causing AntiSpamDB to fall into a Not Synchronizing state. Normal operation was restored after the database was safely failed over and replication was re-established. Impact to Customers Services dependent on AntiSpamDB may have experienced intermittent access issues or temporary disruption. No data loss occurred, and database integrity was maintained throughout the incident.
Minor November 12, 2025 Intermittent Service Interruption Affecting api.ctmail.com 14h 50m
Started Nov 12, 2025, 01:09 AM UTC· resolved Nov 12, 2025, 04:00 PM UTC
- resolved Nov 12, 2025, 04:00 PM UTC
Incident Summary Between approximately 10:09 PM ET on November 11 and 11:00 AM ET on November 12 , some customers experienced intermittent unavailability or slower-than-normal performance when accessing api.ctmail.com (Cyren Licensing API). What Happened An unexpected surge of legitimate traffic to one of our other APIs temporarily placed additional load on shared backend systems. This caused intermittent performance issues for the Licensing API and related services. Customer Impact Some customers were briefly unable to reach api.ctmail.com . Others may have noticed slower responses or occasional connection failures. The impact was intermittent and fully resolved by 11:00 AM ET on November 12 . Resolution Once the underlying cause was identified, our engineering team made targeted adjustments to increase system capacity and improve how connections are handled under high load. These changes quickly stabilized performance, and normal operation was fully restored. Preventive Measures We’re implementing additional improvements to prevent a recurrence, including: Enhancing how traffic is balanced across backend systems Expanding capacity for handling high connection volumes Strengthening monitoring to detect early signs of resource saturation Adding safeguards to prevent one service’s traffic from affecting others Current Status All systems have been operating normally since November 12 at 11:00 AM ET , and no further issues have been observed.