Scaffold Outage History

Scaffold is up right now

Pingoru has recorded 6 incidents for Scaffold: 6 in the last 12 months and 1 in the last 90 days.

Source: status.scaffold.digital

6incidents recorded
6last 12 months
1last 90 days
16 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Scaffold in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026121 of 744 (3%)
June 202639 of 720 (1%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026165 of 744 (9%)
November 202600 of 184 (0%)

Incidents, newest first

Major October 21, 2026 Critical PHP security vulnerabilities 2d 16h Customer Websites (Dedicated), Email (SSN Hotel), Databases (Production), Databases (Staging) and 3 more

Started Oct 21, 2026, 04:30 AM UTC· resolved Oct 23, 2026, 09:25 PM UTC

  1. investigating Oct 21, 2026, 04:30 AM UTC

    We are aware of a security issue affecting PHP, the language many of our clients’ applications run on. In short The PHP team is due to release a fix today, 21 October, at 15:00 UK time. We are preparing to apply it to all affected systems we manage as soon as it is available. Until then, the only way to remove the risk completely is to take an application offline temporarily. If you have any concerns, or would like us to take your application offline until it is patched, please get in touch. What has happened Yesterday (20 October) the PHP security team announced an emergency release to fix two critical vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619. Each is rated 9.2 out of 10 for severity. If exploited, they could allow an attacker to run their own code on an affected server. Overnight, details of the vulnerabilities appear to have been published online ahead of the planned fix. This means they could be exploited before the patch is available. We have no evidence either way at this stage, so we are treating the risk seriously. Mitigation No workarounds have been published so far. Until the fix is applied, taking an application offline is the only way to remove the risk completely, but it also means the service will be unavailable for that period. If a workaround becomes available, we will post an update here. Fixes are only expected for currently supported versions of PHP. If your application runs on an older version, it may need to be upgraded before the fix can be applied. We will contact any clients this affects directly. What we are doing Our team has been monitoring the situation throughout the night and is preparing to patch every affected system we manage as soon as the fix is released. We will post further updates here as the situation develops.

  2. investigating Oct 21, 2026, 04:30 AM UTC

    We are aware of a security issue affecting PHP, the language many of our clients’ applications run on. In short The PHP team is due to release a fix today, 21 October, at 15:00 UK time. We are preparing to apply it to all affected systems we manage as soon as it is available. Until then, the only way to remove the risk completely is to take an application offline temporarily. If you have any concerns, or would like us to take your application offline until it is patched, please get in touch. What has happened Yesterday (20 October) the PHP security team announced an emergency release to fix two critical vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619. Each is rated 9.2 out of 10 for severity. If exploited, they could allow an attacker to run their own code on an affected server. Overnight, details of the vulnerabilities appear to have been published online ahead of the planned fix. This means they could be exploited before the patch is available. We have no evidence either way at this stage, so we are treating the risk seriously. Mitigation No workarounds have been published so far. Until the fix is applied, taking an application offline is the only way to remove the risk completely, but it also means the service will be unavailable for that period. If a workaround becomes available, we will post an update here. Fixes are only expected for currently supported versions of PHP. If your application runs on an older version, it may need to be upgraded before the fix can be applied. We will contact any clients this affects directly. What we are doing Our team has been monitoring the situation throughout the night and is preparing to patch every affected system we manage as soon as the fix is released. We will post further updates here as the situation develops.

  3. investigating Oct 22, 2026, 03:42 PM UTC

    Over the last 24-hours our team has worked to patch sites and platforms as the updates have become available. There are still some more complex applications left to patch but most are now considered resolved.

  4. resolved Oct 23, 2026, 09:25 PM UTC

    The remedial work has been completed. Thank you for your patience!

Read the full incident report →

Major June 25, 2026 We're currently having issues 4h 7m

Started Jun 25, 2026, 06:55 AM UTC· resolved Jun 25, 2026, 11:02 AM UTC

  1. investigating Jun 25, 2026, 08:21 AM UTC

    Some people are experiencing problems with our service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

  2. investigating Jun 25, 2026, 09:28 AM UTC

    We've fixed the core issue, and are waiting for things to recover.

  3. resolved Jun 25, 2026, 11:02 AM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major June 24, 2026 We're currently having issues 4h 7m

Started Jun 24, 2026, 07:53 AM UTC· resolved Jun 24, 2026, 12:00 PM UTC

  1. investigating Jun 24, 2026, 08:10 AM UTC

    Some people are experiencing problems with our service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

  2. investigating Jun 24, 2026, 09:25 AM UTC

    We believe the issue is now resolved and sites are returning to normal. We'll continue to monitor the incident and share any additional updates if relevant.

  3. investigating Jun 24, 2026, 09:34 AM UTC

    After a brief period where sites were responding normally again we're now seeing several sites taking an abnormally long time to respond / failing to respond at all. We're continuing to investigate.

  4. investigating Jun 24, 2026, 10:02 AM UTC

    We've identified the root cause of the issue and are waiting for things to recover. At this time all sites do appear to be responding normally. As before, we'll continue to monitor for and changes and post updates if relevant.

  5. resolved Jun 25, 2026, 08:19 AM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major June 9, 2026 We're currently having issues 24m

Started Jun 09, 2026, 09:30 AM UTC· resolved Jun 09, 2026, 09:54 AM UTC

  1. investigating Jun 09, 2026, 09:30 AM UTC

    Some people are experiencing problems with our service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

  2. resolved Jun 09, 2026, 09:54 AM UTC

    This issue has been resolved and everything should be working normally now. We're continuing to monitor closely to make sure everything stays stable. Thank you so much for your patience while we worked through this.

Read the full incident report →

Major May 12, 2026 Sites Offline 20h 48m

Started May 12, 2026, 02:39 PM UTC· resolved May 13, 2026, 11:27 AM UTC

  1. investigating May 12, 2026, 03:22 PM UTC

    We're currently investigating an issue that is affecting the availability of many of our customer's websites and email services. The issue was first detected at 3:39pm BST and service has been intermittent since then. We are actively working to to restore services ASAP.

  2. investigating May 12, 2026, 09:13 PM UTC

    We've fixed the core issue, and are waiting for things to recover.

  3. resolved May 13, 2026, 11:27 AM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major November 17, 2025 We're currently having issues 19m

Started Nov 17, 2025, 09:50 AM UTC· resolved Nov 17, 2025, 10:09 AM UTC

  1. resolved Nov 17, 2025, 10:09 AM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →