Live / Imperva / Incident
Imperva: [INC-1142] Network Connectivity Degradation Across Multiple PoPs Due to an Upstream Provider Issue
Imperva · imperva.comMinor incidentResolved2026-09-23 07:57 UTC
Public — what happened
Summary
Imperva reported degraded network connectivity at several of its points of presence (PoPs) starting on 2026-09-22 at 11:29 UTC, which it attributed to a major outage at one of its upstream network providers. The company said it moved traffic off the affected carrier at the impacted locations, which it stated reduced the effect on customers, and it kept that provider bypassed while gathering details from them. By 2026-09-23 at 07:57 UTC, Imperva said service was back to normal with no further customer impact seen, and it marked the incident resolved, noting the bypass would stay in place while the outside issue was addressed.
Affected
Chicago 1, IL (CHI), Detroit, MI (DET), Houston, TX (HOU), Los Angeles, CA (SNA), Miami, FL (FLL), Montreal, Canada (YUL), New York 2, NY (EWR), Seattle, WA (SEA), Toronto, Canada (TOR), Vancouver, Canada (VAN)
Timeline
- Started — 2026-09-22 11:29 UTC
- Investigating — 2026-09-22 11:29 UTC
- Monitoring — 2026-09-22 11:38 UTC (3 updates)
- Resolved — 2026-09-23 07:57 UTC · 20h 28m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Imperva against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Imperva: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Imperva report →
More from Imperva
Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.