CHYP.ai · ORBIT // Cloudy_Day Security Suite

CDN & edge

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 vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: Singapore (XSP)

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started53 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “[INC-1145] Service degradation of multiple PoPs”. 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

[INC-1145] Service degradation of multiple PoPs

minor resolved · started · resolved

6 updates

  1. investigating

    We have identified an issue affecting the XSP (Singapore) PoP. Customers may experience increased latency, Error 20 responses, and connectivity impacts related to GRE tunnels. Our teams are actively investigating the issue and working to determine the scope, impact, and root cause. We will provide further updates as soon as additional information becomes available. The next update will not be later than 08:10am UTC

  2. monitoring

    We have implemented corrective actions and service has returned to normal operation. The affected GRE tunnels have been successfully re-established, and traffic is flowing as expected across the previously impacted locations. Customers should no longer experience the increased latency or Error 20 responses previously observed. We are continuing to monitor the environment closely to ensure stability.

  3. identified

    We have identified an issue affecting multiple network locations (PoPs). Customers may experience increased latency, encounter Error 20 responses, and may be impacted by GRE tunnel connectivity issues. Our engineering teams are actively investigating the issue to determine the full scope, impact, and underlying cause. We are working to restore normal service as quickly as possible and will provide updates as more information becomes available.

  4. identified

    We have restored traffic flow across all previously affected PoPs, and GRE tunnel connectivity has been re-established. Traffic is currently routing as expected. While service has stabilized, our engineering teams remain actively engaged in investigating the underlying cause of the issue and monitoring the environment closely. Customers may have experienced increased latency, Error 20 responses, or GRE tunnel connectivity issues during the period of impact. We will continue to provide updates as our investigation progresses - the next update will be no later than 09:09 UTC

  5. monitoring

    We continue to observe stable operations across the previously affected PoPs, with no further signs of impact at this time. Engineering teams remain engaged and are closely monitoring the environment while the investigation into the underlying cause continues. We will provide a final update once monitoring activities have been completed.

  6. resolved

    The issue affecting multiple PoPs has been resolved. Services have recovered, and GRE tunnel connectivity has been restored across the impacted locations. Customers should no longer experience elevated latency or Error 20 responses related to this event. Our teams have validated service recovery and continue to monitor the environment to ensure ongoing stability.

Official incident page ↗

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.

Where to next