Live / OpenText / Incident
OpenText: Core Capture EU is experiencing degraded performance
OpenText · opentext.comMinor incidentResolved2026-10-08 00:27 UTC
Public — what happened
Summary
OpenText reported slower-than-usual processing for customers using its Core Capture service in the GCP-EU environment, beginning on 2026-09-30 at 15:17 UTC. The company said it found a likely cause within the hour and applied a fix that evening, but the slowdown came back on 2026-10-02 and again around 2026-10-05, when OpenText noted that transactions were still going through, only more slowly. OpenText said it worked with an outside vendor and applied several fixes that improved performance by 2026-10-07, and the incident was marked resolved on 2026-10-08 at 00:27.
Affected
Core Capture for SAPĀ® Solutions
Timeline
- Started — 2026-09-30 15:17 UTC
- Investigating — 2026-09-30 15:17 UTC
- Identified — 2026-09-30 16:11 UTC
- Monitoring — 2026-09-30 20:40 UTC
- Investigating — 2026-10-02 12:35 UTC
- Monitoring — 2026-10-02 19:15 UTC (3 updates)
- Resolved — 2026-10-08 00:27 UTC · 7 days 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 OpenText 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 OpenText: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the OpenText report →
More from OpenText
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.