Skip to main content
Imperva

[INC-989] Tokyo, Japan (TKO) Data Center Issue

Degraded Lasted 20h 11m · started · Imperva's page

Level
confirmed
Worst impact
Degraded
Regions
apac, jp

What to do

  • Check whether you use Imperva in apac, jp. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 20h 11m it lasted.

    Anything that failed between 2026-03-06 02:20 UTC and 2026-03-06 22:31 UTC may need a replay.
  • Subscribe to Imperva's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=imperva works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Imperva 5

  1. investigating

    Technical teams are investigating a potential issue in the Tokyo, Japan (TKO) data center. 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.

    provider

  2. investigating

    Technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to ensure service stability. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time.   Engineering teams will continue monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation.   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.

    provider

  3. identified

    The technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to maintain service stability and is scheduled to be brought back online at 21:00 UTC. Customer traffic continues to be served normally through alternate PoP. 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.

    provider

  4. monitoring

    A fix has been implemented and traffic has been restored to the Tokyo, Japan (TKO) data center. We are continuing to monitor in order to ensure that service has returned to normal. 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.

    provider

  5. resolved

    Service in the Tokyo, Japan (TKO) data center has been restored to normal. 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-d4578f2344

Is Imperva still down?

No, this incident was resolved 2026-03-06 22:31 UTC. For Imperva's live state, see https://down.guide/imperva.

How long did it last?

20h 11m, from 2026-03-06 02:20 UTC to 2026-03-06 22:31 UTC, by the times Imperva posted.

What was affected?

Imperva named in apac, jp.

What caused it?

Imperva hasn't published a root cause. If it does, it shows here.

Where does this come from?

Imperva's official status page, https://status.imperva.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.