IRONSCALES incident

Intermittent Disruptions in the US-hosted IRONSCALES environments

Major Resolved View vendor source →

IRONSCALES experienced a major incident on February 19, 2025 affecting Dashboard and AppAPI and 1 more component, lasting 1d 3h. The incident has been resolved; the full update timeline is below.

Started
Feb 19, 2025, 02:30 PM UTC
Resolved
Feb 20, 2025, 06:15 PM UTC
Duration
1d 3h
Detected by Pingoru
Feb 19, 2025, 02:30 PM UTC

Affected components

DashboardAppAPIOffice 365 ProtectionGoogle Workspace ProtectionMS Teams Protection

Update timeline

  1. investigating Feb 19, 2025, 06:51 PM UTC

    Dear customers, IRONSCALES has been experiencing intermittent issues in the US-hosted data center since morning GMT due to an unplanned database issue. This affects all customers that are hosted in our US data-center. At the moment, there are no new incidents being created. Your email flow is not interrupted, and all emails are arriving as usual. We are in the process of fixing it with the highest priority.

  2. investigating Feb 19, 2025, 10:18 PM UTC

    We are continuing to work on the issue. The technical team succeeded in narrowing down the problem and is now working closely with the AWS team and testing several possible solutions. We will follow up with more updates soon.

  3. identified Feb 20, 2025, 01:47 AM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Feb 20, 2025, 09:34 AM UTC

    We are in the final stages of implementing the fix, and we can already observe significant improvements in the system's performance.

  5. monitoring Feb 20, 2025, 12:07 PM UTC

    We would like to inform you that the service disruption in our US-hosted data center has been fully resolved. IRONSCALES has successfully processed the backlog of delayed emails, and no data loss has occurred. All systems are now fully operational, and the issue is considered closed. We appreciate your patience and support. We are still closely monitoring the status of all systems.

  6. resolved Feb 24, 2025, 12:50 PM UTC

    This incident has been resolved.