Is OpenText down?

Last checked 7m ago
Current status
OpenText is down

2 active incidents: Frankfurt EU18 Application Maintenance scheduled for 20 Sep…, Frankfurt EU38 Application Maintenance scheduled for 20 Sep…

Official status page: https://status.opentext.com · Polled every 5 minutes · 267 components tracked

OpenText is reporting a major outage right now (last checked 7m ago). 2 active incidents on the official status page.

Real-time OpenText status, recent outages, and incident history — pulled directly from OpenText's official status page at https://status.opentext.com every 5 minutes. Pingoru tracks 267 OpenText services and has captured 250 incidents in the last 90 days (99.42% uptime). Get email, Slack, Discord, or webhook alerts the moment OpenText reports a new incident — free for 5 monitors, no credit card.

Users who monitor OpenText also follow these Project Management services: Atlassian Jira Software Trello Asana Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp View all 6,000+ providers
OpenText uptime 99.42% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 19m
    Started Sep 18, 2026, 03:11 PM UTC · Resolved Sep 18, 2026, 05:30 PM UTC
    Core Capture (corecapture.us.opentext.com)Core Platform - Content Transformation and Injection Services
    Timeline · 5 updates
    • investigating · Sep 18, 2026, 03:11 PM UTC

      Customers using CTIS-based ingestion in the OCP US environment may experience delays processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored. Teams are assembled and actively looking at the issue for root cause and remediation Reference: IM4001177

    • investigating · Sep 18, 2026, 03:23 PM UTC

      We are continuing to investigate this issue.

    • investigating · Sep 18, 2026, 04:38 PM UTC

      Customers using CTIS-based ingestion in the OCP US environment may experience delays in processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4001177

    • monitoring · Sep 18, 2026, 05:04 PM UTC

      CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM4001177

    • resolved · Sep 18, 2026, 05:30 PM UTC

      CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. The issue is now resolved. We appreciate your patience. Tracking Number: IM4001177

    Latest: CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. The issue i…

  2. Resolved 20m
    Started Sep 17, 2026, 03:29 PM UTC · Resolved Sep 17, 2026, 03:50 PM UTC
    Frankfurt EU8
    Timeline · 3 updates
    • investigating · Sep 17, 2026, 03:29 PM UTC

      Frankfurt EU8 is currently experiencing service degradation. Customers may experience intermittent issues accessing the service. Operations, Engineering, and Support teams are actively investigating the issue and working to restore service as quickly as possible. We are treating this as a high priority and will continue to closely monitor the environment while mitigation efforts are in progress. We appreciate your patience and understanding. We will share more updates as they become available. Tracking Number: IM4000627

    • resolved · Sep 17, 2026, 03:50 PM UTC

      Frankfurt EU8 experienced service degradation. Customers may have experienced intermittent issues accessing the service. The issue is now resolved. We appreciate your patience and understanding. Tracking Number: IM4000627

    • postmortem · Sep 18, 2026, 04:45 PM UTC

      # **Incident Report** **Tracking number**: IM4000627 PM1011731 **Incident window:** September 17, 2026, from 14:28 GMT to September 17, 2026, at 15:04 GMT **Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\) **RCA target completion date:** October 2, 2026 **Overview** On September 17, 2026, at 15:17 GMT, Incident Management was engaged to investigate performance degradation affecting OpenText™ Enterprise Service Management clients in the Frankfurt EU8 environment. **Impact** Users experienced performance degradation and reduced system responsiveness while accessing the application. **Resolution** The investigation identified high CPU and memory utilization within the database environment, that contributed to the observed performance delays. To mitigate the issue and restore service, technical teams created an index for the affected database query to improve query efficiency and executed a controlled restart of the affected deployments. Following these actions, technical teams validated that system performance and stability returned to normal operating thresholds. Full-service recovery was confirmed at 15:40 GMT on September 17, 2026.

    Latest: # **Incident Report** **Tracking number**: IM4000627 PM1011731 **Incident window:** September 17, 2026, from 14:28 GMT to September 17, 2026, at 15:04 GMT **Services affected:** Op…

  3. Resolved 41m
    Started Sep 14, 2026, 01:35 PM UTC · Resolved Sep 14, 2026, 02:16 PM UTC
    Frankfurt EU8
    Timeline · 4 updates
    • investigating · Sep 14, 2026, 01:35 PM UTC

      Frankfurt EU8 is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3998323

    • monitoring · Sep 14, 2026, 01:56 PM UTC

      Frankfurt EU8 experienced a service degradation. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3998323

    • resolved · Sep 14, 2026, 02:16 PM UTC

      Frankfurt EU8 experienced a service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3998323

    • postmortem · Sep 18, 2026, 12:42 PM UTC

      # **Incident Report** **Tracking number:** IM3998323 PM1011731 **Incident window:** September 14, 2026, from 12:32 GMT to 13:35 GMT **Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\) **RCA target completion date:** August 29, 2026 **Overview** On September 14, 2026, at 13:31 GMT, Incident Management was engaged to investigate service degradation affecting the OpenText™ Enterprise Service Management. **Impact** Several customers experienced performance degradation while using the OpenText™ Service Management \(SMAX\) application. The product UI was slow to resolve during this period for impacted customers and some logins were delayed. **Resolution** The investigation determined that a database spike initiated by an external integration resulted in the observed performance degradation. The integration was paused to reduce impact on the database and the system automatically. Performance stabilized at 13:35 GMT on September 14, 2026. OpenText has followed up on the integration with impacted customers to ensure best practices for use are followed going forward.

    Latest: # **Incident Report** **Tracking number:** IM3998323 PM1011731 **Incident window:** September 14, 2026, from 12:32 GMT to 13:35 GMT **Services affected:** OpenText™ Enterprise Serv…

  4. Resolved 2h 23m
    Started Sep 14, 2026, 12:26 PM UTC · Resolved Sep 14, 2026, 02:50 PM UTC
    Zix Archive Services - Business Communication ArchiveZix Archive Services - ZixArchive
    Timeline · 3 updates
    • investigating · Sep 14, 2026, 12:26 PM UTC

      Zix Archive Services BCA and ZixArchive are currently experiencing an issue when administrators navigate to the Archive pages of their respective interfaces. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3997654

    • monitoring · Sep 14, 2026, 01:31 PM UTC

      Zix Archive Services BCA and ZixArchive experienced an issue when administrators navigated to the Archive pages of their respective interfaces. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3997654

    • resolved · Sep 14, 2026, 02:50 PM UTC

      Zix Archive Services BCA and ZixArchive experienced an issue when administrators navigated to the Archive pages of their respective interfaces. The issue is now resolved. We appreciate your patience. Tracking Number: IM3997654

    Latest: Zix Archive Services BCA and ZixArchive experienced an issue when administrators navigated to the Archive pages of their respective interfaces. The issue is now resolved. We apprec…

  5. Resolved 24m
    Started Sep 09, 2026, 07:49 AM UTC · Resolved Sep 09, 2026, 08:13 AM UTC
    Frankfurt EU8
    Timeline · 3 updates
    • investigating · Sep 09, 2026, 07:49 AM UTC

      Frankfurt EU8 is currently experiencing service degradation with UCMDB service on EU8 farm. Clients may experience degradation while loading request entities or using an actual service on the EU8 farm. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3995249

    • resolved · Sep 09, 2026, 08:13 AM UTC

      Frankfurt EU8 experienced service degradation with UCMDB service on EU8 farm. The issue is now resolved. We appreciate your patience. Tracking Number: IM3995249

    • postmortem · Sep 11, 2026, 07:08 PM UTC

      # **Incident Report** **Tracking number:** IM3995249 PM1011727 **Incident window:** September 9, 2026, from 06:56 GMT to 07:53 GMT **Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\) **RCA target completion date:** September 23, 2026 **Overview** On September 9, 2026, at 07:38 GMT, Incident Management was engaged to investigate a service issue affecting the OpenText™ Enterprise Service Management Frankfurt EU8 farm. **Impact** Users experienced service degradation and delays when loading request entities. **Resolution** The investigation determined that gateway processing errors caused performance degradation within the UCMDB infrastructure, leading to the observed delays. To mitigate the issue, technical teams performed targeted service restarts to clear the gateway errors and restore connectivity. Following these actions, service health normalized, and normal functionality was restored at 7:42 GMT. Validations were completed at 07:53 GMT, ending the impact.

    Latest: # **Incident Report** **Tracking number:** IM3995249 PM1011727 **Incident window:** September 9, 2026, from 06:56 GMT to 07:53 GMT **Services affected:** OpenText™ Enterprise Servi…

See the full OpenText outage history

44 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse OpenText outage history →

Or sign up free to get alerts when OpenText breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 49 incidents View full outage history →