Pulsant Outage History

Started Jul 16, 2026, 09:45 AM UTC· resolved Jul 16, 2026, 10:04 AM UTC

1. investigating Jul 16, 2026, 09:45 AM UTC

   We are aware of an issue affecting authentication when attempting to log in to the Pulsant Portal. Our Systems Engineers are currently investigating the issue and working to restore normal service. If you require support in the meantime, please contact us on 0345 119 9900.

2. resolved Jul 16, 2026, 10:04 AM UTC

   Service has been restored. Clients are now able to loign to the Pulsant Portal.

Read the full incident report →

Started Jun 26, 2026, 11:47 AM UTC· resolved Jun 26, 2026, 11:46 PM UTC

1. investigating Jun 26, 2026, 11:47 AM UTC

   We are currently experiencing availability of storage within the NE-1 (Newcastle) site as part of the Pulsant Cloud Infrastructure. This issue is impacting services that rely on the affected storage infrastructure. Our engineering team is actively investigating the incident with vendor to assist with identifying the root cause and restoring service as quickly as possible. We will provide further updates as more information becomes available.

2. monitoring Jun 26, 2026, 05:18 PM UTC

   With the situation being fully assessed, remediation action was taken to by engineer onsite. Indications are that this work has been successful and that services will restore. This will take time to recover, the situation continues to be monitored closely. For your reference, please see our service status page for updates on incidents. This can be found at http://status.pulsant.com Please accept our sincere apologies for any inconvenience this issue is causing.

3. monitoring Jun 26, 2026, 09:32 PM UTC

   Following a Major Incident on the Pulsant Cloud platform earlier today, engineers have been working to remediate the issues. While a number of clients have seen services restore, we have seen further instability for some clients around their connectivity. Pulsant engineers are engaged with the OEM suppliers and continue to work to resolve these issues for all clients.

4. resolved Jun 26, 2026, 11:46 PM UTC

   Following guidance from our OEM suppliers, Pulsant engineers have resolved additional instances of instability within the Pulsant cloud environment at NE-1 (Newcastle). Our Cloud & Storage and Connectivity teams continue to closely monitor the environment to ensure ongoing stability and will provide further updates if necessary.

Read the full incident report →

Started May 26, 2026, 10:37 AM UTC· resolved May 27, 2026, 09:20 AM UTC

1. investigating May 26, 2026, 10:37 AM 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. identified May 26, 2026, 02:54 PM UTC

   A fix has been identified and engineers are working to implement this now. Please continue to contact Pulsant Support on 0345 119 9999 or via the Pulsant Portal - https://portal.pulsant.com/ for any urgent issues. Thank you for your continued patience

3. resolved May 27, 2026, 09:20 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 14, 2026, 08:55 AM UTC· resolved May 14, 2026, 11:49 AM UTC

1. investigating May 14, 2026, 08:55 AM UTC

   Pulsant are aware of a Zayo outage within the London area, Zayo engineers are currently investigating and providing updates. If you experience any issues please do not hesitate to contact Pulsant support.

2. resolved May 14, 2026, 11:49 AM UTC

   Zayo have advised they have located and repaired the issue. They now see alarms clear and services restoring. Please can you check services have restored. If you have any further issues, please do not hesitate to contact Pulsant support

Read the full incident report →

Started Apr 21, 2026, 03:06 PM UTC· resolved Apr 22, 2026, 06:44 AM UTC

1. identified Apr 21, 2026, 03:06 PM UTC

   Pulsant is aware of a Virgin Media outage potentially affecting client circuits in the Hayes-London Area. They have advised that their engineers are currently investigating. Further updates are expected at approximately 16:30.

2. identified Apr 21, 2026, 03:44 PM UTC

   Virgin Media have dispatched an engineer to complete physical checks to the impacted location. Further updates to follow when they become available. Please contact Pulsant support if you are experiencing any service impact.

3. identified Apr 21, 2026, 07:02 PM UTC

   Virgin Media have advised Emergency change work will be undertaken to reseat/replace a line card. Clients may experience a loss of service during this work. Planned Work Start (Local UK): 22/04/2026 00:01 Planned Work End (Local UK): 22/04/2026 06:00 If you have any queries regarding this work please contact Pulsant support.

4. resolved Apr 22, 2026, 06:44 AM UTC

   Virgin Media carried out the emergency change during the scheduled window. IMM Card 1 was reseated and successfully brought back online at 00:08, remaining stable throughout the one-hour monitoring period. As no signs of instability were observed, Virgin Media determined that a card replacement was not required. Virgin Media has confirmed service restoration. Should you continue to experience issues with your Virgin Media circuit, please contact Pulsant Support for further assistance.

Read the full incident report →

Started Apr 09, 2026, 12:35 PM UTC· resolved Apr 10, 2026, 12:52 PM UTC

1. investigating Apr 09, 2026, 12:35 PM UTC

   Pulsant has been made aware of a Virgin Media Outage at Leeds Hub Site on 09/04/2026. Upon initial triage, Virgin Media are reporting a large amount of Frame Check Sequence errors incrementing on a Vodafone interconnect port. Virgin Media's Major Incident teams have been engaged, as well as core data transmission teams. An engineer en -route to the hub site to conduct physical checks. Our data team is also raising a case with Vodafone in the background. Further updates to follow

2. investigating Apr 09, 2026, 01:18 PM UTC

   Initial analysis with Virgin Media’s Technical Teams confirmed that the issues are residing on an NNI Interconnect Link on leed-metnet-2a. A VMO2 Engineer is on route to the Leeds Headend to perform testing of the link at ODF on the Metnet impacted links. An Incident has been raised with Vodafone Further Updates to Follow

3. investigating Apr 09, 2026, 02:54 PM UTC

   Virgin Media Engineers have applied a bi-directional loop at their SFP at the VM hub site and can see the errors cleared. Once the loop was removed, the errors reoccurred. This indicates an issue with the 3rd-party provider's network. Virgin Media has chased Vodafone for updates on their investigations. Virgin Media engineers will remain on-site until they hear back from Vodafone.

4. investigating Apr 09, 2026, 04:43 PM UTC

   Vodafone have confirmed they are seeing their ADVA device down at the VMO2 Leeds hub site and have requested an engineer to attend. Virgin Media have on-call engineers on site, awaiting to provide Vodafone access, and are currently awaiting an ETA. Virgin Media have also escalated this into Vodafone's Major Incident teams to ensure this is progressed with the upmost urgency. Further updates to follow

5. investigating Apr 09, 2026, 05:15 PM UTC

   Virgin Media have engaged Vodafone Major Incident Management Team, and they have escalated the issue to progress investigations on the NNI Adva Transmission Link at Leeds Headend Site. Virgin Meida have observed that even with testing on a spare SFP, Virgin Meida continue recording high frequency of errors on the Metnet Device. Virgin Meida have engaged Nokia and a spare card has been ordered as they found the erroring port is at full duplex having performed the loop testing. Awaiting ETA for part delivery to the site for the Virgin Media Engineer to proceed with the card reseat/replace as required. Virgin Media Engineer is onsite continuing the testing, checks and investigations will continue along Vodafone Engineer

6. investigating Apr 09, 2026, 06:59 PM UTC

   A Vodafone Engineer is currently on site investigating their network. A Virgin Media Engineer remains on-site and is supporting the Vodafone Engineer during this investigation. Escalations with Vodafone are ongoing to expedite service restoration, and we continue to liaise with all relevant teams to progress the resolution of this fault.

7. monitoring Apr 09, 2026, 07:32 PM UTC

   Virgin Media is now starting to see services restoring. The third-party engineer has successfully resolved the issue on their network, resulting in service restoration. Clients have been asked to re-test their services and to contact Pulsant Support if any issues persist.

8. resolved Apr 10, 2026, 12:52 PM UTC

   All services have restored and no further issues have been reported. If you experience any further issues please do not hesitate to contact Pulsant Support.

Read the full incident report →

Started Feb 01, 2026, 03:04 PM UTC· resolved Feb 02, 2026, 11:09 AM UTC

1. investigating Feb 01, 2026, 03:04 PM UTC

   Pulsant is aware of a Virgin Media outage affecting some client circuits. Investigations are ongoing with Virgin Media.

2. identified Feb 01, 2026, 04:19 PM UTC

   Virgin Media engineers have been dispatched to a local exchange to investigate the issue. Further updates to follow. Thank you for your patience whilst work continues to resolve the outage.

3. identified Feb 01, 2026, 05:56 PM UTC

   Virgin Media engineers have identified a fibre fault and are working to complete repairs Further updates to follow. Thank you for your patience whilst work continues to resolve the outage.

4. monitoring Feb 01, 2026, 09:47 PM UTC

   Virgin Media has advised a fibre break has been located and repaired. Pulsant are seeing a recovery of services and have asked impacted clients to test. Pulsant will continue to monitor.

5. resolved Feb 02, 2026, 11:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 07, 2026, 09:27 AM UTC· resolved Jan 09, 2026, 09:09 AM UTC

1. investigating Jan 07, 2026, 09:27 AM UTC

   Pulsant are aware of an issue within the Reading South DC. A Major Incident has been declared, investigations are ongoing and further updates will be provided shortly.

2. identified Jan 07, 2026, 09:57 AM UTC

   Investigations are on going, Pulsant engineers have identified an issue between Pulsant SE-3 and a Third Party DC. Further updates will follow.

3. identified Jan 07, 2026, 11:18 AM UTC

   Support cases have been raised with Third Party DC/Vendors to carry out further investigations. Further updates will be provided when Pulsant have received feedback from the investigations.

4. identified Jan 07, 2026, 01:31 PM UTC

   Pulsant are awaiting feedback from Third Party Vendors and have raised escalations to attempt to facilitate a faster response. Thank you for your patience whilst we continue to investigate

5. identified Jan 07, 2026, 03:40 PM UTC

   Pulsant's escalation with Third party Vendors has been acknowledged and the investigation is now with Third party senior engineers. Further updates will be provided when Pulsant have received feedback from the investigations. Thank you for your patience whilst we await an update.

6. identified Jan 07, 2026, 05:17 PM UTC

   Pulsant's Third Party vendors have located a fault and an engineering team has been dispatched to site to investigate. Further updates will be provided when Pulsant have received feedback from the investigations.

7. identified Jan 07, 2026, 09:53 PM UTC

   Pulsant's Third Party investigation is still ongoing. Further updates will be provided when Pulsant have received feedback from the investigations. Thank you for your patience whilst we await an update.

8. identified Jan 08, 2026, 09:24 AM UTC

   Pulsant's Third Party investigation into a fibre fault located close to the datacentre is ongoing. Further updates will be provided when Pulsant have received feedback from the investigations. Thank you for your patience whilst we await an update.

9. identified Jan 08, 2026, 12:25 PM UTC

   Pulsant continue to chase and escalate to Third Party Vendors for updates. Apologies for any inconvenience caused and thank you for your patience whilst we continue to follow up with Third Parties

10. identified Jan 08, 2026, 01:33 PM UTC

    Third Party vendors have advised their field engineers are on site and actively working to resolve the fault. Pulsant Senior leadership continue to escalate and engage with Third party seniors to ensure the urgency of this issue is understood. Apologies for any inconvenience caused and thank you for your continued patience whilst this issue is escalated and resolved.

11. monitoring Jan 08, 2026, 03:41 PM UTC

    Pulsant's Third Party have confirmed the issue to be resolved. However Pulsant will continue to monitor services for the rest of today, to ensure a stable service. Thank you again for your continued patience and understanding whilst this issue was resolved. Please contact Pulsant support if you experience any further issues

12. resolved Jan 09, 2026, 09:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Dec 16, 2025, 11:07 AM UTC· resolved Dec 16, 2025, 02:33 PM UTC

1. investigating Dec 16, 2025, 11:07 AM UTC

   Pulsant is aware of an outage to our wavelength services in SE-3. Investigation is ongoing to determine the technical cause. Please contact Pulsant support if you are experiencing issues.

2. monitoring Dec 16, 2025, 11:28 AM UTC

   Pulsant have located the source of the outage and steps have been taken to restore the wavelength services in SE-3. Pulsant are monitoring to ensure stability of services.

3. resolved Dec 16, 2025, 02:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 15, 2025, 09:49 AM UTC· resolved Dec 15, 2025, 03:59 PM UTC

1. identified Dec 15, 2025, 09:49 AM UTC

   Pulsant are aware of an issue caused by Third Party maintenance in Reading UK. Third Party engineers are en route and a further update is expected at approximately 10am.

2. identified Dec 15, 2025, 11:09 AM UTC

   Third Party engineers are onsite and investigating the outage. A further update is expected at approximately 12pm

3. identified Dec 15, 2025, 12:11 PM UTC

   Third Party engineers are on site and working to resolve the issue

4. monitoring Dec 15, 2025, 02:16 PM UTC

   The third party have resolved the issues being seen by resplicing cables on the circuit. Pulsant will continue to monitor services. If you experience any further issues, please contact Pulsant support.

5. resolved Dec 15, 2025, 03:59 PM UTC

   Pulsant have continued to monitor services and no further issues have been observed. Please contact Pulsant support if you experience any further issues.

Read the full incident report →

Started Dec 14, 2025, 08:55 PM UTC· resolved Dec 15, 2025, 08:50 AM UTC

1. investigating Dec 14, 2025, 08:55 PM UTC

   We are currently investigating an unplanned interruption of services at our SE-3 Data Centre. Updates will be provided periodically to address progress. Please contact Pulsant support if you are experiencing issues.

2. monitoring Dec 14, 2025, 10:39 PM UTC

   Pulsant are now observing services in SE-3 to have stabilised. Services will continue to be monitored. Please contact Pulsant support if you are experiencing issues.

3. resolved Dec 15, 2025, 08:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 09, 2025, 12:13 PM UTC· resolved Dec 11, 2025, 09:15 AM UTC

1. investigating Dec 09, 2025, 12:13 PM UTC

   Pulsant are aware of issues with the Client portal not loading, engineers are currently investigating. Please contact Pulsant support via 0345 119 9900 for any urgent issues

2. monitoring Dec 09, 2025, 03:23 PM UTC

   Pulsant have implemented a fix, the Client portal is functioning normally. We will continue to monitor these services to ensure continuity and stability. Please reach out to Pulsant Support if you continue to experience any issues.

3. resolved Dec 11, 2025, 09:15 AM UTC

   The Client Portal is fully operational and no further issues have been observed after a monitoring period.

Read the full incident report →

Started Dec 03, 2025, 02:57 PM UTC· resolved Dec 03, 2025, 10:21 PM UTC

1. investigating Dec 03, 2025, 02:57 PM UTC

   Pulsant are aware of a Virgin Media outage in the Croydon area causing a loss of service to clients. Virgin Media are conducting checks with in the area and Pulsant are expecting updates soon.

2. monitoring Dec 03, 2025, 03:32 PM UTC

   Pulsant are now seeing a recovery of client services in the Croydon area. Pulsant will follow up with Virgin Media and will continue to monitor. If you are still seeing an impact please contact Pulsant Support.

3. resolved Dec 03, 2025, 10:21 PM UTC

   The service has remained stable since 16:00

Read the full incident report →

Started Nov 18, 2025, 12:19 PM UTC· resolved Nov 19, 2025, 07:09 AM UTC

1. investigating Nov 18, 2025, 12:19 PM UTC

   Cloudflare is aware and investigating an issue that impacts multiple customers: Widespread 500 errors, Cloudflare Dashboard and API are also failing. Cloudflare is working to understand the full impact and mitigate this problem. Portals utilised by Pulsant for Virtual Machine Management may be inaccessible, but VMs will be unaffected. More updates to follow as information becomes available.

2. investigating Nov 18, 2025, 12:26 PM UTC

   Cloudflare are seeing services recover, but advises customers may continue to observe higher-than-normal error rates as we continue remediation efforts.

3. monitoring Nov 18, 2025, 12:38 PM UTC

   Cloudflare are seeing services recover, but advises customers may continue to observe higher-than-normal error rates as we continue remediation efforts.

4. investigating Nov 18, 2025, 01:07 PM UTC

   Latest Update from Cloudflare: "During our attempts to remediate, we have disabled WARP access in London. Users in London trying to access the Internet via WARP will see a failure to connect."

5. investigating Nov 18, 2025, 01:15 PM UTC

   Latest Update from Cloudflare: "We have made changes that have allowed Cloudflare Access and WARP to recover. Error levels for Access and WARP users have returned to pre-incident rates. We have re-enabled WARP access in London. We are continuing to work towards restoring other services."

6. investigating Nov 18, 2025, 01:55 PM UTC

   Cloudflare are continuing efforts to restore service for application services customers.

7. investigating Nov 18, 2025, 02:37 PM UTC

   Cloudflare have deployed a change which has restored dashboard services. Cloudflare are still working to remediate the broad application services' impact

8. monitoring Nov 18, 2025, 02:50 PM UTC

   A fix has been implemented, and Cloudflare believes the incident is now resolved. Cloudflare is continuing to monitor for errors to ensure all services are back to normal.

9. monitoring Nov 18, 2025, 03:07 PM UTC

   Latest Update from Cloudflare: "Some customers may be still experiencing issues logging into or using the Cloudflare dashboard. We are working on a fix to resolve this, and continuing to monitor for any further issues." Pulsant Cloud Management Portal remains accessible.

10. monitoring Nov 18, 2025, 05:25 PM UTC

    Latest Update from Cloudflare "We continue to monitor the system through recovery and we are seeing errors and latency return to normal levels. A full post-incident investigation and details about the incident will be made available asap." Pulsant Cloud Management Portal remains accessible. Next Pulsant update will be upon Cloudflare's resolution.

11. resolved Nov 19, 2025, 07:09 AM UTC

    This incident has been resolved by Cloudflare

Read the full incident report →

Started Nov 13, 2025, 05:03 PM UTC· resolved Nov 14, 2025, 10:04 AM UTC

1. identified Nov 13, 2025, 05:03 PM UTC

   Pulsant Cloud and Client Portal may be inaccessible between 08:30 am and 09:00 am on 14th November due to essential maintenance. Please contact Pulsant Support via 0345 119 9900 for any issues We apologise for any inconvenience caused.

2. monitoring Nov 14, 2025, 08:57 AM UTC

   The maintenance for the Pulsant Client Portal and Pulsant Cloud has been successfully completed. Please contact Pulsant Support via 0345 119 9900 for any issues.

3. resolved Nov 14, 2025, 10:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 03, 2025, 10:11 PM UTC· resolved Nov 04, 2025, 03:05 PM UTC

1. identified Nov 03, 2025, 10:11 PM UTC

   Zayo update as of 22:00 We have engaged our provider who have confirmed there is an impact to a 96F cable section in Edinburgh. Their fibre teams are onsite investigating. We are pending feedback from our providers onsite teams currently.

2. identified Nov 03, 2025, 10:56 PM UTC

   Zayo update as of 22:45 Please see feedback from our provider below: The Major Incident Team have identified the cause of the incident as fibre strike and are currently working to restore the services. The ERS engineers are currently onsite to repair the fibre. The Major Incident Team are closely monitoring the situation to ensure the issue is fully resolved. Next update to follow by 23:45

3. identified Nov 04, 2025, 12:00 AM UTC

   Zayo update as of 23:31 Please see feedback from our provider below: The Major Incident Team has identified the root cause of the incident as a fibre break, resulting from a high voltage power issue that caused the cables to melt. Due to the extent of the damage, engineers are required to remove the existing cable and install a new one. The estimated time for full service restoration is approximately 8 hours; however, some services are expected to restore prior to the completion of the works. The Major Incident Team is closely monitoring the situation to ensure the issue is fully resolved. Next update to follow by 03:45

4. identified Nov 04, 2025, 04:01 AM UTC

   Zayo Network Outage Impacting Circuits in Edinburgh - Zayo update as of 03:31 Please see feedback from our provider below: Engineers are currently onsite and have removed the damaged cable, replacing it with a new one. Splicing works are now underway. NOC has observed that services have begun to restore; however, full restoration is still expected by approximately 07:00. We are seeing managed services back online, please retest your services. Next update to follow by 07:45

5. identified Nov 04, 2025, 07:33 AM UTC

   Zayo update as of 06:33 Engineers remain onsite and are continuing with the splicing works. NOC has confirmed that the majority of services have now been restored. However, due to some delays encountered in the field, full restoration is now expected by approximately 07:30. We are seeing services back online and will update you once our providers teams are hands off. Next update to follow by 08:15

6. identified Nov 04, 2025, 08:52 AM UTC

   Zayo update as of 08:31 We are still waiting for confirmation that all engineers on site are now hands off. We should get an update before 09:30

7. monitoring Nov 04, 2025, 09:58 AM UTC

   Zayo have confirmed services should now be restored. Pulsant will continue to monitor the situation and any further updates will be provided. If you experience any further issues please do not hesitate to contact Pulsant support.

8. resolved Nov 04, 2025, 03:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 05:03 PM UTC· resolved Oct 30, 2025, 10:49 AM UTC

1. investigating Oct 29, 2025, 05:03 PM UTC

   We are aware of issues currently affecting Microsoft's global services, which may be impacting Outlook and other Microsoft Services. Clients who need support should use the client portal or contact the service desk by phone on: 0345 119 9900

2. investigating Oct 29, 2025, 05:03 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 29, 2025, 07:18 PM UTC

   Microsoft are deploying a previous healthy configuration to the affected portions of infrastructure to resolve this issue. This is being done in tandem with efforts to rebalance traffic across healthy infrastructure to achieve recovery as quickly as possible. This outage was caused by a problematic configuration change that was applied to a portion of Azure infrastructure by Microsoft. Pulsant will continue to monitor as we see service restoration.

4. resolved Oct 30, 2025, 10:49 AM UTC

   All Microsoft 365 Services have been restored and are fully operational.

Read the full incident report →

Started Oct 27, 2025, 03:32 PM UTC· resolved Nov 03, 2025, 09:51 AM UTC

1. investigating Oct 27, 2025, 03:32 PM UTC

   We are aware of an issue affecting access to the customer portal, where some users may be unable to log in. Our technical teams are actively investigating the root cause and working to restore normal service as soon as possible. Current Workaround: If your initial login attempt is unsuccessful, please refresh and try again. This has proven successful in allowing logins. If the issue persists, please get in touch with our support team for assistance. We appreciate your patience and understanding while we work to resolve this issue.

2. investigating Oct 27, 2025, 04:15 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 28, 2025, 09:44 AM UTC

   A workaround has been implemented to enable customer access to the portal and we are currently monitoring. If you are still encountering issues please contact our support team for assistance.

4. resolved Nov 03, 2025, 09:51 AM UTC

   Issues affecting access to the Customer Portal have now been resolved. If you experience any further issues, please reach out to the Pulsant Service Support Team for assistance.

Read the full incident report →

Started Sep 09, 2025, 01:34 PM UTC· resolved Sep 10, 2025, 08:57 AM UTC

1. investigating Sep 09, 2025, 01:34 PM UTC

   Pulsant are aware of an ongoing Virgin Media outage in Manchester and London affecting leased lines. Pulsant is in contact with Virgin Media and will update ASAP. If you believe you are impacted, please contact Pulsant Support.

2. identified Sep 09, 2025, 02:13 PM UTC

   Virgin Media has identified a routing issue affecting a specific backbone device. Virgin Media has confirmed no further drops for the last 30 minutes. Virgin Media is currently in bridge calls to establish the root cause so they can mitigate any potential further service disruption.

3. monitoring Sep 09, 2025, 03:44 PM UTC

   Virgin Media has mitigated service impact by implementing a fix as of 14:50, services are up with no further impact seen. Root Cause investigation is ongoing.

4. resolved Sep 10, 2025, 08:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 06, 2025, 12:22 PM UTC· resolved Jul 06, 2025, 03:53 PM UTC

1. monitoring Jul 06, 2025, 12:22 PM UTC

   Currently the access road to Croydon Data centre LN-1 is closed due a skip plant fire just down the road. No data centre services are affected. Public access is still available on foot via the green field to the side of the data centre, but main on road parking is very congested.

2. resolved Jul 06, 2025, 03:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 23, 2025, 05:06 PM UTC· resolved Jul 08, 2025, 09:30 AM UTC

1. investigating Jun 23, 2025, 05:06 PM UTC

   Pulsant are currently investigating an infrastructure outage which we believe is centred around wavelengths in Pulsant's Reading DC SE-3. If you are currently experiencing any impact please contact Pulsant Support.

2. identified Jun 23, 2025, 11:43 PM UTC

   Pulsant engineers have identified a faulty fibre device in our SE-3 data centre. We are actively exploring replacement options to restore full service. At this time, the issue is believed to be causing a loss of resilience. If you believe your services are being directly impacted beyond this loss of resilience, please contact Pulsant Support.

3. identified Jun 24, 2025, 04:51 PM UTC

   Pulsant is investigating the recent network resilience issue at data centre SE-3. The affected link is currently up but remains unstable. We’re working with our upstream provider to resolve this as quickly as possible and will share updates as they become available. We continue to monitor the link closely until full stability is confirmed.

4. resolved Jul 08, 2025, 09:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 20, 2025, 07:59 AM UTC· resolved Jul 08, 2025, 09:30 AM UTC

1. identified Jun 20, 2025, 07:59 AM UTC

   Please be advised that the public highway Imperial Way, which leads to Croydon Data Centre (LN-1) has been closed until further notices, meaning no vehicle access to the data centre. Pulsant will keep everyone advised when the road is re-opened. We thank you for your understanding and patience during this time. Please contact the support team to provide further assistance.

2. identified Jun 21, 2025, 01:29 PM UTC

   Please be advised that the public highway Imperial Way, which leads to Croydon Data Centre (LN-1) has now reopened and traffic can pass as normal. The normal authorised access to the Data Centre has been resumed. We thank you for your patience and understanding during this time.

3. resolved Jul 08, 2025, 09:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 03, 2025, 04:16 PM UTC· resolved Jun 20, 2025, 07:57 AM UTC

1. investigating Jun 03, 2025, 04:16 PM UTC

   Pulsant are currently aware of a service outage. Our Network Infrastructure team is currently investigating the issue.

2. monitoring Jun 03, 2025, 04:40 PM UTC

   Pulsant Infrastructure engineers have located a change that has now been rolled back. Pulsant are now seeing recovery alerts. If you are still experiencing any impact please contact Pulsant support.

3. resolved Jun 20, 2025, 07:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 27, 2025, 10:25 AM UTC· resolved Jun 03, 2025, 04:41 PM UTC

1. investigating May 27, 2025, 10:25 AM UTC

   Pulsant are currently investigating a routing issue that is affecting multiple clients. It is currently believed to be caused by an upstream provider. If you believe you are affected by this outage please contact Pulsant support(0345 119 9900).

2. monitoring May 27, 2025, 12:20 PM UTC

   Pulsant have implemented a workaround by updating our routing to bypass the upstream provider. Investigation is ongoing with our upstream provider. If you are still encountering issues please contact Pulsant support.

3. resolved Jun 03, 2025, 04:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 04, 2025, 12:15 PM UTC· resolved Apr 15, 2025, 08:15 AM UTC

1. investigating Apr 04, 2025, 12:15 PM UTC

   We are currently investigating an issue with DRaaS at Edinburgh SC-1. Updates will be provided periodically while a fix is implemented.

2. monitoring Apr 04, 2025, 03:21 PM UTC

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

3. monitoring Apr 04, 2025, 03:21 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Apr 15, 2025, 08:15 AM UTC

   This incident has been resolved.

Read the full incident report →