by HonkWatch

Is Opentext down in South Korea?

Opentext has problems

South Korea No reports in the last hour checked just now
Partial outage reported by Opentext 1 of 267 parts affected: Enterprise Service Management / Middle East ME22. Going on for 3 d 15 h. Updated 6 Nov, 23:47 UTC, just now · Official status page
Report a problemFollow community reports
Change country

Reports from people in South Korea

Last 24 hours · South Korea · times in UTC

0 reports

No community reports in the last 24 hours from South Korea. Having trouble? Add your report.

024 00:0006:0012:0018:0000:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 23:48 UTC

Report a problem with Opentext

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in South Korea

Monitor the provider status with HonkWatch

Get monitoring alerts for Opentext

HonkWatch watches the Opentext status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Opentext is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for South Korea. The report chart above is filtered to South Korea.

Our own checks of opentext.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Los Angeles: loaded in 818 ms Portsmouth: loaded in 510 ms New Jersey: loaded in 779 ms Hamina: loaded in 781 ms Frankfurt: loaded in 514 ms Doha: loaded in 1620 ms Querétaro: loaded in 596 ms Toronto: loaded in 174 ms Jakarta: loaded in 1203 ms Bangalore: loaded in 1158 ms St. Louis: loaded in 522 ms Lauterbourg: loaded in 595 ms Osaka: loaded in 991 ms New York: loaded in 185 ms Santiago: loaded in 753 ms Port Louis: loaded in 1876 ms Madrid: loaded in 600 ms Dallas: loaded in 895 ms Mumbai: loaded in 1211 ms Melbourne: loaded in 1129 ms Seattle: loaded in 431 ms Seoul: loaded in 1195 ms Tel Aviv: loaded in 1367 ms Cape Town: loaded in 1404 ms London: loaded in 472 ms Johannesburg: loaded in 1380 ms Delhi: loaded in 1498 ms Sydney: loaded in 1458 ms Amsterdam: loaded in 507 ms Warsaw: loaded in 626 ms Singapore: loaded in 1209 ms Atlanta: loaded in 197 ms São Paulo: loaded in 748 ms Hong Kong: loaded in 2130 ms Tokyo: loaded in 820 ms
  • Los AngelesReachable818 ms, just now
  • PortsmouthReachable510 ms, just now
  • New JerseyReachable779 ms, just now
  • HaminaReachable781 ms, just now
  • FrankfurtReachable514 ms, just now
  • DohaReachable1620 ms, just now
  • QuerétaroReachable596 ms, just now
  • TorontoReachable174 ms, just now
  • JakartaReachable1203 ms, just now
  • BangaloreReachable1158 ms, just now
  • St. LouisReachable522 ms, 1 min ago
  • LauterbourgReachable595 ms, 1 min ago
  • OsakaReachable991 ms, 1 min ago
  • New YorkReachable185 ms, 1 min ago
  • SantiagoReachable753 ms, 1 min ago
  • Port LouisReachable1876 ms, 1 min ago
  • MadridReachable600 ms, 1 min ago
  • DallasReachable895 ms, 1 min ago
  • MumbaiReachable1211 ms, 1 min ago
  • MelbourneReachable1129 ms, 1 min ago
  • SeattleReachable431 ms, 1 min ago
  • SeoulReachable1195 ms, 2 min ago
  • Tel AvivReachable1367 ms, 2 min ago
  • Cape TownReachable1404 ms, 2 min ago
  • LondonReachable472 ms, 2 min ago
  • JohannesburgReachable1380 ms, 2 min ago
  • DelhiReachable1498 ms, 2 min ago
  • SydneyReachable1458 ms, 2 min ago
  • AmsterdamReachable507 ms, 2 min ago
  • WarsawReachable626 ms, 2 min ago
  • SingaporeReachable1209 ms, 2 min ago
  • AtlantaReachable197 ms, 2 min ago
  • São PauloReachable748 ms, 2 min ago
  • Hong KongReachable2130 ms, 2 min ago
  • TokyoReachable820 ms, 2 min ago

This is separate from the status page: we request opentext.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Opentext

OpenText

Enterprise Service Management

  • Middle East ME22Major outage

266 other parts are working.

Incidents and maintenance

Open incidents

  • Middle East ME22 is experiencing an outage (investigating) Since 21 May 2026, 16:57 UTC. Affects Middle East ME22 · Details

Maintenance

  • Network Maintenance scheduled for 07 November 2026 (planned) 7 Nov, 21:00 UTC to 8 Nov, 01:00 UTC · Details
  • OCP Canada maintenance (planned) 7 Nov, 22:00 UTC to 8 Nov, 03:00 UTC. Affects Core Capture, Core Capture for SAP® Solutions, Core Collaboration for Engineering, Core Content Management and 3 more · Details
  • Network Maintenance scheduled for 08 November 2026 (planned) 8 Nov, 02:00 UTC to 8 Nov, 06:00 UTC · Details
  • C2334043 - Rescheduled Managed Services maintenance (planned) 8 Nov, 03:00 UTC to 8 Nov, 07:00 UTC · Details
  • IM4009810 C2337470 - Certificate Renewal (planned) 8 Nov, 03:00 UTC to 8 Nov, 07:00 UTC · Details
  • IM4009131 - Certificate Renewal (planned) 8 Nov, 04:00 UTC to 8 Nov, 06:00 UTC · Details
  • IM4004737 and C2343513 - Certificate Renewal (planned) 8 Nov, 04:00 UTC to 8 Nov, 06:00 UTC · Details
  • Frankfurt EU8 Infrastructure Upgrade Maintenance scheduled for 8 November 2026 (planned) 8 Nov, 04:00 UTC to 8 Nov, 08:00 UTC. Affects Frankfurt EU8 · Details
  • Oregon US6 Infrastructure Upgrade Maintenance scheduled for 8 November 2026 (planned) 8 Nov, 04:00 UTC to 8 Nov, 08:00 UTC. Affects Oregon US6 · Details
  • IM4004744 C2334766 - Certificate Renewal (planned) 8 Nov, 04:00 UTC to 8 Nov, 06:00 UTC · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 3 Nov

Of the last 90 days, 4 had a partial or major outage, 0 had maintenance only and 86 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of opentext.com that failed (9,577 checks). Shaded: when Opentext's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 00:0006:0012:0018:0000:00 0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed2% of 110 checks failed3% of 112 checks failed3% of 112 checks failed1% of 107 checks failed2% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 94 checks failed0% of 101 checks failed0% of 103 checks failed0% of 102 checks failed0% of 102 checks failed0% of 92 checks failed0% of 79 checks failed0% of 102 checks failed0% of 98 checks failed0% of 100 checks failed0% of 103 checks failed0% of 95 checks failed0% of 82 checks failed0% of 86 checks failed0% of 97 checks failed0% of 104 checks failed0% of 93 checks failed0% of 93 checks failed0% of 106 checks failed0% of 103 checks failed0% of 101 checks failed0% of 81 checks failed0% of 75 checks failed0% of 97 checks failed0% of 79 checks failed0% of 91 checks failed0% of 86 checks failed0% of 84 checks failed0% of 85 checks failed0% of 95 checks failed0% of 84 checks failed0% of 106 checks failed0% of 103 checks failed0% of 87 checks failed0% of 103 checks failed0% of 104 checks failed0% of 94 checks failed0% of 86 checks failed0% of 125 checks failed0% of 105 checks failed0% of 83 checks failed2% of 95 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 83 checks failed0% of 104 checks failed0% of 106 checks failed0% of 100 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 35 checks failed

Recent problems

3 Nov, 08:29 UTCPartial outagegoing on, 3 d 15 h1 of 267 parts affected: Enterprise Service Management / Middle East ME22
What can I try?

Having trouble with Opentext?

  1. Compare reports from South Korea and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Opentext down, or is it just me?

Opentext itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Opentext status page and load opentext.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Business software

See the live outage feed for South Korea · Find another service