Incapsula incident

[INC-1110] Queretaro, Mexico (QRO) Data Center Issue

Major Resolved View vendor source →

Incapsula experienced a major incident on August 20, 2026 affecting Queretaro, Mexico (QRO), lasting 6h 37m. The incident has been resolved; the full update timeline is below.

Started
Aug 20, 2026, 04:39 AM UTC
Resolved
Aug 20, 2026, 11:16 AM UTC
Duration
6h 37m
Detected by Pingoru
Aug 20, 2026, 04:39 AM UTC

Affected components

Queretaro, Mexico (QRO)

Update timeline

  1. investigating Aug 19, 2026, 10:17 PM UTC

    We have identified an issue in the Queretaro, Mexico (QRO) 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. Next update on the incident will be shared no later than 22:45 UTC

  2. identified Aug 19, 2026, 10:40 PM UTC

    We are experiencing issues with upstream providers in the region. To minimize customer impact, the affected PoP has been bypassed and traffic is being rerouted through an alternate data center. Customers may experience some increased latency while the reroute is in place. Our teams are actively monitoring the situation and working with the upstream providers. We will provide the next update as more information becomes available.

  3. identified Aug 20, 2026, 12:38 AM UTC

    We continue to work closely with our upstream providers, who have acknowledged the issue and are actively working to restore normal service. To maintain service continuity, the affected PoP will remain bypassed while the providers work on restoration. Customers may experience increased latency during this period. We will provide further updates as more information becomes available.

  4. identified Aug 20, 2026, 04:39 AM UTC

    We are continuing to work on a fix for this issue.

  5. identified Aug 20, 2026, 06:37 AM UTC

    One of our upstream providers has now restored service, and connectivity through that provider is back online. Work is currently in progress with the remaining upstream provider to restore full connectivity. The QRO PoP remains bypassed as restoration activities continue. We will provide further updates as more information becomes available.

  6. identified Aug 20, 2026, 06:55 AM UTC

    One of our upstream providers has now restored service, and connectivity through that provider is back online. Work is currently in progress with the remaining upstream provider to restore full connectivity. The QRO PoP remains bypassed as restoration activities continue. We will provide further updates as more information becomes available

  7. monitoring Aug 20, 2026, 10:07 AM UTC

    Traffic has been restored to the affected QRO PoP and the bypass has been removed. Upstream providers continue to monitor the previously reported network issue, and service remains stable and operational at this time. We are closely monitoring performance and connectivity to ensure continued stability and will provide further updates if necessary.

  8. monitoring Aug 20, 2026, 10:37 AM UTC

    Traffic has been restored to the affected QRO PoP and the bypass has been removed. Upstream providers continue to monitor the previously reported network issue, and service remains stable and operational at this time. We are closely monitoring performance and connectivity to ensure continued stability and will provide further updates if necessary.

  9. resolved Aug 20, 2026, 11:16 AM UTC

    The issue affecting connectivity through the QRO PoP has been resolved. Following confirmation of stable network conditions, traffic has been restored to the QRO PoP and the bypass has been removed. We have continued to monitor service following the restoration and are no longer observing any impact. This incident is now resolved. We thank you for your patience while we worked to restore normal operations.