Incapsula incident

[INC-982] Istanbul Turkey (SAW) Data Center Issue

Minor Resolved View vendor source →
Started
Feb 27, 2026, 12:10 PM UTC
Resolved
Feb 28, 2026, 12:26 AM UTC
Duration
12h 16m
Detected by Pingoru
Feb 27, 2026, 12:10 PM UTC

Affected components

Istanbul, Turkey (SAW)

Update timeline

  1. investigating Feb 27, 2026, 12:10 PM UTC

    We have identified an issue in the Istanbul Turkey (SAW) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  2. identified Feb 27, 2026, 12:44 PM UTC

    We have identified an issue impacting connectivity through a third-party transit ISP. The provider is actively working to resolve the problem. We are closely monitoring the situation and will share further updates as soon as additional information becomes available. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  3. identified Feb 27, 2026, 02:19 PM UTC

    We are currently experiencing a connectivity issue related to a third-party transit ISP. Traffic has been rerouted through an alternate data center within the region to maintain service availability. During this time, some customers may experience increased latency until normal routing is fully restored. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  4. identified Feb 27, 2026, 05:54 PM UTC

    Traffic continues to remain rerouted through the alternate data center within the region to ensure service availability. We are actively following up with the third-party transit ISP(s) as they continue their investigation into the connectivity issue. During this time, some customers may experience increased latency until normal routing is fully restored. Further updates will be shared as more information becomes available. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  5. monitoring Feb 27, 2026, 11:36 PM UTC

    A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  6. resolved Feb 28, 2026, 12:26 AM UTC

    Service in the data center has been restored to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Looking to track Incapsula downtime and outages?

Pingoru polls Incapsula's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Incapsula reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Incapsula alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Incapsula for free

5 free monitors · No credit card required