Is Incapsula down?

Last checked 1m ago
Current status
Incapsula is up

No incidents right now.

Official status page: https://status.incapsula.com · Polled every 5 minutes · 102 components tracked

Incapsula is operational right now. Last checked 1m ago; the most recent incident resolved 13d ago.

Real-time Incapsula status, recent outages, and incident history — pulled directly from Incapsula's official status page at https://status.incapsula.com every 5 minutes. Pingoru tracks 102 Incapsula services and has captured 96 incidents in the last 90 days (99.21% uptime). Get email, Slack, Discord, or webhook alerts the moment Incapsula reports a new incident — free for 5 monitors, no credit card.

Users who monitor Incapsula also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 SentinelOne Keeper Canary View all 6,000+ providers
Incapsula uptime 99.21% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 7h 9m
    Started Jul 29, 2026, 01:29 AM UTC · Resolved Jul 29, 2026, 08:39 AM UTC
    Support Phone Systems
    Timeline · 8 updates
    • investigating · Jul 29, 2026, 01:29 AM UTC

      We are aware of an issue affecting our support phone system globally. Users may be unable to reach support by phone. Our team is actively investigating the issue and working to restore service as quickly as possible. We apologize for the inconvenience . The next Status Update on this Incident will be provided no later than 02:00 UTC 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.

    • investigating · Jul 29, 2026, 02:10 AM UTC

      We are currently aware of a global issue impacting our support phone system. As a result, users may be unable to contact Support by phone. Our team is actively investigating the issue and working to restore service as quickly as possible. We apologize for any inconvenience this may cause. The next update on this incident will be provided no later than 02:40 UTC 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

    • investigating · Jul 29, 2026, 03:07 AM UTC

      We are currently investigating reports of a global issue impacting access to our support phone system. At this time, support phone numbers are operating normally, and users should be able to contact Support by phone. Customers are encouraged to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance while our team continues to monitor service stability. The next Status Update on this Incident will be provided no later than 04:00 UTC We apologize for any inconvenience and appreciate your patience. 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 · Jul 29, 2026, 04:32 AM UTC

      The issue has been identified, and our team is actively implementing corrective actions while monitoring the recovery progress. Support phone numbers are currently operating normally, and users should be able to contact Support by phone. Customers are encouraged to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance while our team continues to monitor service stability. Further updates will be provided 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.

    • monitoring · Jul 29, 2026, 05:34 AM UTC

      Our team is actively monitoring the service to ensure stability and continued availability. Support phone numbers are operating normally, and users should be able to contact Support by phone. Customers can continue to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance. The next Status Update on this Incident will be provided no later than 06:00 UTC 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.

    • monitoring · Jul 29, 2026, 06:26 AM UTC

      Our team continues to monitor the service to ensure stability and ongoing availability. Support phone numbers are operating normally, and users can contact Support by phone. Customers may continue to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance. The next status update for this incident will be provided no later than 07:00 UTC. 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.

    • monitoring · Jul 29, 2026, 07:10 AM UTC

      Our team continues to monitor the service to ensure stability and ongoing availability. Support phone numbers are operating normally, and users can contact Support by phone. Customers may continue to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance. The next status update for this incident will be provided no later than 11:00 UTC. 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.

    • resolved · Jul 29, 2026, 08:39 AM UTC

      The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. We appreciate your patience and understanding throughout this incident. 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.

    Latest: The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. We appreciate your patience a…

  2. Resolved 2h 23m
    Started Jul 27, 2026, 06:09 AM UTC · Resolved Jul 27, 2026, 08:32 AM UTC
    Support Ticketing System
    Timeline · 4 updates
    • investigating · Jul 27, 2026, 06:09 AM UTC

      We are investigating a potential issue affecting the Support Ticketing System. Customers may be experiencing issues logging into the Support Portal. Our technical teams are actively investigating the issue. The next update on the issue will be shared no later than 6:39 UTC.

    • investigating · Jul 27, 2026, 06:49 AM UTC

      Our teams are actively working to restore access to the Support Ticketing System. While this work is ongoing, customers experiencing issues accessing the Support Portal can reach our Support team for urgent assistance by calling +1 410 469 1651. Thank you for your patience as we work to resolve the issue.

    • monitoring · Jul 27, 2026, 07:45 AM UTC

      The issue preventing some customers from logging in to the Customer Support Portal has been resolved. Technical teams have completed remedial actions, and the portal has returned to normal operation. We are continuing to monitor the service to ensure stability and will provide a final update once monitoring is complete.

    • resolved · Jul 27, 2026, 08:32 AM UTC

      The issue that prevented some customers from logging in to the Customer Support Portal has been fully resolved. Technical teams implemented corrective actions and validated that normal login functionality has been restored. The Customer Support Portal is operating normally, and no further customer impact has been observed. We apologise for the inconvenience and appreciate your patience while we worked to resolve this issue. The incident is now closed.

    Latest: The issue that prevented some customers from logging in to the Customer Support Portal has been fully resolved. Technical teams implemented corrective actions and validated that no…

  3. Resolved 1d 1h
    Started Jul 17, 2026, 05:06 AM UTC · Resolved Jul 18, 2026, 06:30 AM UTC
    Rio de Janeiro, Brazil (RIO)
    Timeline · 9 updates
    • identified · Jul 17, 2026, 05:06 AM UTC

      We have identified an issue in the Rio de Janeiro, Brazi 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 · Jul 17, 2026, 06:06 AM UTC

      The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. Next update on the issue will be shared no later than 6:35 UTC. 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 · Jul 17, 2026, 06:41 AM UTC

      Our team is actively working to resolve the issue. To maintain service availability, traffic has been rerouted through an alternate data center in the region. Customers may experience increased latency while this temporary routing remains in place. Next update on the issue will be shared no later than 7:10 UTC. 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 · Jul 17, 2026, 07:14 AM UTC

      Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency. We will provide the next update no later than 7:45 UTC. 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 · Jul 17, 2026, 07:46 AM UTC

      Our team has identified a hardware issue within the routing infrastructure and is actively working with the vendor to troubleshoot and resolve the issue. To maintain service availability, traffic continues to be temporarily rerouted through an alternate data center in the region. Customers may continue to experience increased latency while this temporary routing remains in place. Next update on the issue will be shared no later than 8:15 UTC. 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 · Jul 17, 2026, 08:24 AM UTC

      We are actively working with Hardware vendor to resolve the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. The next update can be expected around 16:00 UTC. 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 · Jul 17, 2026, 03:25 PM UTC

      We have worked with the hardware vendor to address the underlying issue. Based on the current assessment and successful health checks, the team has scheduled the affected PoP to be reactivated at 03:00 UTC on 18 July 2026. To maintain service availability, traffic continues to be rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. The next update on this incident will be provided no later than 03:15 UTC on 18 July 2026.

    • monitoring · Jul 18, 2026, 05:35 AM UTC

      Technical team has successfully activated the PoP, and traffic has been restored to the Rio de Janeiro, Brazil (RIO) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. Next Status Update on this Incident will be provided no later than 6:03 UTC. 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.

    • resolved · Jul 18, 2026, 06:30 AM UTC

      The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally, and the PoP has been fully restored to normal operation. We appreciate your patience and understanding throughout this incident. 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.

    Latest: The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating no…

  4. Resolved 8h
    Started Jul 10, 2026, 03:38 PM UTC · Resolved Jul 10, 2026, 11:38 PM UTC
    Johannesburg, South Africa (QRA)
    Timeline · 5 updates
    • investigating · Jul 10, 2026, 03:38 PM UTC

      We have identified a potential issue in the Johannesburg, South Africa (QRA) 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 · Jul 10, 2026, 04:04 PM UTC

      The team has identified the underlying issue and implemented a fix. To ensure business continuity and validate service stability, the Johannesburg, South Africa (QRA) PoP is scheduled to be reactivated at 23:00 UTC . In the meantime, traffic is being rerouted through an alternate data center in the region. Customers may experience increased latency and intermittent timeouts while the reroute remains in place. The team continues to closely monitor the environment . Next update on the issue will be shared no later than 23:00 UTC.

    • identified · Jul 10, 2026, 11:06 PM UTC

      Our team is currently working to reactivate the affected Point of Presence (PoP). We will provide another update once the PoP has been successfully restored. In the meantime, traffic is being rerouted through an alternate data center within the region to maintain service availability. During this period, customers may experience increased latency and intermittent timeouts. The team continues to closely monitor the environment and is actively working to restore normal service as quickly as possible. Next update on the issue will be shared no later than 23:36 UTC.

    • monitoring · Jul 10, 2026, 11:10 PM UTC

      Technical team has successfully activated the PoP, and traffic has been restored to the Johannesburg, South Africa (QRA) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. Next Status Update on this Incident will be provided no later than 23:40 UTC.

    • resolved · Jul 10, 2026, 11:38 PM UTC

      Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident.

    Latest: Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally.…

  5. Resolved 10h 37m
    Started Jul 01, 2026, 09:40 PM UTC · Resolved Jul 02, 2026, 08:18 AM UTC
    Queretaro, Mexico (QRO)
    Timeline · 6 updates
    • investigating · Jul 01, 2026, 09:40 PM UTC

      Technical teams are investigating a potential issue in the Querétaro, MX (QRO) data center. The next Status Update on this Incident will be provided no later than 10:11 UTC. Further updates to follow. 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 · Jul 01, 2026, 09:54 PM UTC

      The technical teams have identified an issue affecting the Querétaro, MX (QRO) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation. The next Status Update on this Incident will be provided no later than 05:00 UTC. 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 · Jul 01, 2026, 10:52 PM UTC

      The technical teams have identified an issue affecting the Querétaro, MX (QRO) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation. The next Status Update on this Incident will be provided no later than 05:00 UTC. 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 · Jul 02, 2026, 04:59 AM UTC

      The technical teams have identified an issue impacting the Querétaro, Mexico (QRO) data center. To maintain service stability, the PoP will remain in bypass mode as a precaution and is scheduled to be restored during off-peak hours. Customer traffic continues to be served without interruption through an alternate PoP. Engineering teams are actively investigating the issue and working toward a resolution. The next status update will be provided no later than 07:00 UTC. 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.

    • monitoring · Jul 02, 2026, 07:15 AM UTC

      Technical team has successfully activated the PoP, and traffic has been restored to the Querétaro, MX (QRO) data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. The next Status Update on this Incident will be provided no later than 8:13 UTC. 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.

    • resolved · Jul 02, 2026, 08:18 AM UTC

      The technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. The PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident. 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.

    Latest: The technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating norma…

See the full Incapsula outage history

27 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

Outage history

Past 90 days · 32 incidents View full outage history →