by HonkWatch

Is Opentext down in Bhutan?

Opentext has problems

Bhutan No reports in the last hour checked 3 min ago
Partial outage reported by Opentext 1 of 267 parts affected: Enterprise Service Management / Middle East ME22. Going on for 3 d 12 h. Updated 6 Nov, 21:09 UTC, 3 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Bhutan

Last 24 hours · Bhutan · times in UTC

0 reports

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

024 00:0006:0012:0018: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, 21:12 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 Bhutan

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 Bhutan. The report chart above is filtered to Bhutan.

Our own checks of opentext.com

Every 5 minutes, from our probes

Our checks from 33 cities: all fine.

Santiago: loaded in 804 ms Warsaw: loaded in 618 ms Tokyo: loaded in 974 ms Amsterdam: loaded in 512 ms Lauterbourg: loaded in 622 ms Hamina: loaded in 784 ms Atlanta: loaded in 248 ms Bangalore: loaded in 1215 ms Delhi: loaded in 1613 ms Hong Kong: loaded in 1141 ms Madrid: loaded in 636 ms Tel Aviv: loaded in 1232 ms Jakarta: loaded in 1198 ms São Paulo: loaded in 745 ms Sydney: loaded in 1356 ms Port Louis: loaded in 1975 ms Johannesburg: loaded in 1544 ms Cape Town: loaded in 2553 ms Frankfurt: loaded in 550 ms Melbourne: loaded in 1127 ms Seattle: loaded in 485 ms Dallas: loaded in 499 ms Singapore: loaded in 1278 ms Querétaro: loaded in 624 ms Osaka: loaded in 957 ms Doha: loaded in 1621 ms Seoul: loaded in 1192 ms New York: loaded in 159 ms Portsmouth: loaded in 510 ms New Jersey: loaded in 636 ms Mumbai: loaded in 1160 ms Los Angeles: loaded in 1028 ms London: loaded in 547 ms
  • SantiagoReachable804 ms, just now
  • WarsawReachable618 ms, just now
  • TokyoReachable974 ms, just now
  • AmsterdamReachable512 ms, just now
  • LauterbourgReachable622 ms, just now
  • HaminaReachable784 ms, 1 min ago
  • AtlantaReachable248 ms, 1 min ago
  • BangaloreReachable1215 ms, 2 min ago
  • DelhiReachable1613 ms, 3 min ago
  • Hong KongReachable1141 ms, 3 min ago
  • MadridReachable636 ms, 3 min ago
  • Tel AvivReachable1232 ms, 3 min ago
  • JakartaReachable1198 ms, 3 min ago
  • São PauloReachable745 ms, 3 min ago
  • SydneyReachable1356 ms, 3 min ago
  • Port LouisReachable1975 ms, 3 min ago
  • JohannesburgReachable1544 ms, 4 min ago
  • Cape TownReachable2553 ms, 4 min ago
  • FrankfurtReachable550 ms, 4 min ago
  • MelbourneReachable1127 ms, 4 min ago
  • SeattleReachable485 ms, 4 min ago
  • DallasReachable499 ms, 4 min ago
  • SingaporeReachable1278 ms, 5 min ago
  • QuerétaroReachable624 ms, 5 min ago
  • OsakaReachable957 ms, 5 min ago
  • DohaReachable1621 ms, 5 min ago
  • SeoulReachable1192 ms, 6 min ago
  • New YorkReachable159 ms, 6 min ago
  • PortsmouthReachable510 ms, 6 min ago
  • New JerseyReachable636 ms, 6 min ago
  • MumbaiReachable1160 ms, 7 min ago
  • Los AngelesReachable1028 ms, 8 min ago
  • LondonReachable547 ms, 10 min ago
  • TorontoReachable209 ms, 15 min ago
  • St. LouisReachable675 ms, 15 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,618 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: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 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 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 49 checks failed

Recent problems

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

Having trouble with Opentext?

  1. Compare reports from Bhutan 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 Bhutan · Find another service