All Systems Operational

About This Site

Interserver Status Page

my Operational
Management Portal Operational
Datacenters Operational
TEB2 Operational
TEB4 Operational
TEB5 Operational
TEB6 Operational
Equinix NY4 Operational
Equinix LAX1 Operational
LAX2 Operational
TEB7 Operational
Network Operational
Network Operational
Services Operational
Webhosting Operational
Storage Operational
VPS Operational
Mailbaby Operational
Scrub Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

KVM345 Hostnode Upgrade to Ubuntu 24 LTS Apr 15, 2026 15:00-16:00 EDT

Upgrade Path: Ubuntu 22.04 LTS → Ubuntu 24.04 LTS
Summary of Work

To ensure the continued security and performance of our virtualization infrastructure, we are upgrading the KVM345 hostnode to the latest Long Term Support (LTS) version. This maintenance brings critical updates to the Linux Kernel (5.15→6.8), QEMU, and Libvirt, providing better memory management and system stability.
Impact on Virtual Machines

During this maintenance window, the hostnode will require a full system reboot to initialize the new kernel and virtualization stack.

State Saving: Before the final restart, we will attempt to "Save to Disk" (Suspend) all running Virtual Machines. This captures the current RAM state so the VM does not have to perform a cold boot.

Resuming: Once the hostnode is back online, we will automatically attempt to resume all saved VMs.

Potential Downtime: Clients should expect a temporary loss of connectivity for the duration of the host reboot (approximately 10–15 minutes).

Expected Timeline

Preparation: Final backups of host configurations in progress today. This will not affect any systems.

OS Upgrade: In-place upgrade of system packages started tomorrow.

Final Reboot: VMs are saved, the host restarts, and VMs are resumed.

The total time for the upgrade is expected to take 1 hour, the shutdown, resume and reboot time is expected to take less than 15 minutes.

Posted on Apr 14, 2026 - 14:19 EDT
Apr 15, 2026

No incidents reported today.

Apr 14, 2026
Completed - The scheduled maintenance has been completed.
Apr 14, 13:00 EDT
Verifying - All systems are using the new batched logging. An issue causing the subject to show in logs late has been addressed. We are currently verifying all changes at this time.
Apr 13, 16:58 EDT
Update - Approx 70% of systems are now running the batched logging and updates continue to be staged to be seemless. The remaining logs that show as new with delivery info when checked are expected to be completely resolved once all systems use the batched logging. Since the process has started email queue times and delivery have continued to speed up.
Apr 11, 20:04 EDT
Update - The batched logging is still being pushed out. There are some instances where view_mail_log shows 'new' but viewing the message shows properly delivered. This is currently being investigated.
Apr 8, 17:30 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 7, 13:00 EDT
Scheduled - Over the course of the next 7 days, smtp systems will begin moved to a new batched logging processing. This process will first log to an in memory database, then batch the logs to the SQL Cluster log system in bulk, making the process much more efficient.
Apr 7, 12:34 EDT
Apr 13, 2026
Apr 12, 2026

No incidents reported.

Apr 11, 2026
Apr 10, 2026
Completed - The scheduled maintenance has been completed.
Apr 10, 12:07 EDT
Scheduled - The Storage-kvm2000 system will have a replacement for the OS drives used for the system. This drive is in software RAID 1. While it does not affect user data, which is on a ZFS pool, the replacement does require downtime.
Apr 10, 11:36 EDT
Apr 9, 2026

No incidents reported.

Apr 8, 2026
Apr 7, 2026
Apr 6, 2026
Completed - The scheduled maintenance has been completed.
Apr 6, 17:56 EDT
Update - * Final checks are running on the system. The queue has been delivering during this process
* These changes will allow in the future a new logging technique which will use a batch processing, rather than per email. The smtp relays will no longer directly use the sql cluster, and instead will write to a temporary in memory db. This will then approx each minute write logs to the sql cluster.

Apr 6, 17:36 EDT
Verifying - view mail log is beginning to show new logs, however the maintenance remains ongoing.
Apr 6, 17:09 EDT
Update - The maintenance is still in progress. Email queues continue to deliver during this time as expected.
Apr 6, 16:41 EDT
Update - This maintenance will be extended due to the cluster sync on a new node taking longer than expected.
Apr 6, 15:52 EDT
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Apr 6, 15:02 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 6, 15:00 EDT
Scheduled - The sql cluster will undergoing maintenance for mailbaby logging in order to improve performance. During this

* some logs will not show on the main view log page
* checking the email id will show the appropriate logs
* delivery will not be affected during this time

Apr 6, 14:00 EDT
Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026
Resolved - This issue has been resolved
Apr 3, 19:42 EDT
Monitoring - A fix has been applied , all plesk4700 services are back online , we are monitoring the server
Apr 3, 07:58 EDT
Identified - The issue has been identified and fix applied ,all services are back online
Apr 3, 07:57 EDT
Update - The issue has been identified and fix applied ,all services are back online
Apr 3, 07:56 EDT
Investigating - We are currently investigating IIS config issue on plesk4700 , we are working on it
Apr 3, 07:04 EDT
Apr 2, 2026

No incidents reported.

Apr 1, 2026

No incidents reported.