Duration: 2 hours and 1 minute

Affected Components: Signal 311, Microsoft Dynamics 365, greymatter

Aug 20, 16:03:54 GMT+0
Investigating - There have been a few customer reports on overall CRM and portal performance. Microsoft has not updated their status page with any known current issue. We have opened a case with Microsoft and will continue to monitor their status page for any updates. .

Aug 20, 16:42:00 GMT+0
Identified - Update from Microsoft: Based on our initial analysis, the slowness and timeout behavior reported across the Dynamics 365 CRM environment is related to a **known platform issue** currently being investigated by Microsoft Engineering teams. The impact has been observed primarily within the Canada region, where elevated gateway thread pool scheduling latency and intermittent 503 (Service Unavailable) errors have resulted in degraded service performance. This may affect multiple scenarios, including: 1. Approval operations 2. Test flow executions 3. Manual flow invocations 4. General web role latency 5. Power Automate related service operations Microsoft Engineering teams have identified the underlying platform issue and have already rolled out mitigation measures to reduce the impact. Service performance has improved following the mitigation deployment; however, the incident remains under active investigation as engineering teams continue to monitor the service, validate the effectiveness of the mitigation, and work toward complete service restoration. The issue has been appropriately escalated and is receiving active attention from the responsible engineering teams. Coordination is ongoing with relevant platform teams, including Core Services and Service Fabric engineering groups, to determine the underlying cause and implement any additional corrective actions as needed. We understand the business impact of this issue and appreciate your patience and cooperation while our teams continue working toward full resolution. We will keep you informed of any significant updates as they become available..

Aug 20, 17:05:44 GMT+0
Monitoring - Update from Microsoft: We would like to provide an update regarding the service degradation experienced on **20 August 2026 between 12:07 UTC and 15:45 UTC**. During this period, your organization experienced intermittent service degradation, including increased latency and failures during platform operations. The impact was caused by an infrastructure issue affecting a dependent service, which resulted in reduced service capacity and degraded performance. Microsoft Engineering teams investigated the issue and identified the affected infrastructure components. Mitigation measures, including service failover and capacity scale-out activities, were successfully implemented to restore service availability and performance. Service health validations have confirmed that the environment has recovered and is operating normally. At this time, the service has been fully restored and is operating within expected performance parameters. Our teams continue to closely monitor the environment to ensure ongoing stability and reliability. Additionally, Microsoft is conducting a detailed root cause analysis and reviewing further resiliency and automated recovery improvements to help minimize the likelihood and impact of similar incidents in the future. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding throughout this event..

Aug 20, 18:05:07 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 51 minutes

Affected Components: Signal 311, Microsoft Dynamics 365, greymatter, Click Dimensions Marketing Automation

Jul 23, 18:37:57 GMT+0
Investigating - Source : <https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect> User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region. More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to: \- Microsoft OneDrive: Intermittent connection issues. \- SharePoint Online: Intermittent connection issues. Some users are receiving “Something went wrong” errors. \- Microsoft Teams: Degraded chat functionality, including images not loading. Additionally, real-time voice apps reporting and historical reporting are not functioning as expected. \- Copilot Chat: Intermittent delays using Copilot Chat and failures in query actions. \- Microsoft 365 Admin Center: Latency and intermittent inability to access features \- Power Automate: Automate flows not loading. \- Microsoft Loop: Unable to open or load Loop pages. \- Microsoft Purview: Degraded Purview DLP Agent response time. eDiscovery and Data Security Investigations failures when submitting new jobs and delays in processing existing jobs. \- Fabric/Power BI: Users in the West US region may encounter issues accessing Publish to Web reports. Some users in Europe and Asia Pacific regions may also be intermittently delayed when accessing Fabric artifacts due to service dependencies in West US. Current status: Our service telemetry indicates that rerouting traffic has provided some relief across affected services. We’re continuing to perform targeted traffic-routing actions while we revert the networking change mentioned in our last update. We're monitoring our telemetry and working directly with some impacted customers to ensure our actions are effectively addressing impact. We expect the configuration change reversion to complete by our next scheduled update, and we’re evaluating other pathways to expedite recovery. Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Users from other regions who are served by this infrastructure may also experience impact. Start time: Thursday, July 23, 2026, at 2:44 PM UTC.

Jul 23, 18:50:12 GMT+0
Monitoring - Current status: We’ve completed reverting the networking update, and our telemetry indicates impact is resolved for the vast majority of users. We're reviewing all known impact scenarios and monitoring for a period of time to confirm resolution for all affected environments..

Jul 23, 20:28:40 GMT+0
Resolved - **Current Update:** We are pleased to inform you that the incident has been mitigated and service has been restored..

Duration: 1 hour and 57 minutes

Affected Components: Microsoft Azure Services, greymatter

Jul 23, 18:32:23 GMT+0
Investigating - Source: <https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect> Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (<https://status.cloud.microsoft/>) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: App Service, Application Gateway, Azure AD B2C, Azure AI Search, Azure API Management, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL - Flexible Server, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We may have identified the likely cause of the issue and are actively deploying mitigation actions. Based on our current progress, we expect to have additional information on the effectiveness of these actions within approximately 30 minutes. We are closely monitoring service recovery as this action is rolling out. Last updated: Thursday, July 23, 2026 at 6:12:58 PM UTC.

Jul 23, 18:51:04 GMT+0
Identified - **Current Status:** We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

Jul 23, 20:29:06 GMT+0
Resolved - This incident has been resolved..

Duration: 1 day, 3 hours and 44 minutes

Jun 2, 20:35:13 GMT+0
Identified - We are aware that ticket update emails have not been sent out, we are working on a fix. Please for now, monitor your cases in the support portal to view any updates on your cases..

Jun 4, 00:19:37 GMT+0
Resolved - This is resolved, all ticket update emails are sending successfully. .

Duration: 22 hours and 29 minutes

Affected Components: Click Dimensions Marketing Automation, Microsoft Azure Services

Oct 29, 16:28:51 GMT+0
Investigating - We are investigating an issue with the Azure Portal where customers may be experiencing issues accessing the portal. More information will be provided shortly. This message was last updated at 16:18 UTC on 29 October 2025.

Oct 29, 16:37:20 GMT+0
Identified - Starting at approximately 16:00 UTC, we began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions. More information will be provided within 60 minutes or sooner. This message was last updated at 16:35 UTC on 29 October 2025.

Oct 29, 16:58:58 GMT+0
Identified - Starting at approximately 16:00 UTC, we began experiencing Azure Front Door issues resulting in a loss of availability of some services. In addition. customers may experience issues accessing the Azure Portal. Customers can attempt to use programmatic methods (PowerShell, CLI, etc.) to access/utilize resources if they are unable to access the portal directly. We have failed the portal away from Azure Front Door (AFD) to attempt to mitigate the portal access issues and are continuing to assess the situation. We are actively assessing failover options of internal services from our AFD infrastructure. Our investigation into the contributing factors and additional recovery workstreams continues. More information will be provided within 60 minutes or sooner. This message was last updated at 16:57 UTC on 29 October 2025.

Oct 29, 17:19:28 GMT+0
Identified - Starting at approximately 16:00 UTC, we began experiencing Azure Front Door issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from Azure Front Door (AFD) to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. This message was last updated at 17:17 UTC on 29 October 2025.

Oct 29, 17:30:23 GMT+0
Identified - This issue also continues to impact Click's web content from loading and other feature availability within their platform, primarily affecting users in the US and EU regions. .

Oct 29, 17:40:56 GMT+0
Identified - Microsoft have now confirmed that Azure Front Door (AFD) is currently experiencing a global outage affecting all regions. This issue continues to impact Click web content loading and certain platform features. Microsoft is actively working to restore service..

Oct 29, 17:50:19 GMT+0
Identified - From Microsoft : We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery. Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace). We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. .

Oct 29, 18:22:46 GMT+0
Identified - From Microsoft: **Current status:** We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. Customer configuration changes will remain blocked during this time as we work towards mitigation. We will communicate to customers when this block is reverted. Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace). We do not have an ETA for full mitigation, we will update this communication within 30 minutes, once the deployment is completed. Customers can consider implementing failover strategies with Azure Traffic Manager, to fail over from Azure Front Door to your origins This message was last updated at 18:11 UTC on 29 October 2025.

Oct 29, 18:58:59 GMT+0
Identified - From Microsoft: We do not yet have an ETA for full mitigation, but we will provide another update within 30 minutes or once the deployment has completed. At that point, we will have a clearer understanding of the timeline for full recovery..

Oct 29, 19:17:41 GMT+0
Identified - **Current status:** We have pushed our ‘last known good’ configuration, and customers may begin to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted. Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems. We are continuing to monitor progress closely and will provide an ETA for full mitigation within the next 20 minutes as we assess recovery across the AFD service. Although we are seeing signs of recovery, customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure. <https://learn.microsoft.com/en-us/azure/architecture/guide/networking/global-web-applications/overview>.

Oct 29, 19:29:19 GMT+0
Monitoring - From Microsoft: **Current status:** We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted. Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025\. We will provide another update on our progress within two hours, or sooner if warranted. Although we are seeing signs of recovery and have an estimated timeline, customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure. Learn more about Azure Front Door failover strategies for AFD: <https://learn.microsoft.com/en-us/azure/architecture/guide/networking/global-web-applications/overview> From Click: Microsoft has implemented a fix for the Azure Front Door (AFD) issue, and we are seeing positive recovery results. Previously affected areas, such as Email Editors, are now loading successfully, though performance may still be slightly slower than normal as full recovery completes. We are continuing to monitor closely and do not expect any further service degradation. Thank you for your patience while we worked through this issue with Microsoft..

Oct 29, 21:11:01 GMT+0
Monitoring - From Micorsoft: Affected Azure services include, but are not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID, Microsoft Purview, Microsoft Sentinel, Video Indexer, and Virtual Desktop. **Current status:** We initiated the deployment of our ‘last known good’ configuration, which has now successfully completed. We are currently recovering nodes and re-routing traffic through healthy nodes. As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. **This means we expect recovery to happen by 23:20 UTC on 29 October 2025** Customer configuration changes remain temporarily blocked to prevent new deployments that could interfere with recovery. We will notify customers once this block has been lifted. Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems. We will provide another update on our progress within two hours, or sooner if warranted. Although we are seeing signs of recovery, customers may also consider implementing existing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure. <https://learn.microsoft.com/azure/frontdoor/routing-methods>.

Oct 30, 14:57:54 GMT+0
Resolved - From Microsoft: **What happened?** Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. Affected Azure services include, but are not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Copilot for Security, Microsoft Defender External Attack Surface Management, Microsoft Entra ID (Mobility Management Policy Service, Identity & Access Management, and User Management UX), Microsoft Purview, Microsoft Sentinel (Threat Intelligence), and Video Indexer. Customer configuration changes to AFD remain temporarily blocked. We will notify customers once this block has been lifted. While error rates and latency are back to pre-incident levels, a small number of customers may still be seeing issues and we are still working to mitigate this long tail. Updates will be provided directly via Azure Service Health. **What went wrong and why?** An inadvertent tenant configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting both Microsoft services and customer applications dependent on AFD for global content delivery. The change introduced an invalid or inconsistent configuration state that caused a significant number of AFD nodes to fail to load properly, leading to increased latencies, timeouts, and connection errors for downstream services. As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy. We immediately blocked all further configuration changes to prevent additional propagation of the faulty state and began deploying a ‘last known good’ configuration across the global fleet. Recovery required reloading configurations across a large number of nodes and rebalancing traffic gradually to avoid overload conditions as nodes returned to service. This deliberate, phased recovery was necessary to stabilize the system while restoring scale and ensuring no recurrence of the issue. The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations. Safeguards have since been reviewed and additional validation and rollback controls have been immediately implemented to prevent similar issues in the future. **How did we respond?** * 15:45 UTC on 29 October 2025 – Customer impact began. * 16:04 UTC on 29 October 2025 – Investigation commenced following monitoring alerts being triggered. * 16:15 UTC on 29 October 2025 – We began the investigation and started to examine configuration changes within AFD. * 16:18 UTC on 29 October 2025 – Initial communication posted to our public status page. * 16:20 UTC on 29 October 2025 – Targeted communications to impacted customers sent to Azure Service Health. * 17:26 UTC on 29 October 2025 – Azure portal failed away from Azure Front Door. * 17:30 UTC on 29 October 2025 – We blocked all new customer configuration changes to prevent further impact. * 17:40 UTC on 29 October 2025 – We initiated the deployment of our ‘last known good’ configuration. * 18:30 UTC on 29 October 2025 – We started to push the fixed configuration globally. * 18:45 UTC on 29 October 2025 – Manual recovery of nodes commenced while gradual routing of traffic to healthy nodes began after the fixed configuration was pushed globally. * 23:15 UTC on 29 October 2025 - PowerApps mitigation of dependency, and customers confirm mitigation. * 00:05 UTC on 30 October 2025 – AFD impact confirmed mitigated for customers. **What happens next?** Our team will be completing an internal retrospective to understand the incident in more detail and will share findings within 14 days. Once we complete our internal retrospective, generally within 14 days, we will publish a final Post Incident Review (PIR) to all impacted customers. To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: <https://aka.ms/ash-alerts> For more information on Post Incident Reviews, refer to <https://aka.ms/AzurePIRs> The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: <https://aka.ms/AzPIR/Monitoring> Finally, for broader guidance on preparing for cloud incidents, refer to <https://aka.ms/incidentreadiness>.

Duration: 6 minutes

Affected Components: , Intermedia/Telax Non-Critical Services, Intermedia/Telax Hosted Contact Center Email, Intermedia/Telax Hosted Contact Center Voice, Telax-Intermedia →

Jul 31, 21:04:24 GMT+0
Identified - _Please note Telax reported Some Contact Center callers may be routed to a “closed” message because working-hours settings are missing for the affected account. Scheduled reports for that account may also be delayed._ _The Telax team is actively working to resolve the issue and will provide an update within 30 minutes or sooner if the status changes._.

Jul 31, 21:10:45 GMT+0
Resolved - Summary of Issue: Some Contact Center callers were routed to an after-hours greeting because the working-hours configuration for one account was missing. Scheduled reports for that account were also delayed. Business Impact: Service has returned to normal. Technical Details: Our Contact Center Engineering team resolved the issue by restoring the configuration from a recent backup. Please note that any changes made between 10:30 AM and 1:30 PM PT will need to be re-applied. We have tested and confirmed that all callers can now reach available agents as intended and scheduled reports are processing normally. If you continue to experience any issues, please contact our Support team for assistance..

Affected Components: Microsoft Dynamics 365, Microsoft Azure Services, Microsoft 365

Jul 19, 20:51:37 GMT+0
Resolved - Dear Valued Customers, You have probably already heard about it, but we wanted to formally inform you about a recent issue that may be currently impacting some services. This morning we were informed of a Crowdstrike outage that is affecting Microsoft Cloud, Azure, and virtual machines. **Our Response** We understand the critical nature of this situation and are taking immediate steps to address it. Our dedicated team is actively monitoring the situation and working closely with Crowdstrike and Microsoft to determine the full scope of the impact and restore normal operations as quickly as possible. **Our Commitment to You** Your trust and understanding are of utmost importance to us. We appreciate your patience as we work through this issue. Please know that we are fully committed to resolving this matter promptly and effectively. Our teams are on standby to provide support and updates. **Next Steps** We will continue to keep you informed with regular updates on the status of the outage and any actions you may need to take. In the meantime, if you have any questions or require immediate support, please do not hesitate to reach out to our customer retention team via our customer support portal. Thank you for your continued trust and understanding as we work to resolve this issue. Thank you, Frequency Foundry Retention Team.

Duration: 6 days, 21 hours and 34 minutes

Affected Components: Click Dimensions Marketing Automation

May 14, 17:19:24 GMT+0
Monitoring - ClickDimensions is investigating delays in adding Participants through Triggers in Campaign Automations. The duration of delays in adding Participants have varied but delays of a few hours have been observed. A fix has been implemented and we are monitoring the results..

May 21, 14:53:25 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 13 minutes

Affected Components: Click Dimensions Marketing Automation

Apr 9, 16:18:51 GMT+0
Identified - We have identified an issue causing pages not to load in the US data center and are working on a fix..

Apr 9, 16:51:21 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results..

Apr 9, 17:31:55 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 44 minutes

Affected Components: Click Dimensions Marketing Automation

Feb 6, 19:06:31 GMT+0
Monitoring - A fix has been implemented and we are continuing to monitor. Any existing delays should resolve soon. ### Time posted Feb 6, 18:42 UTC ### Components affected US Data Center - Email Statistics.

Feb 6, 20:50:47 GMT+0
Resolved - This incident has been resolved..

Duration: 2 hours and 9 minutes

Affected Components: Click Dimensions Marketing Automation

Jan 16, 16:56:34 GMT+0
Investigating - We are currently investigating an issue causing the CD App to display a "Service is unavailable" error intermittently when attempting to load an Email Template or Web Content builder, or when attempting to send an Email Send. If you encounter the error, please close the app and try opening it once more as this may bypass the error. .

Jan 16, 17:41:08 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results. .

Jan 16, 19:05:09 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 20 minutes

Affected Components: Microsoft Dynamics 365

Sep 27, 16:17:52 GMT+0
Investigating - https://foundrysupport.powerappsportals.com/ is currently down, we are working on a fix..

Sep 27, 17:37:47 GMT+0
Resolved - This incident has been resolved..

Duration: 9 minutes

Affected Components: Intermedia/Telax Hosted Contact Center Voice

Jul 11, 20:08:24 GMT+0
Investigating - Please be advised that we are currently experiencing an issue with our voice services causing call quality Our voice engineering team is actively working on a resolution..

Jul 11, 20:17:15 GMT+0
Resolved - This issue is resolved as of 15:58. Dear Valued Customer(s), Please be advised that we are currently experiencing an issue with our voice services causing call quality . Our voice engineering team is actively working on a resolution. We will provide an update as soon as available. We apologize for any inconvenience and thank you for your understanding. Sincerely, Business Technical Services Team .

Duration: 1 day, 18 hours and 34 minutes

Affected Components: Click Dimensions Marketing Automation

Jun 30, 15:07:56 GMT+0
Resolved - This incident was resolved as of 21:51 UTC yesterday. Our team has monitored results of the fix implemented at that time and further issues have not recurred. Please reach out to the Support team if you have any issues accessing hosted pages. Posted 19 hours ago. Jun 29, 2023 - 20:16 UTC.

Jun 28, 20:34:17 GMT+0
Investigating - We are currently investigating an issue for the Canada Datacentre where there are persistent Security Errors occurring on hosted pages (email editors, web content designers, and Campaign Automation builders etc.). Our team is attempting to mitigate the issues now and we will provide updates as soon as possible. Jun 28, 2023 - 20:22 UTC.

Jun 28, 21:53:49 GMT+0
Monitoring - A fix has been implemented for this issue and we are monitoring results. In our testing, this looks to be resolved. Please reach out to the Support team if you are still seeing issues accessing hosted pages. Jun 28, 2023 - 21:51 UTC.

Duration: 28 days and 13 minutes

Affected Components: Click Dimensions Marketing Automation

Jun 2, 19:35:28 GMT+0
Monitoring - Monitoring - Our team is continuing to work with our Microsoft cloud services provider for a long term fix for this issue. We have a critical severity escalation with their App Service team at this time. You should not experience any data loss or participant failures due to this issue. If you are seeing participant delays of more than a few hours at each node, please alert the support team of this for additional investigation. Jun 01, 2023 - 19:31 UTC.

Jun 5, 14:50:17 GMT+0
Monitoring - Update - For customers on our US Data center: a new Campaign Automation IP Address has been created, thus needs to be whitelisted on any relevant firewalls. The new IP address is 20.98.25.64/28 (20.98.25.64 / 255.255.255.240). .

May 25, 15:24:28 GMT+0
Investigating - Investigating - Currently our technology team has narrowed down the issue to our Microsoft Services. We have a critical severity escalation with their App Service team at this time and continue and hard at work to expedite the resolution of this issue. May 25, 2023 - 12:31 UTC Update - Our team continues to investigate this issue. We are seeing intermittent delays in the processing of Campaign Automations, primarily in our US data center. .

Jun 8, 15:58:15 GMT+0
Monitoring - Update - Our team has been able to implement a fix and we are seeing improved performance. At this time we are not seeing delays in progression and will continue to monitor for a few days. We will provide a root cause in the coming days..

Jun 22, 15:37:50 GMT+0
Resolved - This incident has been resolved..

Duration: 37 minutes

Affected Components: Microsoft Dynamics 365

Mar 31, 17:45:20 GMT+0
Investigating - We are currently having technical issues affecting the support portal, we are working to resolve this ASAP..

Mar 31, 18:22:15 GMT+0
Resolved - This incident has been resolved..

Duration: 2 hours and 6 minutes

Affected Components: Click Dimensions Marketing Automation

Feb 17, 18:17:50 GMT+0
Investigating - We are currently investigating an issue causing ClickDimensions forms/landing pages to show an error in the CAN data center. We are not aware of impact to other data centers at this time. Posted 1 minute ago. Feb 17, 2023 - 18:15 UTC.

Feb 17, 18:57:31 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results. .

Feb 17, 20:24:03 GMT+0
Resolved - This incident has been resolved. .

Duration: 2 hours and 37 minutes

Affected Components: Click Dimensions Marketing Automation

Dec 12, 20:53:08 GMT+0
Investigating - We are investigating an issue causing Web Content embed loading times to fluctuate in the US Posted 46 minutes ago. Dec 12, 2022 - 20:04 UTC This incident affects: US Data Center (Forms, Landing Pages, Surveys). https://status.clickdimensions.com/incidents/3sq90v728pq2.

Dec 12, 23:30:21 GMT+0
Resolved - This incident has been resolved. Posted 1 hour ago. Dec 12, 2022 - 21:58 UTC.

Duration: 57 minutes

Affected Components: Click Dimensions Marketing Automation

Sep 28, 16:17:30 GMT+0
Monitoring - A fix has been implemented and we are no longer seeing syncing delays. We are currently monitoring the fix, but if you continue to see any issues please contact ClickDimensions Support .

Sep 28, 16:01:33 GMT+0
Identified - Identified The issue has been identified and a fix is being implemented. Posted 11 minutes ago. Sep 28, 2022 - 15:48 UTC Investigating We are currently investigating an issue causing Form Capture and/or Web Content submissions to be delayed in syncing back to CRM. We have seen some success in mitigating this delay by re-authenticating the Service User. If you see you are impacted, please re-authenticate your Service User and contact ClickDimensions Support. Posted 1 hour ago. Sep 28, 2022 - 14:33 UTC This incident affects: US Data Center (Forms, Surveys), CAN Data Center (Forms, Surveys).

Sep 28, 16:58:33 GMT+0
Resolved - This incident has been resolved. .

Duration: 18 hours and 38 minutes

Affected Components: Intermedia/Telax Hosted Contact Center Voice

Sep 23, 15:27:18 GMT+0
Resolved - .

Sep 22, 20:49:18 GMT+0
Investigating - Be advised that ThinkTel is currently experiencing service interruptions. Our Engineers are currently investigating, Issue is intermittent and we are working on to address it..

Affected Components: Intermedia/Telax Hosted Contact Center Voice

Sep 22, 19:32:00 GMT+0
Investigating - Be advised that ThinkTel is currently experiencing service interruptions. Our Engineers are currently investigating, we do not have an ETR(Estimated Time to Restore) at the moment. .

Sep 22, 19:32:15 GMT+0
Resolved - [UPDATE - Sep 22, 2022 @ 15:27 ET] This issue is has been resolved as of 03:13 PM ET and we will continue to monitor to ensure no further service interruption..

Duration: 45 minutes

Affected Components: Intermedia/Telax Hosted Contact Center Voice

Sep 22, 14:19:10 GMT+0
Investigating - https://status.mycontactcenter.net/ Update - The Network team is currently investigating the issue with an onsite tech Sep 22, 2022 - 09:53 EDT Update - We are continuing to investigate this issue. Sep 22, 2022 - 09:53 EDT Investigating - We are currently investigating the issue. Issue within our TOR datacenter may impact some TOR clients ability to make outbound calls or receive inbound calls Sep 22, 2022 - 09:25 EDT.

Sep 22, 14:51:05 GMT+0
Identified - Identified - The issue has been identified and the network team is currently working to further mitigate the issue Sep 22, 2022 - 10:22 EDT.

Sep 22, 15:03:57 GMT+0
Resolved - Resolved - The issue has been identified and resolved.

Duration: 14 minutes

Affected Components: Click Dimensions Marketing Automation

Jun 9, 17:48:53 GMT+0
Identified - Identified The issue has been identified and a fix is being implemented. Posted 4 minutes ago. Jun 09, 2022 - 17:42 UTC Investigating We are currently investigating an issue wherein inboxcast does not provide a link to the generated email send in the US data center. Manually created email sends still function at this time..

Jun 9, 18:03:14 GMT+0
Resolved - This incident has been resolved. .

Duration: 1 hour and 58 minutes

Affected Components: Click Dimensions Marketing Automation

Jun 1, 18:11:36 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results. .

Jun 1, 17:30:29 GMT+0
Investigating - We are currently investigating an issue that causes intermittent "service is unavailable" errors in US Email and Web Content builders. At this time the issue is intermittent and can often be bypassed via refreshing the page. This incident affects: US Data Center (Email, Forms, Landing Pages, Surveys).

Jun 1, 19:28:29 GMT+0
Resolved - This incident has been resolved. .

Duration: 3 hours and 18 minutes

Affected Components: Intermedia/Telax Hosted Contact Center Voice

May 5, 22:58:11 GMT+0
Resolved - We just resolved the issue!.

May 5, 19:40:14 GMT+0
Investigating - Affecting - Automatic Call Distribution (ACD) https://status.mycontactcenter.net/ Update - We are continuing to investigate this issue. May 5, 15:32 EDT Investigating - We are currently investigating the call completion issue in the Toronto datacenter. The team is investigating..

May 5, 21:46:57 GMT+0
Monitoring - High Availability services are now operational .