Nuance PowerShare Outage History

Nuance PowerShare is up right now

Nuance PowerShare had 31 outages in the last 2 years totaling 579h 14m of downtime — averaging 1.3 incidents per month.

There were 31 Nuance PowerShare outages since September 30, 2024 totaling 579h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nuancediagnosticsolutions.com/

Critical April 4, 2025

Service Disruption: mPower Cloud - Australia

Detected by Pingoru
Apr 04, 2025, 02:56 PM UTC
Resolved
Apr 04, 2025, 05:22 PM UTC
Duration
2h 26m
Affected: ANZ Market
Timeline · 4 updates
  1. investigating Apr 04, 2025, 02:56 PM UTC

    We are currently investigating reports of issues accessing the mPower application.

  2. identified Apr 04, 2025, 04:31 PM UTC

    The issue has been identified, and we are working to restore service.

  3. monitoring Apr 04, 2025, 04:54 PM UTC

    A fix has been implemented, and we are monitoring the results.

  4. resolved Apr 04, 2025, 05:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2025

Intermittent latency and delayed message delivery

Detected by Pingoru
Mar 19, 2025, 08:10 PM UTC
Resolved
Mar 20, 2025, 02:19 PM UTC
Duration
18h 9m
Timeline · 4 updates
  1. identified Mar 19, 2025, 08:10 PM UTC

    Users may experience latency issues and message delivery may be delayed in PowerConnect Actionable Findings (PCAF). This issue has been investigated and resolution is in progress.

  2. identified Mar 19, 2025, 08:12 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Mar 19, 2025, 09:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 20, 2025, 02:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 10, 2025

PowerConnect Actionable Findings: Outbound Call Center Workflow Impact

Detected by Pingoru
Mar 10, 2025, 05:39 PM UTC
Resolved
Mar 10, 2025, 05:47 PM UTC
Duration
7m
Timeline · 3 updates
  1. investigating Mar 10, 2025, 05:39 PM UTC

    Our team is currently investigating an issue at our Outbound Call Center which is impacting their ability to follow-up on actionable results. At this time, please follow-up on all actionable results internally. We will provide updates as soon as possible.

  2. monitoring Mar 10, 2025, 05:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 10, 2025, 05:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 7, 2025

Service Disruption: PowerScribe One Essentials - AutoText Manager

Detected by Pingoru
Feb 07, 2025, 06:38 PM UTC
Resolved
Feb 07, 2025, 06:49 PM UTC
Duration
10m
Affected: PowerScribe One Essentials
Timeline · 3 updates
  1. investigating Feb 07, 2025, 06:38 PM UTC

    We are currently investigating an issue where AutoText Manager is not available in PowerScribe One Essentials. Users will still be able to use current AutoText but are unable to edit and create new ones. We are working on resolving this issue.

  2. monitoring Feb 07, 2025, 06:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 07, 2025, 06:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 30, 2024

PowerConnect Actionable Findings

Detected by Pingoru
Sep 30, 2024, 12:36 PM UTC
Resolved
Sep 30, 2024, 01:39 PM UTC
Duration
1h 2m
Timeline · 3 updates
  1. investigating Sep 30, 2024, 12:36 PM UTC

    We are currently experiencing issues with PowerConnect Actionable Findings that may impact SMS alert delivery. At this time, Nuance is monitoring and directly notifying clients via phone of critical alerts where an impact is present while we work to address the notifications issue. Thank you for your patience while we work to resolve this as soon as possible.

  2. monitoring Sep 30, 2024, 01:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 30, 2024, 01:39 PM UTC

    This incident has been resolved.

Read the full incident report →