Operational Imperva status
imperva.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Imperva problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS19551: routing data not loaded on this view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: CDN and WAF Management
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 82 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Service Degradation Affecting Email Notifications”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Imperva's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Imperva. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Imperva, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Imperva may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Imperva. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Service Degradation Affecting Email Notifications
minor resolved · started · resolved
6 updates
- investigating
We are currently investigating an issue affecting email notifications. Customers may experience delays or failures in receiving notification and confirmation emails. Our engineering teams are actively working to identify the cause and restore normal notification delivery as quickly as possible. We will provide additional updates as more information becomes available. The next update will be before 09:05 UTC.
- investigating
Our teams continue to actively investigate the issue affecting email notifications. We are working to identify the underlying cause and restore normal notification delivery as quickly as possible. Customers may continue to experience delays or failures in receiving notification and confirmation emails during this time. We will provide our next update no later than 09:30 UTC
- identified
We have identified a potential source of the issue affecting email notifications and are actively validating our findings. Our teams are working to implement and verify corrective actions while closely monitoring system behaviour. Customers may continue to experience delays or failures in receiving notification and confirmation emails during this period. We will continue to monitor the effectiveness of the mitigation efforts and provide further updates as additional information becomes available. The next update will be provided before 10:05 UTC.
- identified
Our investigation into the email notification degradation is ongoing. We have identified the affected notification flow and are actively working to restore normal delivery rates. While mitigation efforts continue, some customers may still experience delays or failures in receiving email notifications. We will continue to monitor the effectiveness of the mitigation efforts and provide further updates as additional information becomes available. The next update will be provided before 10:35 UTC.
- monitoring
We have implemented mitigation measures and are observing recovery in email notification delivery. Current monitoring indicates notification volumes have returned to expected levels, and email notifications are being processed successfully. We will continue to monitor the service closely to ensure recovery is sustained and to identify any residual impact.
- resolved
We have implemented corrective actions and confirmed that the affected functionality has been restored. Monitoring has shown normal service operation, and validation efforts indicate that requests are being processed successfully. Our teams will continue to review the incident to better understand the contributing factors and help prevent similar issues in the future. This incident has been resolved.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.