- Detected by Pingoru
- Oct 02, 2026, 01:27 PM UTC
- Resolved
- Oct 02, 2026, 07:41 PM UTC
- Duration
- 6h 13m
Affected: US-SouthEast (ATL) Region
Timeline · 4 updates
-
investigating Oct 02, 2026, 01:27 PM UTC
We have identified an issue causing a partial service degradation for a subset of customers in the [US-SouthEast] region. ControlOne Agents may experience intermittent connectivity or "Retrying" status
-
identified Oct 02, 2026, 01:51 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 02, 2026, 02:34 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 02, 2026, 07:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2026, 01:25 PM UTC
- Resolved
- Sep 23, 2026, 05:30 PM UTC
- Duration
- 4h 4m
Affected: US-MidWest (ORD) Region
Timeline · 3 updates
-
investigating Sep 23, 2026, 01:25 PM UTC
We are currently investigating service degradation in the US-Midwest (ORD) Region, affecting connectivity for a subset of customers.
-
monitoring Sep 23, 2026, 02:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 23, 2026, 05:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 06, 2026, 03:09 AM UTC
- Resolved
- Sep 06, 2026, 05:05 AM UTC
- Duration
- 1h 56m
Affected: ControlOne Management Portal
Timeline · 4 updates
-
investigating Sep 06, 2026, 03:09 AM UTC
We are investigating an issue that is causing ControlOne's Management portal and device management API to respond to requests more slowly than usual. The management portal may appear unresponsive, and ControlOne Agents attempting to connect may experience difficulties connecting.
-
identified Sep 06, 2026, 03:24 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 06, 2026, 03:39 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 06, 2026, 05:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 12:54 PM UTC
- Resolved
- Sep 03, 2026, 12:54 PM UTC
- Duration
- —
Affected: US-SouthWest (LAX) Region
Timeline · 3 updates
-
investigating Sep 02, 2026, 04:07 PM UTC
We are currently investigating a partial service degradation in the US-SouthWest (LAX) Region. Some customers are experiencing higher than normal latency and intermittent connectivity.
-
monitoring Sep 02, 2026, 07:49 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 03, 2026, 12:54 PM UTC
A large fiber cut in the Los Angeles area impacting upstream carriers has been repaired.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 06:48 PM UTC
- Resolved
- Sep 03, 2026, 06:58 PM UTC
- Duration
- 1d
Affected: Call Completion
Timeline · 6 updates
-
investigating Sep 02, 2026, 06:48 PM UTC
We are currently investigating an issue affecting inbound calls for some customers. The disruption is related to a fiber network failure impacting one of our upstream service providers. Our team is actively working with the provider to monitor recovery and restore normal inbound calling as quickly as possible. Outbound calling (unless routed through this provider) and other services are not currently impacted. We will provide additional updates as more information becomes available.
-
investigating Sep 02, 2026, 06:49 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 02, 2026, 07:08 PM UTC
We are continuing to investigate this issue.
-
identified Sep 02, 2026, 07:58 PM UTC
Our investigation has identified an ongoing fiber network incident affecting an upstream provider in the Los Angeles area that may be contributing to the issue. The impact is intermittent and does not affect all customers or calls. Our team is actively monitoring the situation and working with our upstream providers to determine the full impact and restore normal service. We will provide additional updates as more information becomes available.
-
monitoring Sep 03, 2026, 01:49 PM UTC
Our upstream carrier is observing expected calling behavior and will continue to monitor for stability.
-
resolved Sep 03, 2026, 06:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2026, 05:29 PM UTC
- Resolved
- Aug 28, 2026, 11:36 PM UTC
- Duration
- 6h 6m
Affected: US-SouthEast (ATL) Region
Timeline · 3 updates
-
investigating Aug 28, 2026, 05:29 PM UTC
We are currently investigating a partial service degradation in the US-Southeast (ATL) Region impacting bridge connectivity for a subset of customers.
-
monitoring Aug 28, 2026, 07:57 PM UTC
Impacted workloads have been rescheduled to alternate compute hosts and we are monitoring the results. The impacted hardware will undergo remediation actions for the affected physical components.
-
resolved Aug 28, 2026, 11:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 12:33 PM UTC
- Resolved
- Aug 14, 2026, 02:34 PM UTC
- Duration
- 2h 1m
Affected: ControlOne Management Portal
Timeline · 3 updates
-
identified Aug 14, 2026, 12:33 PM UTC
We have identified an issue affecting ControlOne Agent geolocation services. Agents may intermittently fail a location in the portal, or fail a device posture check that requires a location fix. As a workaround partners can remove geolocation from the policy.
-
monitoring Aug 14, 2026, 12:47 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 14, 2026, 02:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 08:10 PM UTC
- Resolved
- Aug 14, 2026, 02:22 AM UTC
- Duration
- 6h 11m
Affected: ControlOne Management Portal
Timeline · 4 updates
-
investigating Aug 13, 2026, 08:10 PM UTC
We are currently investigating an issue causing a subset of ControlOne Sites to report an incorrect ISP status in the ControlOne portal. This is a visual problem only and does not impact site connectivity.
-
identified Aug 13, 2026, 09:06 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 13, 2026, 10:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 14, 2026, 02:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2026, 01:29 PM UTC
- Resolved
- Aug 11, 2026, 07:47 PM UTC
- Duration
- 6h 18m
Affected: US-SouthEast (ATL) Region
Timeline · 3 updates
-
investigating Aug 11, 2026, 01:29 PM UTC
We are currently investigating a partial service degradation in the US-Southeast (ATL) Region.
-
monitoring Aug 11, 2026, 04:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 11, 2026, 07:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 09:18 PM UTC
- Resolved
- Aug 07, 2026, 09:57 PM UTC
- Duration
- 38m
Affected: ControlOne Management Portal
Timeline · 2 updates
-
identified Aug 07, 2026, 09:18 PM UTC
We are investigating an issue that is causing ControlOne's Management portal and device management API to respond to configuration changes more slowly than usual. The management portal may appear unresponsive until this clears.
-
resolved Aug 07, 2026, 09:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2026, 06:10 PM UTC
- Resolved
- Jul 30, 2026, 09:25 PM UTC
- Duration
- 3h 14m
Affected: Call CompletionBLF Presence
Timeline · 3 updates
-
identified Jul 30, 2026, 06:10 PM UTC
We are investigating an issue impacting inbound and outbound call failures. We we identified an incorrect configuration that caused this issue. We are working on a fix and will update soon.
-
monitoring Jul 30, 2026, 06:16 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 30, 2026, 09:25 PM UTC
This incident has been resolved. We have implemented an extra step so the automated config management doesn't trigger outside a declared maintenance window. We apologize for the disruption caused by this.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2026, 03:36 PM UTC
- Resolved
- Jul 30, 2026, 09:55 PM UTC
- Duration
- 6h 19m
Affected: US-SouthCentral (DFW) Region
Timeline · 3 updates
-
investigating Jul 30, 2026, 03:36 PM UTC
We have identified an issue causing a partial service degradation for a subset of customers in the US-SouthCentral ControlOne region. ControlOne Bridges may experience intermittent connectivity ControlOne Agents may experience intermittent connectivity or "Retrying" status
-
monitoring Jul 30, 2026, 04:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 30, 2026, 09:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 05:53 PM UTC
- Resolved
- Jul 09, 2026, 06:05 PM UTC
- Duration
- 11m
Affected: Call CompletionBLF Presence
Timeline · 3 updates
-
investigating Jul 09, 2026, 05:53 PM UTC
One of the servers in our fleet experiencing network connectivity issues and our engineering team is investigating. If you are in that server, you may experience intermittent call failures. We will resolve this quickly and thanks for your patience.
-
monitoring Jul 09, 2026, 05:55 PM UTC
We restarted the network interface and the calls should flow as usual. Thanks for your patience during this issue.
-
resolved Jul 09, 2026, 06:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 05:17 PM UTC
- Resolved
- Jul 07, 2026, 09:48 PM UTC
- Duration
- 4h 30m
Affected: Call CompletionBLF Presence
Timeline · 3 updates
-
investigating Jul 07, 2026, 05:17 PM UTC
We are currently investigating an issue causing partial inbound and outbound call failures for some customers. Affected users may experience failed call attempts, delayed call setup, or intermittent call completion issues. The issue does not appear to impact all calls or all customers. Our engineering team is actively investigating and working to restore full calling functionality. We will provide additional updates as more information becomes available.
-
monitoring Jul 07, 2026, 05:35 PM UTC
We have taken corrective action to address the partial inbound and outbound call failures affecting some customers. A small number of call processing servers were restarted to restore normal call flow. Call traffic has recovered, and we are currently monitoring the platform to confirm continued stability. Some users may have experienced failed call attempts, delayed call setup, or intermittent call completion issues during the incident. We will continue monitoring and provide a final update once the issue is fully resolved.
-
resolved Jul 07, 2026, 09:48 PM UTC
The issue causing partial inbound and outbound call failures has been resolved. Corrective action was taken by restarting a small number of call processing servers, which restored normal call flow. After continued monitoring, inbound and outbound calling have remained stable. Some customers may have experienced failed call attempts, delayed call setup, or intermittent call completion issues during the incident window. We apologize for the disruption and appreciate your patience while our team worked to restore service.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 03:24 PM UTC
- Resolved
- Jun 30, 2026, 07:45 AM UTC
- Duration
- 16h 20m
Affected: Call Center
Timeline · 4 updates
-
investigating Jun 29, 2026, 03:24 PM UTC
We are currently investigating an issue affecting the Realtime Call Center dashboard. Call center event processing is delayed due to a backlog in the event processing service, which may cause dashboard status, agent state, and call activity updates to appear stale or delayed. Inbound and outbound calling are not impacted. Calls continue to route and complete normally. Our team is working to restore realtime event processing and will provide updates as we make progress.
-
identified Jun 29, 2026, 04:33 PM UTC
**Update: Realtime Call Center Dashboard Delays** We have identified the issue affecting the Realtime Call Center dashboard. A backend event processing service became degraded due to a high volume of invalid messages, which caused call center status updates to be delayed. A fix has been implemented, and queued events are now being processed. The dashboard may continue to show delayed or stale status information while the backlog clears. Inbound and outbound calling remain unaffected. Calls continue to route and complete normally. We expect the Realtime Call Center dashboard to be current within the next hour.
-
monitoring Jun 29, 2026, 05:02 PM UTC
Queued events are now processing concurrently, and the Realtime Call Center dashboard is recovering. Due to the backlog and out-of-sequence event processing during recovery, some dashboards may show incorrect call-waiting counts for today. We are working to correct these values where possible. Inbound and outbound calling remain unaffected. Calls continue to route and complete normally. Realtime dashboard activity is expected to normalize as event processing catches up. Daily dashboard statistics should display as usual starting tomorrow.
-
resolved Jun 30, 2026, 07:45 AM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:43 PM UTC
- Resolved
- Jun 11, 2026, 11:34 AM UTC
- Duration
- 16h 51m
Affected: BLF Presence
Timeline · 3 updates
-
identified Jun 10, 2026, 06:43 PM UTC
We are currently experiencing a backlog in our call event processing system, which may cause delays in event-related updates. This may impact CDR processing, BLF status updates, and voicemail arrival indicators. Inbound and outbound calling remain operational, and voicemail delivery is not impacted. Our team is actively working to clear the backlog and will continue to monitor the system.
-
monitoring Jun 10, 2026, 08:50 PM UTC
We have identified and corrected the issue. Call Detail Records (CDRs) in Insights during the incident will be available within next 12 hours. New events are processing normally and are not expected to experience delays. Inbound and outbound calling, voicemail delivery, and new CDR processing are not impacted at this time. We will continue monitoring until the backlog is fully cleared.
-
resolved Jun 11, 2026, 11:34 AM UTC
All backlog Call Details Records have been processed. This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 08:32 PM UTC
- Resolved
- Jun 10, 2026, 02:04 AM UTC
- Duration
- 5h 31m
Affected: BLF Presence
Timeline · 3 updates
-
identified Jun 09, 2026, 08:32 PM UTC
We are currently experiencing a backlog in our call event processing system, which may cause delays in event-related updates. This may impact CDR processing, BLF status updates, and voicemail arrival indicators. Inbound and outbound calling remain operational, and voicemail delivery is not impacted. Our team is actively working to clear the backlog and will continue to monitor the system.
-
monitoring Jun 09, 2026, 09:44 PM UTC
We have identified and corrected the issue that caused a backlog in our event processing pipeline. The issue was related to a failed event consumer, which has now been restarted, and queued messages are processing successfully. Some Call Detail Records (CDRs) in Insights may continue to be delayed for the next few hours while the CDR processor catches up on previously delayed events. New events are processing normally and are not expected to experience delays. Inbound and outbound calling, voicemail delivery, and new CDR processing are not impacted at this time. We will continue monitoring until the backlog is fully cleared.
-
resolved Jun 10, 2026, 02:04 AM UTC
The backlog processing has been completed. This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 03:10 PM UTC
- Resolved
- Jun 04, 2026, 04:06 AM UTC
- Duration
- 12h 56m
Affected: Call Completion
Timeline · 3 updates
-
investigating Jun 03, 2026, 03:10 PM UTC
We are currently investigating an issue causing intermittent inbound and outbound call failures for some customers. Our engineering team is actively working to identify the root cause and restore normal call processing. We will provide an update as soon as more information is available.
-
monitoring Jun 03, 2026, 03:49 PM UTC
We have identified and mitigated the issue that caused intermittent call setup failures for some customers. The issue was related to a degraded backend component that impacted call processing on a subset of voice infrastructure. Our engineering team applied corrective action, and calls are now processing normally. We are continuing to monitor the platform closely to ensure stability.
-
resolved Jun 04, 2026, 04:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 04:11 PM UTC
- Resolved
- Jun 02, 2026, 08:57 PM UTC
- Duration
- 4h 45m
Affected: Call Completion
Timeline · 4 updates
-
investigating Jun 02, 2026, 04:11 PM UTC
We are currently investigating intermittent inbound and outbound call failures affecting some customers. Our team is actively working to identify the issue and will provide updates as they become available.
-
monitoring Jun 02, 2026, 04:49 PM UTC
We identified an issue affecting call processing on a subset of voice servers, which resulted in intermittent inbound and outbound call failures for some customers. Our engineering team applied corrective action, and call processing has returned to normal. We are continuing to monitor the platform closely to ensure stability.
-
monitoring Jun 02, 2026, 08:56 PM UTC
The issue causing intermittent inbound and outbound call failures has been resolved. Our engineering team identified a capacity constraint in a backend call processing service and applied corrective action. Calls are now processing normally, and the platform remains stable.
-
resolved Jun 02, 2026, 08:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 06:41 PM UTC
- Resolved
- May 29, 2026, 11:27 PM UTC
- Duration
- 4h 45m
Affected: Caller ID ResolutionSpamGuard Service
Timeline · 3 updates
-
identified May 29, 2026, 06:41 PM UTC
We have identified that our third-party CNAM provider is not responding within our required performance thresholds. To prevent call completion delays or failures, we are temporarily bypassing Caller ID name resolution for affected calls. During this time, calls may complete without a resolved caller identity or display name. Call delivery itself remains operational. Our team is working on a remediation plan and expects to implement a permanent solution within the next 72 hours. We will continue to monitor the service and provide updates as progress is made.
-
monitoring May 29, 2026, 09:02 PM UTC
The Caller Id resolution is working as expected. We are monitoring for any further issues.
-
resolved May 29, 2026, 11:27 PM UTC
The CNAM (Caller ID) service is fully functional without any performance constraints.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 03:20 PM UTC
- Resolved
- May 29, 2026, 08:19 AM UTC
- Duration
- 16h 58m
Affected: Call Completion
Timeline · 4 updates
-
identified May 28, 2026, 03:20 PM UTC
The UCaaS platform is experiencing intermittent inbound/outbound call failures. We are investigating the root cause.
-
monitoring May 28, 2026, 04:47 PM UTC
We have identified and mitigated an issue that was causing intermittent call completion failures. The issue was related to a third-party CNAM lookup service responding slower than expected. This delay caused some calls to fail over to our secondary data center, which resulted in intermittent disruption to call completion. We have temporarily disabled this dependency, and calls are now completing as expected. We are continuing to monitor call completion and overall service stability.
-
monitoring May 28, 2026, 04:58 PM UTC
We are continuing to monitor for any further issues.
-
resolved May 29, 2026, 08:19 AM UTC
This incident is marked as resolved. No further inbound call failures were observed.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 07:39 PM UTC
- Resolved
- May 27, 2026, 10:03 PM UTC
- Duration
- 2h 23m
Affected: Call Completion
Timeline · 4 updates
-
monitoring May 27, 2026, 07:39 PM UTC
In our primary data center inbound/outbound calls are failing in several voice Pods and they are being routed to our secondary data center. Callers may experience intermittent call failures until we resolve this issue.
-
identified May 27, 2026, 08:05 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 27, 2026, 08:48 PM UTC
We identified an issue with a third-party call-signing service provider and temporarily disabled that dependency to restore normal call flow. Calls are currently completing as expected. We are continuing to monitor call completion and will implement a remediation plan to reduce future impact from this dependency.
-
resolved May 27, 2026, 10:03 PM UTC
Call flow has returned to normal, and calls are completing as expected. We are closing this incident. Our team will continue with the planned remediation work to reduce future impact from this third-party call-signing dependency.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 12:30 PM UTC
- Resolved
- May 26, 2026, 12:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 26, 2026, 01:57 PM UTC
Between 7:30–7:45 AM CST, one of our voice servers experienced an issue that prevented it from processing inbound and outbound calls for a small subset of customers. The issue was isolated to a service module on the affected server. We restarted the server, and call processing resumed normally afterward.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 02:07 PM UTC
- Resolved
- May 22, 2026, 02:15 PM UTC
- Duration
- 1d
Affected: US-SouthEast (ATL) Region
Timeline · 4 updates
-
investigating May 21, 2026, 02:07 PM UTC
We are currently investigating an issue impacting Agent connectivity in our US-SouthEast (ATL) Region.
-
identified May 21, 2026, 03:08 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 21, 2026, 03:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 22, 2026, 02:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 10:51 PM UTC
- Resolved
- Apr 18, 2026, 02:45 AM UTC
- Duration
- 3h 53m
Affected: Call Completion
Timeline · 3 updates
-
investigating Apr 17, 2026, 10:51 PM UTC
Cytracom Engineering has identified an issue impairing outbound calls for a subset of our customers. We are investigating the root cause and working towards a full resolution. As updates become available, they will be posted here.
-
monitoring Apr 18, 2026, 12:16 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 18, 2026, 02:45 AM UTC
This incident has been resolved.
Read the full incident report →
