Stay updated with ongoing incidents by following this page.
22nd October 2026: PHP security issue: an update on Juniper services
You may have seen the recent BBC coverage of a global security issue involving PHP, software used by many websites and online services. We understand that you may have questions about what this means for your school. Our technical teams are responding to the issue across Juniper services, putting protections in place and applying security updates.
What is PHP, and what has happened?
PHP is software that helps websites and online applications run. A critical security issue has been identified that could allow attackers to gain unauthorised access to systems using it. Security updates have been released to address the issue.
How does this affect Juniper products?
A number of Juniper products use PHP. Our technical teams have identified the applications that use it and are checking those services and carrying out the necessary security work.
What is Juniper doing?
We have applied additional protections to all our production workloads. In most cases this means the underlying vulnerability has been patched; this is the case for all school websites, assessment trackers, analytics, estates, risk management and MIS customers. In a minority of cases we have taken systems offline until a patch can be applied, or we have implemented mitigations (WAF).
Do I need to do anything?
You do not need to make any changes to your Juniper services at this time. Our technical teams are managing the necessary work. If that advice changes for any service, we will contact the relevant customers directly with clear instructions.
23rd October 2026 at 14:20 - RESOLVED
Our technical leadership has confirmed that the necessary work to address the identified risks has been completed. Checks and monitoring are continuing. For more information, see Juniper Education Services and the Global PHP Security Issue.
RESOLVED
24th September: 10:00- Slow responses and 504 timeout errors
We are aware of an issue whereby the MIS system is currently running significantly slower than usual. As a result, some users may experience 502 and 504 timeout errors when navigating the system.
Our Development Team are actively investigating the issue and working to implement a resolution as quickly as possible.
We apologise for any inconvenience this may cause and appreciate your patience while we work to restore normal service.
Further updates will be provided here as soon as they become available.
24th September: 12:15 - Resolved
Our development team have released a fix and this issue has now been resolved.
RESOLVED
1st September 2026, 10:00: Log on Issue
We are aware that some users are encountering an error when trying to log into this product. Our development team are investigating this as a high priority and we will provide further updates when we have them.
1st September 2026, 12:00:
Our development team are continuing to investigate the issue and are working towards a resolution. Thank you for your continued patience.
1st September 2026, 15:45: Resolved
A fix has now been implemented to address the following issue: unable to access system via the JoinUp portal. Seeing a 'Bad Gateway', 'Error 500' error or system timing out on log-in attempt.
Customers should now be able to successfully log in to the JoinUp portal.
Thank you for your patience whilst our engineers have been working to deploy a fix for these access issues. We apologise for the disruption caused.
RESOLVED
23rd June 2026: 12:00 - Juniper Wonde Connection
We are aware that some schools have received a communication from Wonde, indicating that the connection isn't working as expected. We are aware of what has triggered this communication and are working with Wonde to resolve the situation.
We will provide further updates here when we have them.
ONGOING
22nd May 2026 - Census: Table 12 incorrect exclusions count
We are aware of a count issue within Table 12 of the Summary Report, where exclusions are incorrectly being counted as SEN. Our development team are investigating the issue and working on a resolution. We anticipate a fix will be implemented early next week.
26th May 2026: 16:00 - Resolved
Our development team have released a fix and this issue has now been resolved. Exclusions are no longer being incorrectly counted as SEN in Table 12 of the Summary Report.
RESOLVED
Updated