Microsoft capacity is increasing and emails are beginning to deliver. However there remains 16+ hours of email queues that did not deliver giving double the rate to microsoft services than normal. This introduces new challenges on delivery due to standard rate limits microsoft has in inbound email that under normal circumstances are not exceeded.
identified
Microsoft emails remain delayed.
identified
Further information from microsoft can be followed at https://x.com/MSFT365Status/status/2120938282204688468
identified
We have identified the Microsoft responses behind these delays, including “The maximum number of concurrent server connections has exceeded a limit, closing transmission channel” and “Temporary server error. Please try again later”, and added handling for them to our system.
Messages that receive these responses are now moved to a separate slow queue and retried automatically from there. This keeps them from backing up the main queue, so delivery to other destinations should no longer be held up behind Microsoft-bound mail.
Email to Microsoft-hosted recipients, including Outlook, Hotmail and Microsoft 365 domains, may continue to be delayed while the issue persists on Microsoft’s side. No mail has been lost, and no action is needed from senders. Delayed messages will be delivered as Microsoft accepts them.
investigating
Emails to Microsoft are currently delayed, with similar reports from other vendors on the Mail ops list including errors such as 'The maximum number of concurrent server connections has exceeded a limit, closing transmission channel'
The issue is widespread and causing email delays.
The restore is completed and we are monitoring the system.
identified
The openvz87 system has had a double harddrive failure. The latest full system backup is being restored to new hardware with approximatly 1 - 2 hours left.
Please be aware virtuozzo7 reaches end of life Dec 31st https://www.interserver.net/tips/kb/virtuozzo7-upcoming-end-of-life/
Exchange hosted domains are seeing increased 451 4.7.500 Server busy. Please try again later errors. There is a broader issue at exchange being tracked with incident id EX1467029. Delayed emails remain in queue to be tried later.
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating a mysql replication error and expect the portal to be restored shortly
Legacy Incident Archive
23 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
cPanel Security: Privilege Escalation via Phusion Passenger's Watchdog API
Source not attested
Last archived state: resolved
View archived record details
Webhosting
investigating
Phusion Passenger Watchdog API privilege escalation vulnerability:
https://support.cpanel.net/hc/en-us/articles/42694659893143-Security-Privilege-Escalation-via-Phusion-Passenger-s-Watchdog-API?utm_medium=email&_hsmi=433242580&utm_content=433242580&utm_source=hs_email
cPanel has released patches for the above root exploit, however cloudlinux the os vendor in use has not. Out of caution the package will be removed on systems until a patch is released.
Plesk panel loading issue plesk6300
Source not attested
Last archived state: resolved
View archived record details
identified
We are actively restoring the affected data and services. Due to severe filesystem corruption, we are experiencing delays and additional challenges during the recovery process. Our team is working continuously to recover as much data as possible and restore affected services. We will continue to provide updates as progress is made.
identified
We have identified severe filesystem corruption on the D: drive. Recovery efforts are currently in progress; however, some portions of the filesystem are beyond recovery. This is causing delays in service restoration. We are working to restore affected services as quickly as possible and will provide further updates as they become available.
identified
We have identified data corruption on plesk6300.is.cc server and we were unable to address it fully. We are working to migrate the accounts to a newly built server (Plesk10000.is.cc), the details for which will be provided in your support tickets. We appreciate your patience and understanding during this transition.
identified
The issue has been identified and we are working on this matter on priority
investigating
We are currently investigating IIS application pool crashing & Plesk panel loading issue on plesk6300.is.cc server after hardware issue occurred
July 2026
KVM520 CPU fauls
Source not attested
Last archived state: resolved
View archived record details
identified
KVM520 indicates a fault (Service Information: Runtime Fault, Processor(Intel), Processor 2. A CPU replacement will begin on this hostnode.
KVM530 Hostnode outage
majorSource not attested
Last archived state: resolved
View archived record details
investigating
KVM530 has been rebuild as kvm553. Systems with backups generating through my.interserver.net are currently restoring.
investigating
A replacement server is being built while recovery options continue to be looked into. At this time, multiple drives are reporting as failed in the zfs array after an Runtime Fault, Storage Backplanes error in the HPE chassis.
investigating
This system is still being worked on, unfortunately there is no resolution yet. The system is still showing errors moved to another chassis.
investigating
We are currently investigating a hardware issue on KVM host node kvm530. The server's out-of-band management interface (iLO) has started reporting hardware errors.
Impact:
If your virtual machine is located on kvm530, you may experience degraded performance, intermittent network drops, or unexpected reboots while the physical hardware is in this state.
What we are doing:
Our infrastructure team is actively reviewing the iLO diagnostic logs to identify the specific failing component (such as...
Scheduled maintenance for 3 Hyperv servers
Source not attested
Last archived state: resolved
View archived record details
monitoring
3 Hyperv servers are back online and we are monitoring the services
investigating
We are performing scheduled maintenance for the following servers listed below.
hyperv78.is.cc
hyperv79.is.cc
hyperv117.is.cc
During this maintenance, downtime is expected to be up to 2-3 hours per server.
Multiple cPanel Systems showing license errors
Source not attested
Last archived state: resolved
View archived record details
investigating
cPanel is aware and tracking at https://support.cpanel.net/hc/en-us/articles/41816676353943-cPanel-License-Update-Failures-July-8th-2026
However no fix is available yet.
investigating
Multiple cpanel systems are showing license errors. We have opened a case with cpanel 96038885 but have no further informations. Based on other public channels this is a widespread issue affecting cpanel.
Plesk6300 hardware issue
Source not attested
Last archived state: resolved
View archived record details
monitoring
Plesk6300 services are back online and we are monitoring the server
investigating
We are currently investigating hardware issue on plesk6300 server
Plesk4500 IIS application pool issue
Source not attested
Last archived state: resolved
View archived record details
monitoring
Plesk4500 services are online and accessible , we are monitoring the server
identified
We are working on plesk4500 server and checking crashing issues , we are trying to bring server back online soon
monitoring
Plesk4500 services are back online , we are monitoring the server
investigating
We are currently investigating IIS application pool crashing issue on plesk4500.is.cc server
Plesk6600 slowness issue
Source not attested
Last archived state: resolved
View archived record details
monitoring
Plesk6600 services are back online , we are monitoring server
identified
We have identified a hardware issue on server and we are working to fix it
investigating
Plesk6600 slowness issue is being investigated by our techs , we are checking server for possible overheating issues
Mailbaby Logging delayed
Source not attested
Last archived state: resolved
View archived record details
identified
There will be a delay in mailbaby logging in order to correct a reported error where an id may show multiple times in the mail log. Mail logging will resume once this process is done, and logging will then resume. The process may take up to one hour.
