Incapsula incident

[INC-1142] Network Connectivity Degradation Across Multiple PoPs Due to an Upstream Provider Issue

Minor Resolved View vendor source →

Incapsula experienced a minor incident on September 22, 2026 affecting Chicago 1, IL (CHI) and Detroit, MI (DET) and 1 more component, lasting 20h 27m. The incident has been resolved; the full update timeline is below.

Started
Sep 22, 2026, 11:29 AM UTC
Resolved
Sep 23, 2026, 07:57 AM UTC
Duration
20h 27m
Detected by Pingoru
Sep 22, 2026, 11:29 AM UTC

Affected components

Chicago 1, IL (CHI)Detroit, MI (DET)Houston, TX (HOU)Los Angeles, CA (SNA)Montreal, Canada (YUL)New York 2, NY (EWR)Seattle, WA (SEA)Toronto, Canada (TOR)Vancouver, Canada (VAN)Miami, FL (FLL)

Update timeline

  1. investigating Sep 22, 2026, 11:29 AM UTC

    One of our upstream providers is currently experiencing a major outage. We are contacting the provider to gather more information about the issue. As a mitigation, we have rerouted traffic away from the affected carrier at the impacted PoPs, which has mitigated customer impact. We will continue to closely monitor the environment to ensure ongoing service stability. Further updates will be provided as more information becomes available.

  2. monitoring Sep 22, 2026, 11:38 AM UTC

    We have rerouted traffic away from the affected carrier in the impacted PoPs, mitigating customer impact. We will continue to closely monitor the environment to ensure ongoing service stability.

  3. monitoring Sep 22, 2026, 02:45 PM UTC

    To maintain service stability, the impacted upstream provider remains bypassed. Our teams continue to closely monitor the environment and are working with the upstream provider to gather further information. Additional updates will be provided as more details become available.

  4. monitoring Sep 23, 2026, 07:57 AM UTC

    The affected network path remains bypassed as a precautionary measure to ensure continued service stability across the Imperva network. Following the mitigation actions implemented, service has been restored to normal and no further customer impact has been observed. Our teams continue to closely monitor the environment to ensure ongoing stability. At this time, the bypass remains in place while the external network issue is being addressed. Additional updates will be provided as more information becomes available.

  5. resolved Sep 23, 2026, 07:57 AM UTC

    This incident has been resolved.