Plum Voice Outage History

Plum Voice is up right now

Plum Voice had 8 outages in the last 2 years — averaging 0.3 incidents per month.

There were 8 Plum Voice outages since October 23, 2024. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.plumvoice.com

Minor October 8, 2025

Intermittent Call Failures for Some Fuse PCI Customers

Detected by Pingoru
Oct 08, 2025, 09:21 PM UTC
Resolved
Oct 08, 2025, 09:21 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 08, 2025, 09:21 PM UTC

    Type: Incident Duration: 16 minutes Affected Components: PCI DEV, PCI Fuse Oct 8, 21:21:56 GMT+0 - Investigating - We are currently investigating reports of intermittent call failures affecting a subset of Fuse PCI customers. At this time, not all Fuse PCI customers are impacted. Our engineering team is actively reviewing the issue and working toward a resolution. Additional updates will be provided here as more information becomes available. Oct 8, 21:24:35 GMT+0 - Monitoring - We recognize there was impact to a subset of Fuse PCI customers. A fix has been implemented, and our team is currently monitoring the results to confirm stability. Oct 8, 21:38:16 GMT+0 - Resolved - This incident has been resolved. It was scoped to affect both Fuse PCI and PS DEV customers leveraging the PCI environment who have not yet been migrated to the new infrastructure. System performance has stabilized, and normal operations have resumed.

Read the full incident report →

Minor June 5, 2025

Intermittent Connectivity Issues with Fuse

Detected by Pingoru
Jun 05, 2025, 08:08 PM UTC
Resolved
Jun 05, 2025, 08:08 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 05, 2025, 08:08 PM UTC

    Type: Incident Duration: 2 hours and 52 minutes Affected Components: PCI Fuse, FUSE Jun 5, 20:08:53 GMT+0 - Investigating - We are currently investigating an incident involving intermittent connectivity issues with the Fuse service. Our team is actively working to identify the root cause and implement a resolution. Jun 5, 21:40:08 GMT+0 - Identified - We’ve identified the issue as related to elevated system load. The problem is still ongoing, but we’ve narrowed down the cause. You may continue to see delays or unexpected behavior to logging. We’ll provide updates as we make progress. Jun 5, 21:56:27 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 5, 23:00:34 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor April 30, 2025

Intermittent connectivity issues PCI

Detected by Pingoru
Apr 30, 2025, 08:37 PM UTC
Resolved
Apr 30, 2025, 08:37 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 30, 2025, 08:37 PM UTC

    Type: Incident Affected Components: PCI Fuse Apr 30, 20:37:00 GMT+0 - Resolved - We experienced an issue affecting the processing of inbound PCI numbers. The failure point was identified and corrective action was taken at 6:52 PM Eastern Time. Services are now operating normally.

Read the full incident report →

Minor December 20, 2024

Inbound IVR Disruption

Detected by Pingoru
Dec 20, 2024, 02:44 PM UTC
Resolved
Dec 20, 2024, 02:44 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 20, 2024, 02:44 PM UTC

    Type: Incident Duration: 1 day, 7 hours and 1 minute Affected Components: PCI Fuse, Inbound Calling , Outbound Calling, FUSE Dec 20, 14:44:57 GMT+0 - Investigating - We are aware of a current issue impacting some customers' IVR experiences. This is preventing inbound calls from connecting as expected. We have all necessary resources engaged and will resolve the issue as soon as possible. Dec 20, 14:59:07 GMT+0 - Identified - We have identified the issue and have implemented a workaround to restore service. You may experience a slight delay in initial connection time, but calls now connect. We are continuing working on a final fix. Dec 20, 15:11:46 GMT+0 - Identified - We have confirmed the full fix for this issue and are implementing it now. We expect resolution shortly. Dec 20, 15:15:57 GMT+0 - Resolved - This incident is resolved.

Read the full incident report →