Pulsant Outage History

Started Mar 31, 2025, 11:42 AM UTC· resolved Apr 09, 2025, 11:19 AM UTC

1. investigating Mar 31, 2025, 11:42 AM UTC

   Pulsant have been made aware of a fibre fault in Reading SE-4. We have observed a number of alerts and are actively investigating. This is currently believed to only be a loss of resilience. If you believe you are seeing any impact please contact Pulsant support.

2. investigating Mar 31, 2025, 01:44 PM UTC

   The investigation into the fibre fault is ongoing. Additional Pulsant resources have been engaged to assist. Please update the Pulsant support team if you are seeing an impact.

3. identified Mar 31, 2025, 05:10 PM UTC

   Pulsant engineers have been preforming testing and have located the fibre fault. A Third party has been engaged to attend site on 01/04/25 to assess and repair damaged cabling.

4. identified Apr 01, 2025, 11:18 AM UTC

   Pulsant's Third-party fibre provider has assessed the fibre fault and found multiple breaks. Next steps are to excavate a pit to allow the fibre repair. We are currently awaiting an ETA to begin the work.

5. identified Apr 02, 2025, 02:34 PM UTC

   Pulsant's Third-party fibre provider has assessed the fibre fault and found multiple breaks. Repair plan is under review. Client circuits are stable and being continually monitored.

6. monitoring Apr 04, 2025, 06:14 PM UTC

   Pulsant's Third-party fibre provider has repaired the fibre break. We will continue to monitor. If you believe you are still being impacted please contact Pulsant Support.

7. resolved Apr 09, 2025, 11:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 27, 2025, 04:13 PM UTC· resolved Mar 01, 2025, 03:01 AM UTC

1. investigating Feb 27, 2025, 04:13 PM UTC

   We are currently investigating network issues affecting a number of clients. Updates will be provided as soon as possible.

2. investigating Feb 27, 2025, 05:00 PM UTC

   Investigations are still underway currently and updates will be provided as troubleshooting continues. We appreciate your patience at this time.

3. monitoring Feb 27, 2025, 05:33 PM UTC

   A fix has been implemented and we are seeing services back online from our monitoring systems. If you are experiencing further issues, please contact Pulsant support. We will continue to monitor.

4. resolved Mar 01, 2025, 03:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2025, 04:22 PM UTC· resolved Feb 26, 2025, 10:19 PM UTC

1. identified Feb 26, 2025, 04:22 PM UTC

   Please be aware of the following emergency network maintenance. What: The Network Infrastructure team will be performing a core network maintenance on our IP Fabric switches located in Maidenhead SE-2, in response to a device failure. As with any maintenance activity, there is an element of risk, although there is no expected impact as this is a resilient service. Why: This work is required to resolve a failed device in our IP fabric at the recommendation of the vendor. When: The maintenance will take place during the following window: Start: Wednesday 26th February 21:00 GMT End: Thursday 27th February 00:00 GMT If you have any questions, please raise a ticket by emailing [email protected] or by calling our support team directly.

2. resolved Feb 26, 2025, 10:19 PM UTC

   Emergency Network Maintenance in Maidenhead SE-2 IP Fabric successfully completed with full resilience being restored.

Read the full incident report →

Started Feb 08, 2025, 02:01 PM UTC· resolved Mar 01, 2025, 03:02 AM UTC

1. identified Feb 08, 2025, 02:01 PM UTC

   Pulsant Datacentre engineers have located a fault with a UPS unit in Datacentre SC-1 data hall 6 leading to a loss of resiliency. Emergency work is to be completed between 8:00 to 17:00 on 09/02/2025. No client impact is anticipated.

2. monitoring Feb 09, 2025, 04:07 PM UTC

   Emergency maintenance has been successfully completed, and UPS unit fault has been resolved. Further action is underway due to the identification of battery autonomy degradation as a result of the fault. Pulsant engineers are actively monitoring UPS status in Datacentre SC-1 data hall 6 following the work and until the follow-up activities are completed. No client impact is anticipated.

3. resolved Mar 01, 2025, 03:02 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2025, 03:01 PM UTC· resolved Feb 06, 2025, 07:54 AM UTC

1. investigating Feb 05, 2025, 03:01 PM UTC

   We are currently investigating a potential fibre line fault between third party Data Centres, IXN LON1 and Telehouse West, Cases have been raised with providers and we will provide updates as and when we receive them.

2. monitoring Feb 05, 2025, 05:00 PM UTC

   A Fix has been implemented and a cable has been patched at Telehouse west. Service has now restored. We will continue to monitor this and update if any further issues are experienced.

3. resolved Feb 06, 2025, 07:54 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 21, 2025, 11:52 AM UTC· resolved Jan 22, 2025, 12:24 PM UTC

1. identified Jan 21, 2025, 11:52 AM UTC

   Pulsant are aware of ongoing reduced management functionality for VM's within rack B06. Engineers are working to restore full service ASAP. Apologies for the inconvenience at tis time.

2. monitoring Jan 21, 2025, 03:17 PM UTC

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

3. resolved Jan 22, 2025, 12:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 12, 2025, 11:10 PM UTC· resolved Jan 14, 2025, 10:00 AM UTC

1. investigating Jan 12, 2025, 11:10 PM UTC

   We are currently experiencing issues with our telephony system and calls to the support line are not going through as expected. If required, please raise a case with us via the Pulsant Portal - https://portal.pulsant.com/ Alternatively raise a case with us via the Pulsant support email address - [email protected] We apologise for any inconvenience and will provide updates in due course.

2. monitoring Jan 13, 2025, 10:31 AM UTC

   Telephony issues now resolved. We will continue to monitor this and provide updates if issues re-occur.

3. resolved Jan 14, 2025, 10:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 09, 2025, 09:20 AM UTC· resolved Jan 10, 2025, 07:40 AM UTC

1. identified Jan 09, 2025, 09:20 AM UTC

   Pulsant is aware that following 3rd party planned maintenance , at present there is a loss of resilience on a link within the Slough area. Pulsant will update progress to restore full resilience as quickly as possible.

2. resolved Jan 10, 2025, 07:40 AM UTC

   The 3rd party vendor has confirmed restoration of full resilience to services by the resplicing of the fractured fibre and are now seeing bi-directional traffic

Read the full incident report →

Started Jan 08, 2025, 10:13 AM UTC· resolved Jan 09, 2025, 09:12 AM UTC

1. investigating Jan 08, 2025, 10:13 AM UTC

   Pulsant engineers have identified an possible upstream switch failure, resulting in loss of resilience. Investigations are ongoing to restore full resilience as quickly as possible.

2. monitoring Jan 08, 2025, 12:02 PM UTC

   Full resilience has been restored and being monitored closely. Pulsant engineers investigating to understand root cause.

3. resolved Jan 09, 2025, 09:12 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 24, 2024, 01:23 PM UTC· resolved Dec 24, 2024, 02:52 PM UTC

1. identified Dec 24, 2024, 01:23 PM UTC

   Network Operations Engineers have identified a Firewall fault within SE1 Milton Keynes Data Centre and are working to resolve. Currently there should be no client impact, please contact Pulsant support if you suspect otherwise. Updates will be provided in due course.

2. resolved Dec 24, 2024, 02:52 PM UTC

   Network Operations Engineers have successfully replaced a device within SE-1 Data Centre and full resiliency has been restored.

Read the full incident report →

Started Dec 16, 2024, 05:02 PM UTC· resolved Dec 18, 2024, 09:09 AM UTC

1. investigating Dec 16, 2024, 05:02 PM UTC

   We are currently experiencing an issue with our ticket logging system wherein emails are not creating cases or updating cases as expected. If you require assistance urgently, please contact Pulsant Support on 0345 119 9999 or via the Pulsant Portal - https://portal.pulsant.com/ We apologise for the inconvenience this may be causing you. Updates will be provided as soon as possible.

2. monitoring Dec 16, 2024, 07:06 PM UTC

   These issues have now been resolved and any delayed cases are being worked through urgently. We will continue to monitor and provide updates when required.

3. investigating Dec 17, 2024, 09:16 AM UTC

   Pulsant are still experiencing issues with cases being created/updated when sent via Email. We urge all clients to raise cases via the Pulsant portal or by contacting Pulsant support. Portal - https://portal.pulsant.com/ Contact - 0345 119 9999 We apologise for the inconvenience and will provide updates as soon as possible.

4. resolved Dec 18, 2024, 09:09 AM UTC

   This incident has now been resolved.

Read the full incident report →

Started Dec 09, 2024, 10:48 PM UTC· resolved Dec 10, 2024, 10:45 AM UTC

1. identified Dec 09, 2024, 10:48 PM UTC

   Following scheduled maintenance - SOFTWARE LIFECYCLE | core.ld5 software upgrade - 09-DEC-2024 2000-2300hrs Please be advised that the following maintenance window is being extended due to an unexpected outage caused by a software bug. A workaround is in place, however, to ensure stability further emergency work is necessary. Start: 09/12/2024 20:00 GMT End: 10/12/2024 03:00 GMT

2. monitoring Dec 10, 2024, 01:18 AM UTC

   Please be advised that the following maintenance is now complete. Please accept our sincere apologies for any inconvenience caused. If you have any questions, please raise a ticket by emailing [email protected] or by calling our support team directly.

3. resolved Dec 10, 2024, 10:45 AM UTC

   After close monitoring, Pulsant are confident that services have remained stable and resolving the incident. Thank you for your continued patience.

Read the full incident report →

Started Dec 04, 2024, 04:24 AM UTC· resolved Dec 05, 2024, 01:39 PM UTC

1. investigating Dec 04, 2024, 04:24 AM UTC

   Pulsant are aware of ongoing intermittent connection issues to some services connected to a Pulsant core device in LD5. Troubleshooting is ongoing to stabilise services as quickly as possible.

2. investigating Dec 04, 2024, 05:22 AM UTC

   Engineers are currently working to isolate the fault the by shutting down LINX and a transit provider to try stablise the connection. Please be aware this means a current loss of resilience for the service during this time, whilst engineers continue to apply a fix.

3. identified Dec 04, 2024, 05:57 AM UTC

   Pulsant are confident the flapping connection has stabilise with isolating some routes. Close monitoring will continue until full resiliency is restored.

4. monitoring Dec 04, 2024, 08:55 AM UTC

   A workaround has been implemented and Pulsant continue to monitor closely until fix can be applied

5. resolved Dec 05, 2024, 01:39 PM UTC

   Full resiliency has been restored as of 1600hrs on December 4th, 2024. Pulsant engineers shut down a LINX connection and reviewed/modified BGP configuration.

Read the full incident report →

Started Nov 23, 2024, 06:58 PM UTC· resolved Nov 26, 2024, 09:56 AM UTC

1. identified Nov 23, 2024, 06:58 PM UTC

   Pulsant have identified a monitoring incident that is currently being investigated. It is not believed to be client affecting, However if you are experiencing any difficulties please raise a support case or call on Pulsant support on 0345 119 9900

2. monitoring Nov 24, 2024, 07:35 PM UTC

   The monitoring incident has now been resolved. Pulsant will continue to monitor for 24 hours. If you are experiencing any difficulties please raise a support case or call on Pulsant support on 0345 119 9900.

3. resolved Nov 26, 2024, 09:56 AM UTC

   The monitoring incident has now been resolved. Pulsant will continue to monitor for 24 hours. If you are experiencing any difficulties please raise a support case or call on Pulsant support on 0345 119 9900.

Read the full incident report →

Started Nov 19, 2024, 10:06 AM UTC· resolved Jan 15, 2025, 08:56 AM UTC

1. identified Nov 19, 2024, 10:06 AM UTC

   Pulsant Cyber Security are aware of Critical Vulnerabilities impacting VMware vCenter Server and VMware Cloud Foundation. These include a heap-overflow vulnerability (CVE-2024-38812) with a CVSSv3 score of 9.8, and a privilege escalation vulnerability (CVE-2024-38813) with a CVSSv3 score of 7.5. Exploitation of these vulnerabilities has been observed in the wild. Impacted Products: VMware vCenter Server (versions 7.0, 8.0) VMware Cloud Foundation (versions 4.x, 5.x, 5.1.x) Vulnerability Details: Heap-overflow vulnerability in vCenter Server (CVE-2024-38812): Severity: Critical (CVSSv3 9.8) Description: This vulnerability in the DCERPC protocol allows remote code execution when an attacker with network access sends a specially crafted packet to vCenter Server. Resolution: Immediate application of the latest patches from the "Response Documentation" is essential. Privilege escalation vulnerability in vCenter Server (CVE-2024-38813): Severity: Important (CVSSv3 7.5) Description: This vulnerability can enable an attacker to escalate privileges to root by sending a specially crafted packet to vCenter Server. Resolution: Application of the latest patches from the "Response Documentation" is required to remediate this issue. Response Documentation : https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24968

2. resolved Jan 15, 2025, 08:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 08, 2024, 10:10 AM UTC· resolved Nov 08, 2024, 02:24 PM UTC

1. investigating Nov 08, 2024, 10:10 AM UTC

   Pulsant have been made aware of an ongoing incident impacting Citrix EU Customers ' Few EU customers could not launch apps and desktops through DaaS' For up to date information - https://status.cloud.com/incidents/651542

2. monitoring Nov 08, 2024, 10:42 AM UTC

   Citrix Status page update 'We have identified the root cause and are applying mitigations now. Some of the impacted customers should see successful DaaS launches as we they are recovering. https://status.cloud.com/incidents/651542

3. monitoring Nov 08, 2024, 11:16 AM UTC

   Current update from Citrix - Status is UP. Post mitigation most of the impacted customers are able to launch apps and desktops. We continue to monitor.

4. resolved Nov 08, 2024, 02:24 PM UTC

   This incident has been resolved.

Read the full incident report →