Critical October 12, 2026 - Detected by Pingoru
- Oct 12, 2026, 08:45 PM UTC
- Resolved
- Oct 14, 2026, 03:38 AM UTC
- Duration
- 1d 6h
Affected: End User Portal NA
Timeline · 3 updates
-
investigating Oct 12, 2026, 08:45 PM UTC
We are currently investigating an issue with the Cloudvoice portal (https://cloudvoice.kandy.io/), does not load. Users see "Kong Error".
-
monitoring Oct 13, 2026, 08:55 AM UTC
The issue has been identified and fixed and we are currently monitoring
-
resolved Oct 14, 2026, 03:38 AM UTC
This incident has been confirmed resolved, the Cloudvoice portal is now loading as expected.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2026, 01:11 PM UTC
- Resolved
- Jul 17, 2026, 07:35 PM UTC
- Duration
- 14d 6h
Affected: Call Services NA
Timeline · 12 updates
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 03:21 PM UTC
- Resolved
- Jun 04, 2026, 03:01 PM UTC
- Duration
- 23h 40m
Affected: Order & Subscription Management
Timeline · 4 updates
-
investigating Jun 03, 2026, 03:21 PM UTC
We are currently investigating stuck orders reports impacting EU production infrastructure
-
monitoring Jun 03, 2026, 03:48 PM UTC
A fix was implemented and the orders are reprocessing, we are monitoring for errors.
-
monitoring Jun 04, 2026, 03:41 AM UTC
We are continuing to monitor. No issues seen currently.
-
resolved Jun 04, 2026, 03:01 PM UTC
We have received confirmation that this issue is resolved. Please reach out if you require further assistance.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 03:55 PM UTC
- Resolved
- May 22, 2026, 08:11 PM UTC
- Duration
- 1d 4h
Affected: Media Integrations
Timeline · 5 updates
-
investigating May 21, 2026, 03:55 PM UTC
We are investigating an issue affecting the Google Ad Manager (GAM) integration for some customers. We will provide further updates as they become available.
-
investigating May 21, 2026, 04:36 PM UTC
We have identified the root cause of the issue and are in the proces of deploying a fix.
-
monitoring May 21, 2026, 09:47 PM UTC
The fix has been deployed to all environments and we have seen no further issues post deployment. We are actively monitoring.
-
monitoring May 22, 2026, 10:28 AM UTC
Monitoring continues.
-
resolved May 22, 2026, 08:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 07:51 AM UTC
- Resolved
- May 20, 2026, 07:13 AM UTC
- Duration
- 23h 21m
Affected: Call Services NA
Timeline · 4 updates
-
identified May 19, 2026, 07:51 AM UTC
We are currently monitoring a provider-reported fiber cable damage impacting Kandy US Call Services. The provider has advised that an 864 fiber cable was partially cut and is part of a near fully utilized system. Emergency maintenance is required to complete repairs. Field teams have secured the required materials and are preparing to excavate and replace approximately 3,000 feet of cable. Restoration activities are currently pending completion of the customer impact notification process. Once notifications are completed, the provider has indicated that a waiting period of approximately one hour will be observed before excavation and repair work can begin. At this time, an estimated time of restoration (ETR) is not yet available. We will continue to monitor the situation closely and provide further updates as more information becomes available.
-
identified May 19, 2026, 09:43 AM UTC
The provider has confirmed that customer notifications for the emergency maintenance was sent and restoration activities have now commenced. Repair operations began at 07:41 hrs UTC with field teams actively engaged onsite in executing the restoration work. We will continue to closely monitor progress and provide timely updates as further information becomes available.
-
identified May 19, 2026, 11:48 AM UTC
The provider has scheduled an emergency maintenance, which is currently ongoing with a planned end date: 19 May at 20:00 UTC. We will keep monitoring the service status and provide the latest updates when possible.
-
resolved May 20, 2026, 07:13 AM UTC
On May 19th at 9:40 UTC, there was a dark fiber disturbance in the CU metro area, affecting Metro Connect and Equinix Fabric customers. This incident resulted in a loss of redundancy for protected services and outages for unprotected services. The issue was resolved by the provider. The services were fully restored by May 19 at 09:48 UTC. As of now, the service is stable.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 09:59 PM UTC
- Resolved
- May 19, 2026, 01:08 AM UTC
- Duration
- 6d 3h
Affected: Call Services UAE
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 02:25 PM UTC
- Resolved
- May 11, 2026, 01:39 AM UTC
- Duration
- 3d 11h
Affected: End User Portal UAE
Timeline · 4 updates
-
investigating May 07, 2026, 02:25 PM UTC
We are currently investigating an issue that's causing KBS Portal to be unreachable. our infrastructure team is working on this with top priority.
-
monitoring May 07, 2026, 04:36 PM UTC
The infrastructure applied a fix and the portal is working for now. We are monitoring the situation.
-
monitoring May 08, 2026, 02:51 AM UTC
We are continuing to monitor for any further issues.
-
resolved May 11, 2026, 01:39 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 08:05 AM UTC
- Resolved
- May 05, 2026, 03:44 PM UTC
- Duration
- 7h 38m
Affected: Call Services NA
Timeline · 2 updates
-
monitoring May 05, 2026, 08:05 AM UTC
We are aware of an upstream provider issue affecting part of the underlying infrastructure. At this time, we are not observing any impact to our services due to built-in redundancy. We are continuing to monitor the situation and will provide updates if anything changes
-
resolved May 05, 2026, 03:44 PM UTC
Resolution: The dark fiber service was restored at 06:07 UTC following completion of provider maintenance. The service is stable and operating normally since then.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 07:41 PM UTC
- Resolved
- Apr 24, 2026, 07:07 PM UTC
- Duration
- 23h 25m
Affected: Call Services UAE
Timeline · 3 updates
-
investigating Apr 23, 2026, 07:41 PM UTC
Old recordings are not accessible, and new ones are not being recorded in the UAE. We are investigating the issue.
-
monitoring Apr 23, 2026, 11:22 PM UTC
The issue with call recordings has been resolved and new recordings are functioning correctly. We will continue to monitor this.
-
resolved Apr 24, 2026, 07:07 PM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 07:08 AM UTC
- Resolved
- Apr 23, 2026, 01:48 AM UTC
- Duration
- 18h 39m
Affected: Call Services NA
Timeline · 4 updates
-
identified Apr 22, 2026, 07:08 AM UTC
We have received reports of BGP connectivity issues. We have since identified the cause and confirmed with Equinix SMC that a fiber cut has been identified along Technology Drive, Culpeper, impacting the dark fiber link between DC14 and CU2. This incident is impacting the dark fiber link between DC14 and CU2 and has resulted in a BGP peer outage for affected customers. Technicians are currently onsite performing restoration work. An estimated time to repair (ETR) is not yet available. We will provide another update as soon as more information becomes available.
-
identified Apr 22, 2026, 08:03 AM UTC
Following updates from the dark fiber provider, their onsite technicians have begun pulling fiber in preparation for the re‑splicing work. Unfortunately, no estimated time to restore (ETR) has been provided at this time. They will provide another update once the re‑splicing activity has commenced.
-
monitoring Apr 22, 2026, 10:19 AM UTC
The cable cut has been fixed, and we are now monitoring for Stability.
-
resolved Apr 23, 2026, 01:48 AM UTC
The fiber cut impacting the dark fiber link between DC14 and CU2 has been fully resolved. Connectivity has been restored, and services are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 02:29 PM UTC
- Resolved
- Apr 12, 2026, 02:29 PM UTC
- Duration
- –
Affected: Call Services UAE
Timeline · 1 update
-
resolved Apr 12, 2026, 02:29 PM UTC
We identified an issue affecting a portion of CloudTalk users who were unable to log in due to a Keycloak connectivity problem. The issue has been resolved as of 14:00 UTC, and login functionality has been fully restored.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 11:43 AM UTC
- Resolved
- Apr 10, 2026, 12:49 PM UTC
- Duration
- 1d 1h
Affected: End User Portal UAECall Services UAECall Center UAEAuto Attendant UAEInstant Messaging UAEProvisioning Portal UAEVoicemail UAE
Timeline · 4 updates
-
investigating Apr 09, 2026, 11:43 AM UTC
We are currently investigating an issue affecting users in the UAE region, where login and connection attempts may fail across multiple platforms.
-
investigating Apr 09, 2026, 11:44 AM UTC
We are continuing to investigate this issue.
-
monitoring Apr 09, 2026, 12:07 PM UTC
The issue affecting login and connection attempts in the UAE region for Kandy has been mitigated, and services are now recovering. We are currently monitoring the system to ensure stability and full resolution.
-
resolved Apr 10, 2026, 12:49 PM UTC
The issue affecting login and connection attempts in the UAE region for Kandy has been fully resolved. Services have stabilized, and users should now be able to log in and connect normally across impacted platforms.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 04:17 PM UTC
- Resolved
- Mar 09, 2026, 10:36 PM UTC
- Duration
- 3d 6h
Affected: CloudSense
Timeline · 4 updates
-
investigating Mar 06, 2026, 04:17 PM UTC
We are currently investigating the issue of EU Digital Fulfilment not processing messages.
-
monitoring Mar 06, 2026, 04:47 PM UTC
We believe the issue has been resolved. We continue monitoring the situation.
-
monitoring Mar 09, 2026, 03:40 AM UTC
The issue has not been reported again. We are continuing to monitor this.
-
resolved Mar 09, 2026, 10:36 PM UTC
We have received no further reports of this issue and testing on our end indicates that this is resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 09:39 AM UTC
- Resolved
- Jan 21, 2026, 02:32 AM UTC
- Duration
- 1d 16h
Affected: CloudSenseDigital Commerce - Elastic
Timeline · 4 updates
-
investigating Jan 19, 2026, 09:39 AM UTC
We are currently investigating an issue that is impacting mainly e-commerce for both EU & APAC Regions. we are working on this with top priority
-
monitoring Jan 19, 2026, 05:03 PM UTC
Our team has identified and implemented a fix that we believe fixed the issue. We are monitoring the logs.
-
monitoring Jan 20, 2026, 03:38 AM UTC
No issues have been reported related to this. We are continuing to monitor this.
-
resolved Jan 21, 2026, 02:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 06:39 PM UTC
- Resolved
- Nov 14, 2025, 03:10 PM UTC
- Duration
- 20h 31m
Affected: Order & Subscription ManagementSecurity
Timeline · 5 updates
-
investigating Nov 13, 2025, 06:39 PM UTC
We are currently investigating errors with fullfillment returning 404 errors
-
monitoring Nov 13, 2025, 08:59 PM UTC
A fix has been implemented to address failures to refresh OAuth2 credentials, and we are monitoring the results
-
monitoring Nov 14, 2025, 10:27 AM UTC
We are continuing to monitor the situation and have confirmed that we have not seen the recent errors for the last two hours. Thank you for your continued patience as we work towards a resolution.
-
monitoring Nov 14, 2025, 10:30 AM UTC
We are continuing to monitor the situation and have seen no further errors occurring.
-
resolved Nov 14, 2025, 03:10 PM UTC
Our investigation has determined that the "(404) Not Found" errors are originating from Google Ad Manager (GAM). This indicates an issue on Google's side and is not related to the CloudSense platform. The incident can be tracked via Google’s official status page: https://ads.google.com/status/publisher/incidents/UjDUDxUnwHJUAZfvRJUL
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 07:35 AM UTC
- Resolved
- Nov 06, 2025, 10:04 AM UTC
- Duration
- 2h 29m
Affected: InstoreMobilogy Reports - CDA
Timeline · 2 updates
-
investigating Nov 06, 2025, 07:35 AM UTC
We have identified an issue with the Mobilogy License Server, causing license installation failures and impacting customer device operations. Our teams are working on this with highest priority.
-
resolved Nov 06, 2025, 10:04 AM UTC
The issue affecting the license server has been resolved, and service should be back to normal. Please reach out to Customer Support for any other requests.
Read the full incident report →
Critical November 4, 2025 - Detected by Pingoru
- Nov 04, 2025, 11:38 AM UTC
- Resolved
- Nov 04, 2025, 12:16 PM UTC
- Duration
- 37m
Affected: PPR Module
Timeline · 3 updates
-
identified Nov 04, 2025, 11:38 AM UTC
We have identified an issue with our PPR service and our infrastructure team is working on this with highest priority.
-
monitoring Nov 04, 2025, 12:16 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 04, 2025, 12:16 PM UTC
This incident has been resolved.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 11:36 AM UTC
- Resolved
- Oct 20, 2025, 11:12 PM UTC
- Duration
- 11h 36m
Affected: CloudSenseCatalog & Pricing ServiceAsync Task Accelerator ServiceConfigurator ServiceDigital Commerce SolutionDigital Commerce - ElasticDoc DiffMedia IntegrationsOrchestrator AcceleratorOrder & Subscription ManagementSecuritySolution ManagementCloudSense Sandbox EnvironmentPPR Module
Timeline · 3 updates
-
identified Oct 20, 2025, 11:36 AM UTC
AWS has confirmed increased error rates and latencies affecting multiple services in the US-EAST-1 region. The incident is currently classified as "Degraded" by AWS. You may experience slowness, timeouts, or trouble accessing some parts of platform and services. We're closely monitoring the situation and will keep you updated as AWS provides more information.
-
identified Oct 20, 2025, 01:43 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Oct 20, 2025, 11:12 PM UTC
AWS has confirmed that the outage in the US-EAST-1 region has now been resolved, and all services are operational.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2025, 10:58 AM UTC
- Resolved
- Oct 07, 2025, 02:41 PM UTC
- Duration
- 3h 43m
Affected: CloudSense
Timeline · 4 updates
-
investigating Oct 07, 2025, 10:58 AM UTC
We have identified an issue which prevents perform MACD and save orders in E2E process affecting the EU region. We are investigating the issue.
-
monitoring Oct 07, 2025, 11:09 AM UTC
A fix has been implemented and we are monitoring the results.
-
identified Oct 07, 2025, 01:12 PM UTC
We have received additional reports that the issue is recurring, and we have identified the issue. some of our customers in the APAC and EU may face trouble performing MACD and save orders.
-
resolved Oct 07, 2025, 02:41 PM UTC
Dear Customers, this has been resolved. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2025, 03:14 PM UTC
- Resolved
- Sep 24, 2025, 02:10 PM UTC
- Duration
- 1d 22h
Affected: CloudSense
Timeline · 4 updates
-
investigating Sep 22, 2025, 03:14 PM UTC
We are currently investigating an issue causing Pricing Service unavailability. Our team is working to identify the root cause and restore service.
-
monitoring Sep 22, 2025, 04:46 PM UTC
A fix has been implemented, and the Pricing Service is now operational. We are currently monitoring the system to ensure stability and full recovery.
-
monitoring Sep 22, 2025, 04:47 PM UTC
We are continuing to monitor for any further issues.
-
resolved Sep 24, 2025, 02:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2025, 10:23 AM UTC
- Resolved
- Sep 08, 2025, 12:12 PM UTC
- Duration
- 1h 48m
Affected: CloudSense Sandbox Environment
Timeline · 2 updates
-
identified Sep 08, 2025, 10:23 AM UTC
We have identified an issue that is affecting sandbox instances causing orders and baskets to not generate on Salesforce. Our teams are working on this with high priority.
-
resolved Sep 08, 2025, 12:12 PM UTC
Our infrastructure team has fixed the issue, if you encounter any further issues, please reach out to the support team
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2025, 03:32 PM UTC
- Resolved
- Aug 06, 2025, 03:14 AM UTC
- Duration
- 11h 41m
Affected: Catalog & Pricing ServiceCloudSense Sandbox EnvironmentPPR Module
Timeline · 4 updates
-
investigating Aug 05, 2025, 03:32 PM UTC
We are investigating an issue with an expired certificate affecting PPR and other services for EU customers.
-
identified Aug 05, 2025, 04:27 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 05, 2025, 04:36 PM UTC
A fix was implemented and we are monitoring the details
-
resolved Aug 06, 2025, 03:14 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2025, 01:37 AM UTC
- Resolved
- Jul 23, 2025, 03:48 PM UTC
- Duration
- 6d 14h
Affected: CloudSense
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- May 07, 2025, 04:33 AM UTC
- Resolved
- May 07, 2025, 05:48 AM UTC
- Duration
- 1h 15m
Affected: Configurator Service
Timeline · 3 updates
-
investigating May 07, 2025, 04:33 AM UTC
We are aware of an issue which is affecting the saving of baskets. Our team is actively investigating this.
-
monitoring May 07, 2025, 04:50 AM UTC
A fix has been implemented for this issue and we are monitoring this currently.
-
resolved May 07, 2025, 05:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2025, 03:59 PM UTC
- Resolved
- Apr 25, 2025, 03:12 AM UTC
- Duration
- 2d 11h
Affected: Media Integrations
Timeline · 3 updates
-
investigating Apr 22, 2025, 03:59 PM UTC
We have identified an issue with Digital Fulfillment messages in the EU region, resulting in 504 messages. We are currently investigating and will provide further details as they become available.
-
monitoring Apr 22, 2025, 05:05 PM UTC
We have implemented a fix and are monitoring the situation. We expect errors to no longer occur; however, reach out to Customer Support if you still experience problems.
-
resolved Apr 25, 2025, 03:12 AM UTC
This incident has been resolved
Read the full incident report →