Is Incapsula down?
Last checked 1m agoActive incident: [INC-1173] - QRO PoP Connectivity Issue
Incapsula is reporting a partial outage right now (last checked 1m ago). Some components are affected; others remain operational.
Real-time Incapsula status, recent outages, and incident history: pulled directly from Incapsula's official status page at status.incapsula.com every 5 minutes. Pingoru tracks 103 Incapsula services and has captured 104 incidents in the last 90 days (99.09% uptime). Get email, Slack, Discord, or webhook alerts the moment Incapsula reports a new incident, free for 3 monitors, no credit card.
Active incident 1
- Queretaro, Mexico (QRO)
Timeline · 3 updates
- identified · Oct 29, 2026, 12:09 AM UTC
We have identified an issue in the 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.
- identified · Oct 29, 2026, 01:23 AM UTC
Traffic remains rerouted through alternate PoPs in the region. Customers may experience increased latency while the reroute is in place.
- identified · Oct 29, 2026, 02:59 AM UTC
Third-party upstream providers in the region are experiencing issues, and our teams remain in close contact with them for updates. Traffic will continue to be rerouted through alternate PoPs in the region while the providers work to resolve the issue.
Latest: Third-party upstream providers in the region are experiencing issues, and our teams remain in close contact with them for updates. Traffic will continue to be rerouted through alte…
-
Recent outages & incidents
Past 90 days- Cloud Security Management Platform
Timeline · 8 updates
- investigating · Oct 20, 2026, 08:43 AM UTC
We are investigating a service degradation affecting resolution for some newly onboarded sites. Our teams are working to determine the cause and will provide updates as more information becomes available. The next update will be provided by 09:15 UTC.
- identified · Oct 20, 2026, 09:04 AM UTC
Our internal teams have identified the service degradation that is affecting the newly onboarded sites. We are currently working to remediate the incident and further updates will be provided as information becomes available. The next update will be before 09:45 UTC
- identified · Oct 20, 2026, 09:43 AM UTC
Efforts into mitigating the issue are still ongoing. Further updates will be provided as information becomes available. The next update will be before 11:15 UTC
- identified · Oct 20, 2026, 10:26 AM UTC
Efforts to mitigate the issue are still ongoing. Our teams continue working to restore normal service. Further updates will be provided as information becomes available.
- identified · Oct 20, 2026, 12:54 PM UTC
Imperva teams continue working to mitigate the issue and restore normal service. We are currently implementing and validating mitigation actions. Further updates will be provided as information becomes available.
- identified · Oct 20, 2026, 02:28 PM UTC
Mitigation efforts are ongoing. Our teams have completed additional configuration changes and continue working to restore normal service. Further updates will be provided as information becomes available.
- monitoring · Oct 20, 2026, 04:12 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Oct 20, 2026, 04:21 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 8 updates
- investigating · Oct 19, 2026, 05:38 PM UTC
We have discovered a service degradation that is affecting newly onboarded sites having problematic with CNAME resolution. Investigation into the cause of the service degradation is currently ongoing. Further updates will be provided as information becomes available.
- investigating · Oct 19, 2026, 06:34 PM UTC
Our internal teams are continuing to investigate the service degradation that is affecting the newly onboarded sites. Investigation into the cause of the service degradation is ongoing. Further updates will be provided by 19:00 UTC
- investigating · Oct 19, 2026, 07:10 PM UTC
Investigation into the cause of the service degradation is currently ongoing. Further updates will be provided as information becomes available.
- identified · Oct 19, 2026, 07:27 PM UTC
Our internal teams have identified the service degradation that is affecting the newly onboarded sites. They are currently working to remediate the incident and further updates will follow.
- identified · Oct 19, 2026, 08:30 PM UTC
Following identification of the service degradation, our teams successfully tested mitigation measures and are actively working to deploy them and restore normal service.
- identified · Oct 19, 2026, 09:29 PM UTC
The impact has been mitigated, and normal service has been restored. Our teams are continuing to monitor the environment to confirm stability. The next update will be provided by 22:30 UTC.
- monitoring · Oct 19, 2026, 09:35 PM UTC
Mitigation efforts have concluded and new site resolution has returned to normal. The next update will be provided by 22:45 UTC.
- resolved · Oct 19, 2026, 10:47 PM UTC
Following successful mitigation and a period of monitoring, we have confirmed that the service is operating normally and the issue is resolved. We apologize for any inconvenience this may have caused.
Latest: Following successful mitigation and a period of monitoring, we have confirmed that the service is operating normally and the issue is resolved. We apologize for any inconvenience t…
-
-
Timeline · 3 updates
- investigating · Oct 15, 2026, 09:49 PM UTC
We are currently investigating an issue with SIEM log data that may affect the accuracy of information reported for some customers. Our team is working to assess the impact and identify the appropriate corrective actions. The next update will be provided by 22:30 UTC.
- identified · Oct 15, 2026, 10:36 PM UTC
We have identified the source of the SIEM log data issue affecting the accuracy of information reported for some customers. Our teams are actively working to implement mitigation measures and restore normal service. The next update will be provided by 23:00 UTC.
- resolved · Oct 15, 2026, 11:05 PM UTC
Mitigation measures have been implemented to address the SIEM log data issue. Our teams have confirmed the environment accuracy.
Latest: Mitigation measures have been implemented to address the SIEM log data issue. Our teams have confirmed the environment accuracy.
-
-
Timeline · 5 updates
- investigating · Oct 13, 2026, 03:18 PM UTC
We are currently investigating an issue that may be causing some customers to experience false positive IRA blocks. Our teams are actively working to identify the cause and mitigate the impact. The next update will be before 16:00 UTC.
- identified · Oct 13, 2026, 03:30 PM UTC
We have identified the cause of the issue that may be resulting in false positive IRA blocks for some customers. Our teams are actively working on mitigation measures and will provide additional updates as progress is made. The next update will be provided before 16:00 UTC.
- identified · Oct 13, 2026, 03:31 PM UTC
.
- monitoring · Oct 13, 2026, 04:28 PM UTC
We have implemented mitigation measures to address the issue that may have resulted in false positive IRA blocks for some customers. Current indicators show the mitigations are performing as expected, and we are actively monitoring the environment to confirm stability. The next update will be provided before 17:30 UTC.
- resolved · Oct 13, 2026, 05:29 PM UTC
We have completed monitoring and confirmed that the mitigation measures have successfully resolved the issue that resulted in false positive IRA blocks for some customers. Service is operating normally, and no further impact has been observed. We sincerely apologize for the inconvenience and appreciate your patience while our teams worked to identify and resolve the issue.
Latest: We have completed monitoring and confirmed that the mitigation measures have successfully resolved the issue that resulted in false positive IRA blocks for some customers. Service …
-
- Cloud Security Management Platform
Timeline · 4 updates
- identified · Oct 13, 2026, 01:29 PM UTC
We are investigating an issue affecting Imperva-generated certificate issuance. Customers may experience issues when onboarding new sites using an Imperva-generated certificate and renewing existing certificates. Customer assets and sites remain protected during this time. The next update will be before 14:00 UTC.
- identified · Oct 13, 2026, 01:58 PM UTC
We have identified the issue affecting the onboarding of new WAF sites and the issuance of new certificates. Our teams are actively working to restore normal service. The next update will be before 15:00 UTC.
- monitoring · Oct 13, 2026, 03:38 PM UTC
The issue was identified as a degradation affecting a third-party service. The issue should now be resolved, and certificate issuance is operating as expected. We are closely monitoring the service to ensure continued stability. The next update will be no later than 17:00 UTC
- resolved · Oct 13, 2026, 05:44 PM UTC
Monitoring has confirmed that the service is stable and certificate issuance is functioning as expected. No additional issues have been observed, and this incident has been resolved. Thank you for your patience.
Latest: Monitoring has confirmed that the service is stable and certificate issuance is functioning as expected. No additional issues have been observed, and this incident has been resolve…
-
See the full Incapsula outage history
28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Incapsula outage history →Or sign up free to get alerts when Incapsula breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Statuspage by Atlassian · 103 components checked every 5 minutesThe longest incident in the last year, [INC-1106] Elevated Latency for a Subset of Origin Fetch Traffic in Ashburn, VA (WDC) on August 13, 2026, ran for 20 days. 164 maintenance windows announced in the same period.
Most affected components, last 12 months
- Cloud Security Management Platform13
- CDN and WAF Management7
- New York 2, NY (EWR)7
- Chicago 1, IL (CHI)5
- Cloud Security Management Configuration Changes5
Latest incidents
- [INC-1173] - QRO PoP Connectivity Issue
We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency…
- [INC-1166] Service Degradation Affecting Newly Onboarded Sites
We are investigating a service degradation affecting resolution for some newly onboarded sites. Our teams are working to determine the cause and will provide…
- [INC-1165] Service Degradation Affecting Newly Onboarded Sites
We have discovered a service degradation that is affecting newly onboarded sites having problematic with CNAME resolution. Investigation into the cause of the…
- Started Oct 29, 2026, 12:09 AM UTC · ● 3h 59m
- Started Oct 20, 2026, 08:43 AM UTC · Resolved Oct 20, 2026, 04:21 PM UTC · 7h 38m
- Started Oct 19, 2026, 05:38 PM UTC · Resolved Oct 19, 2026, 10:47 PM UTC · 5h 9m
- INC-1163 SIEM log investigation ResolvedStarted Oct 15, 2026, 09:49 PM UTC · Resolved Oct 15, 2026, 11:05 PM UTC · 1h 15m
- Started Oct 13, 2026, 03:18 PM UTC · Resolved Oct 13, 2026, 05:29 PM UTC · 2h 11m
- Started Oct 13, 2026, 01:29 PM UTC · Resolved Oct 13, 2026, 05:44 PM UTC · 4h 15m
- Started Oct 09, 2026, 10:16 PM UTC · Resolved Oct 10, 2026, 10:11 AM UTC · 11h 55m
- Started Oct 05, 2026, 08:41 AM UTC · Resolved Oct 06, 2026, 01:48 AM UTC · 17h 7m