Pulsant Outage History

Pulsant is up right now

Pulsant had 22 outages in the last 2 years totaling 1816h 37m of downtime — averaging 0.9 incidents per month.

There were 22 Pulsant outages since May 27, 2025 totaling 1816h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pulsant.com

Notice May 26, 2026

Ticketing System Emails

Detected by Pingoru
May 26, 2026, 10:37 AM UTC
Resolved
May 27, 2026, 09:20 AM UTC
Duration
22h 42m
Timeline · 3 updates
  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 →

Minor May 14, 2026

Zayo outage in the London area 14/05/2026

Detected by Pingoru
May 14, 2026, 08:55 AM UTC
Resolved
May 14, 2026, 11:49 AM UTC
Duration
2h 54m
Timeline · 2 updates
  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 →

Minor April 21, 2026

Virgin Media Outage Hayes-London Area

Detected by Pingoru
Apr 21, 2026, 03:06 PM UTC
Resolved
Apr 22, 2026, 06:44 AM UTC
Duration
15h 37m
Timeline · 4 updates
  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 →

Notice February 1, 2026

Virgin Media Outage

Detected by Pingoru
Feb 01, 2026, 03:04 PM UTC
Resolved
Feb 02, 2026, 11:09 AM UTC
Duration
20h 5m
Timeline · 5 updates
  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 →

Notice December 16, 2025

Wavelength outage impacting services in SE-3

Detected by Pingoru
Dec 16, 2025, 11:07 AM UTC
Resolved
Dec 16, 2025, 02:33 PM UTC
Duration
3h 25m
Affected: SE-3 - Reading South
Timeline · 3 updates
  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 →

Notice December 15, 2025

Third Party maintenance issues in Reading

Detected by Pingoru
Dec 15, 2025, 09:49 AM UTC
Resolved
Dec 15, 2025, 03:59 PM UTC
Duration
6h 9m
Timeline · 5 updates
  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 →

Minor December 14, 2025

Unplanned interruption to service at SE-3 (Reading South)

Detected by Pingoru
Dec 14, 2025, 08:55 PM UTC
Resolved
Dec 15, 2025, 08:50 AM UTC
Duration
11h 55m
Affected: SE-3 - Reading South
Timeline · 3 updates
  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 →

Notice December 9, 2025

Client Portal issues

Detected by Pingoru
Dec 09, 2025, 12:13 PM UTC
Resolved
Dec 11, 2025, 09:15 AM UTC
Duration
1d 21h
Timeline · 3 updates
  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 →

Minor December 3, 2025

Virgin Media Outage in the Croydon Area

Detected by Pingoru
Dec 03, 2025, 02:57 PM UTC
Resolved
Dec 03, 2025, 10:21 PM UTC
Duration
7h 24m
Affected: LN-1 - South London
Timeline · 3 updates
  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 →

Notice November 13, 2025

CHG0056167 - Essential Maintenance on Pulsant Client Portal and Pulsant Cloud

Detected by Pingoru
Nov 13, 2025, 05:03 PM UTC
Resolved
Nov 14, 2025, 10:04 AM UTC
Duration
17h
Timeline · 3 updates
  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 →

Major October 29, 2025

Microsoft 365 service degradation

Detected by Pingoru
Oct 29, 2025, 05:03 PM UTC
Resolved
Oct 30, 2025, 10:49 AM UTC
Duration
17h 46m
Timeline · 4 updates
  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 →

Minor October 27, 2025

Some users may experience difficulty logging into the customer portal.

Detected by Pingoru
Oct 27, 2025, 03:32 PM UTC
Resolved
Nov 03, 2025, 09:51 AM UTC
Duration
6d 18h
Timeline · 4 updates
  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 →

Notice September 9, 2025

Virgin Media Outage impacting services in Manchester and London

Detected by Pingoru
Sep 09, 2025, 01:34 PM UTC
Resolved
Sep 10, 2025, 08:57 AM UTC
Duration
19h 22m
Timeline · 4 updates
  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 →

Notice July 6, 2025

Limited access to Croydon Data Centre LN-1

Detected by Pingoru
Jul 06, 2025, 12:22 PM UTC
Resolved
Jul 06, 2025, 03:53 PM UTC
Duration
3h 31m
Affected: LN-1 - South London
Timeline · 2 updates
  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 →

Minor June 23, 2025

Wavelength outage at Reading DC

Detected by Pingoru
Jun 23, 2025, 05:06 PM UTC
Resolved
Jul 08, 2025, 09:30 AM UTC
Duration
14d 16h
Affected: SE-3 - Reading South
Timeline · 4 updates
  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 →

Notice June 20, 2025

Croydon Data Centre (LN-1) access road closed

Detected by Pingoru
Jun 20, 2025, 07:59 AM UTC
Resolved
Jul 08, 2025, 09:30 AM UTC
Duration
18d 1h
Affected: LN-1 - South London
Timeline · 3 updates
  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 →

Notice June 3, 2025

Outage Investigation

Detected by Pingoru
Jun 03, 2025, 04:16 PM UTC
Resolved
Jun 20, 2025, 07:57 AM UTC
Duration
16d 15h
Timeline · 3 updates
  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 →

Notice May 27, 2025

INC0101000 - Multiple clients have reported routing issues that are causing outages

Detected by Pingoru
May 27, 2025, 10:25 AM UTC
Resolved
Jun 03, 2025, 04:41 PM UTC
Duration
7d 6h
Timeline · 3 updates
  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 →