https://status.8dweb.com/2026-10-21T22:34:18Zhttps://status.8dweb.com/incidents/104.html2026-03-18T19:13:31Z2026-03-18T17:56:04Z<p><b>Resolved</b> (2026-03-18T19:13:31Z): WEB06 was hung at boot prompt... Matter resolved by onsite.</p><p><b>Investigating</b> (2026-03-18T17:56:04Z): After a critical OS update, WEB06 has failed to reboot properly. Technician is being dispatched to Data Center.</p>https://status.8dweb.com/incidents/103.html2025-11-22T22:17:04Z2025-11-18T15:15:32Z<p><b>Resolved</b> (2025-11-22T22:17:04Z): :)</p><p><b>Identified</b> (2025-11-18T15:15:32Z): Cloudflare has been experiencing issues this morning. These are not related to 8Dweb, however, some servers and customers utilize Cloudfare. This will cause various connectivity problems. https://www.cnbc.com/2025/11/18/cloudflare-down-outage-traffic-spike-x-chatgpt.html</p>https://status.8dweb.com/incidents/102.html2025-08-09T04:43:05Z2025-08-09T04:32:34Z<p><b>Resolved</b> (2025-08-09T04:43:05Z): Issue with Litespeed hung process has been resolved.</p><p><b>Investigating</b> (2025-08-09T04:32:34Z): We are currently investigating WEB06 issue with lite speed - we will apprise once we have resolved</p>https://status.8dweb.com/incidents/101.html2025-07-28T18:17:03Z2025-07-27T18:34:54Z<p><b>Resolved</b> (2025-07-28T18:17:03Z): All known sites are now restored.</p><p><b>Monitoring</b> (2025-07-28T15:33:23Z): Nearly all websites have been restored. Some things such as Redis or Litespeed caching plugins may be missing, however, those are minor issues and can be rectified (if required) at a future time. There are several sites (currently 6) that were affected by a further issue where DNS records were not contained in the Enhance backups. This matter is being investigated by the Enhance team, and those sites remain OFFLINE at this moment.</p><p><b>Identified</b> (2025-07-28T11:57:16Z): Site restoration continues. In each case Enhance backups have come to the rescue, however, the full disaster recovery provided for downed servers in Enhance did not work as expected. Please do not open tickets for down sites at this juncture, we are aware of all sites that are currently still not working properly, and are methodically working through the process.</p><p><b>Identified</b> (2025-07-28T10:39:42Z): Sites are being restored. At this juncture there is a manual step in the disaster recovery where our team needs to touch each web site. We have notified and been working directly with Enhance support about that particular issue. Sites will come online in a strictly alphabetical order.</p><p><b>Identified</b> (2025-07-28T02:04:55Z): Restorations are under way, however, database restorations are not properly working. We are working with the Enhance team to pin this DR issue down.</p><p><b>Identified</b> (2025-07-28T00:46:49Z): web05 has been rebuilt. web06 has been rebuilt Restoration of sites will begin via disaster recover process at approximately 9:00pm Eastern. This will not guarantee any specific site will be online shortly thereafter. The process is expected to take some time, so there will be no ETA until restoration is complete and our team begins going through sites to verify them online, or not.</p><p><b>Investigating</b> (2025-07-27T18:34:54Z): There has been an unknown failure on our WEB05 server. There is no ETA on resolution.</p>https://status.8dweb.com/incidents/100.html2025-05-06T14:15:21Z2025-05-06T13:06:36Z<p><b>Resolved</b> (2025-05-06T14:15:21Z): Updates are finalized on all servers.</p><p><b>Investigating</b> (2025-05-06T13:06:36Z): Our team is currently addressing some ssh vulnerability updates. You may see services flicker for several minutes on web servers.</p>https://status.8dweb.com/incidents/99.html2025-03-20T10:52:35Z2025-03-19T20:41:18Z<p><b>Resolved</b> (2025-03-20T10:52:35Z): DataCenters has successfully identified the source of this attack and implemented mitigations as of 6:15 PM. All services should be restored to normal operation. If you are still experiencing any network degradation, please let us know.</p><p><b>Investigating</b> (2025-03-19T21:13:15Z): DataCenters Network Outage Notification Update from 03/19/2025 05:06:58 PM EDT The root cause of this incident is thought to be related to an ongoing DDoS attack. We are attempting to pinpoint the source/destination and mitigate this attack to restore services, and will provide additional updates as they become available.</p><p><b>Investigating</b> (2025-03-19T20:41:18Z): DataCenters Network Outage Notification We are aware of an issue affecting network services to a number of clients originating out of our IAD3 data center. Our networking team is actively troubleshooting this issue, and additional information will be provided as we work to resolve this as quickly as possible.</p>https://status.8dweb.com/incidents/98.html2025-02-25T19:16:04Z2025-02-25T19:16:04Z<p><b>Resolved</b> (2025-02-25T19:16:04Z): We experienced a NON-scheduled update on our Enhance servers. This was not Enhance v.11 to v.12 - that is on hold until further notice. This issue was a security cronjob that fired during normal business hours, causing most of the Enhance servers to reboot after critical SSH updates were run. We are adjusting this cron for notify only so that these types of updates will be scheduled and monitored.</p>https://status.8dweb.com/incidents/97.html2025-02-14T17:19:47Z2025-02-14T15:48:04Z<p><b>Resolved</b> (2025-02-14T17:19:47Z): Onsite team has found that a previous security script altered mount points. This has been rectified and web05 is online.</p><p><b>Identified</b> (2025-02-14T16:03:01Z): Team is enroute to data center to check why Web05 is not responding. 2 reboot attempts have failed.</p><p><b>Identified</b> (2025-02-14T15:54:07Z): During reboot process, WEB05 has hung. Team is investigating</p><p><b>Identified</b> (2025-02-14T15:48:04Z): Security Updates are being applied and reboots during business hours are taking place. Downtimes will be minimal.</p>https://status.8dweb.com/incidents/96.html2025-01-28T13:35:25Z2025-01-28T13:23:40Z<p><b>Resolved</b> (2025-01-28T13:35:25Z): The issue was an unscheduled reboot for Operating System update. Server is up.</p><p><b>Investigating</b> (2025-01-28T13:23:40Z): We are investigating WEB05 server at the moment. Updates will follow</p>https://status.8dweb.com/incidents/95.html2024-12-10T11:02:26Z2024-12-10T11:02:09Z<p><b>Resolved</b> (2024-12-10T11:02:26Z): Server reboot finalized.</p><p><b>Resolved</b> (2024-12-10T11:02:09Z): There was a need to remove some tools from WEB05 and perform an update. This was accomplished. Server is now up and running as of 6:00am.</p>https://status.8dweb.com/incidents/94.html2024-11-13T13:11:25Z2024-11-13T00:57:58Z<p><b>Resolved</b> (2024-11-13T13:11:25Z): This matter is resolved. The Data Center has not completed an ROF.</p><p><b>Investigating</b> (2024-11-13T00:57:58Z): We were alerted about 5 minutes ago that all sites and services in our IAD4 Data Center are unreachable. We have reached out to data center personnel.</p>https://status.8dweb.com/incidents/93.html2024-11-13T13:12:07Z2024-10-05T01:16:32Z<p><b>Resolved</b> (2024-11-13T13:12:07Z): The past 30 days have been without incident on Cogent link.</p><p><b>Monitoring</b> (2024-10-09T12:30:04Z): 2024-10-09 - COGENT UPDATE: Customers connected to our network located at 12100 SUNRISE VALLEY DR. in the Reston, VA area may be experiencing loss of network connectivity. NOTE: 8Dweb personnel have been onsite and found no current network outages, however, with the Cogent partial outage, we continue to monitor the network...</p><p><b>Monitoring</b> (2024-10-05T02:29:43Z): Operational at 9:55pm Eastern. This will remain open for 72 hours.</p><p><b>Investigating</b> (2024-10-05T02:29:16Z): Cogent found an issue on their side, and made a change in configuration. We appear to back online. Please use portal to update of any continuing outages/issues.</p><p><b>Investigating</b> (2024-10-05T01:16:32Z): At this time, we have had 18 hours of downtime on the 23.165.0.0/24 and about 12 hours of downtime on 38.83.60.0/23 subnets. Please send all emails to noc@8dweb.co to report continued outages. We continue to work with Cogent to see when they will rectify the routing issues that have plagued us all day.</p>https://status.8dweb.com/incidents/92.html2024-10-05T02:28:44Z2024-10-04T02:03:57Z<p><b>Resolved</b> (2024-10-05T02:28:44Z): Resolved</p><p><b>Monitoring</b> (2024-10-05T02:28:26Z): Resolved.</p><p><b>Monitoring</b> (2024-10-04T02:03:57Z): At 9:09pm we lost our feed from one of our uplines - 365 Data Centers. Restoration took place at 9:49pm. No explanation has been forthcoming at this time. If/When they provide a clear RFO we will post that to this issue.</p>https://status.8dweb.com/incidents/91.html2025-02-17T14:18:27Z2024-09-27T11:30:55Z<p><b>Resolved</b> (2025-02-17T14:18:27Z): HMM.</p><p><b>Monitoring</b> (2024-09-27T11:30:55Z): https://help.8dweb.com/announcements/article/wp-engine-sues-wordpress-founder-matt-mullenweg-and-automattic-in-high-stakes-copyright-clash</p>https://status.8dweb.com/incidents/90.html2024-09-20T23:35:47Z2024-09-20T18:31:52Z<p><b>Resolved</b> (2024-09-20T23:35:47Z): The offending switch has been removed, everything is now cut over to the new equipment. This matter is now closed.</p><p><b>Investigating</b> (2024-09-20T18:31:52Z): Today we experienced a total outage on our route IP blocks affecting all customers in IAD3. It took a bit of time to assess onsite. The issue was with one of our primary links AND our switch. Once the issue was identified steps were taken to TEMPORARILY by-pass this switch. All permanent links will be finalized after 6pm Today. There will be another 10-15 minute window of expected down time as this is a hard-cutover to alternate equipment.</p>https://status.8dweb.com/incidents/89.html2024-09-13T00:22:45Z2024-09-12T23:55:52Z<p><b>Resolved</b> (2024-09-13T00:22:45Z): The issue has been identified with an OS update on several VM&#x27;s Restorations are taking place.</p><p><b>Investigating</b> (2024-09-12T23:55:52Z): Some customers have reported VM offline... we are investigating and will restore service as soon as possible.</p>https://status.8dweb.com/incidents/88.html2024-08-14T21:15:32Z2024-08-14T14:38:28Z<p><b>Resolved</b> (2024-08-14T21:15:32Z): All sites are restored.</p><p><b>Identified</b> (2024-08-14T19:42:06Z): Restoration of Sites on WEB06 has begun. There may be some SSL Certificate issues for a short while after your site is restored. This will self-correct as the server requests new and updated SSL certifications (SSL certificates is what makes https work properly). The restoration takes place with a series of sites per round, so restoration of any particular site has no guaranteed time-frame.</p><p><b>Identified</b> (2024-08-14T18:28:23Z): We have ascertained the issue and replaced the faulty (new out of box 2 weeks ago) drive. We have also built in further redundancy on WEB06. The server is repaired and in the rack. We will commence restoration of sites after some testing and adding it to our Enhance hosting estate.</p><p><b>Investigating</b> (2024-08-14T16:10:17Z): Restoration of SOME sites form WEB06 to WEB05 is underway. However, due to the fact that 8Dweb does not handle name servers for all site, those sites that do not utilize dns100.8dcloud.com dns200.8dcloud.com dns300.8dcloud.com will need to await repair of WEB06.</p><p><b>Investigating</b> (2024-08-14T15:23:40Z): Web05 has self-recovered from an as yet unexplained fault. Web06, however, is currently OFFLINE. Our team will work to restore the server and websites to full functionality. There is NO current ETA.</p><p><b>Investigating</b> (2024-08-14T14:38:28Z): We have experienced an ODD Appcd Daemon lockup on two of our Enhance Webservers, in different data centers at the same time. Our team is investigating the issue</p>https://status.8dweb.com/incidents/87.html2024-07-30T11:47:52Z2024-07-30T11:45:23Z<p><b>Resolved</b> (2024-07-30T11:47:52Z): NONE</p><p><b>Investigating</b> (2024-07-30T11:47:33Z): NONE</p>https://status.8dweb.com/incidents/86.html2024-07-02T20:18:04Z2024-07-02T17:50:40Z<p><b>Resolved</b> (2024-07-02T20:18:04Z): SSH updates finalized on all servers.</p><p><b>Investigating</b> (2024-07-02T17:50:40Z): due to a rather nasty openssh bug that allows remote root execution, all - that is ALL sentry servers running any form of linux will be updated and rebooted (if required) asap. There will be no direct customer notifications sent due to the severity and importance of this issue.</p>https://status.8dweb.com/incidents/85.html2024-01-02T04:16:34Z2023-12-13T12:10:55Z<p><b>Resolved</b> (2024-01-02T04:16:34Z): See January 1, 2024 IAD3 Network Notices.</p><p><b>Monitoring</b> (2023-12-13T12:11:25Z): At this time, the affected servers are working properly. We will leave this monitoring for the next 24 hours.</p><p><b>Investigating</b> (2023-12-13T12:10:55Z): 8Dweb experienced some oddities with memory management on our IAD3 and IAD4 hosting cluster. This began at 11:06pm on December 12. The issue was resolved with reboots of several hosts and sentryserver VMs.</p>https://status.8dweb.com/incidents/84.html2023-10-27T15:36:39Z2023-10-27T05:33:41Z<p><b>Resolved</b> (2023-10-27T15:36:39Z): This matter is now closed.</p><p><b>Monitoring</b> (2023-10-27T13:04:57Z): ...</p><p><b>Identified</b> (2023-10-27T13:02:55Z): ...</p><p><b>Identified</b> (2023-10-27T12:59:36Z): As of 8:56am Most IP connectivity has been restored. We are leaving this issue in critical status for the next 90 minutes.</p><p><b>Identified</b> (2023-10-27T12:18:26Z): Update from Data Center Personnel @ 8:15am: Please be advised that the maintenance activity that was originally scheduled to run between 10/27/23 00:00 EDT and 10/27/23 04:00 EDT has been extended for an additional two (2) hours due to unforeseen circumstances. Further updates will be provided as they become available. A final completion notice will only be sent once this maintenance has been confirmed completed. If you are experiencing any manner of service interruption as a result of this maintenance, rest assured that this event is being actively addressed by our senior engineers and that every effort is being made to restore your services as quickly as is possible.</p><p><b>Identified</b> (2023-10-27T11:04:41Z): Update from Data Center Personnel @7:03am: Please be advised that this maintenance activity that began between 10/27/23 00:00 Eastern and 10/27/23 04:00 Eastern has been extended due to unforeseen circumstances. Further updates will be provided as they become available. A final completion notice will only be sent once this maintenance has been confirmed completed.</p><p><b>Identified</b> (2023-10-27T10:26:33Z): Some customers are seeing restored IP connectivity, however, most of our IAD3 network remains offline at this moment.</p><p><b>Identified</b> (2023-10-27T10:09:26Z): The 6am Window has now arrived with no resolution. Awaiting further updates from Data Center Personnel.</p><p><b>Identified</b> (2023-10-27T09:12:53Z): Update from Data Center Personnel: Please be advised that this maintenance activity that began between 10/27/2023 at 00:01 AM EDT and 10/27/2023 at 4:00 AM EDT has been extended to 10/27/2023 at 6:00 AM EDT due to unforeseen circumstances. Further updates will be provided as they become available. A final completion notice will only be sent once this maintenance has been confirmed completed.</p><p><b>Identified</b> (2023-10-27T09:05:29Z): There has been no word nor any replies to 8Dweb inquiries from Data Center personnel for the IAD3 outage for one hour. All Primary and Secondary network connectivity remains offline at this time.</p><p><b>Identified</b> (2023-10-27T08:21:26Z): Here is the latest from the Data Center Personnel: &quot;Please be advised that this maintenance activity that began between 10/27/2023 at 00:01 AM EDT and 10/27/2023 at 4:00 AM EDT has been extended due to unforeseen circumstances. Further updates will be provided as they become available.&quot;</p><p><b>Identified</b> (2023-10-27T08:18:51Z): The window has now progressed more than 15 minutes past what was promised. Data center personnel had indicated it would be less than the window, then would be the window, and now the time has extended. 8D personnel are awaiting clarification and response from 365 at this time. Please be advised that we will keep this notice updated as we gain information.</p><p><b>Identified</b> (2023-10-27T07:22:56Z): ...</p><p><b>Investigating</b> (2023-10-27T07:08:18Z): At this moment, despite being notified in writing that this event would be &quot;shorter&quot; than expected (once again 8D received no prior notice - the data center team is working to rectify that matter) - it appears the event may last the full 240 minute window.</p><p><b>Investigating</b> (2023-10-27T06:00:47Z): The data center team has responded that this was a planned event - However - it is confirmed that no email notice regarding such a major event was provided. Here is the information received: Facility(s): IAD3 – Reston, VA Ticket #: 2671997 Maintenance Type: Scheduled Network Maintenance Please be advised that from approximately/27/2023 at 00:01 AM EDT to 10/27/2023 at 4:00 AM EDT, 365 Data Centers will be conducting scheduled network maintenance in the Reston, VA area. Please see the details below: Duration of Window: 4 Hours Maintenance Location: Reston, VA Reason for Maintenance: Core network switch replacement Customer Estimated Impact &amp; Duration: You are directly connected to a device that will be impacted by this maintenance. Your service is expected to be impacted, which may result in a loss of connectivity of up to 240 minutes</p><p><b>Investigating</b> (2023-10-27T05:59:06Z): It has taken our team some time to contact data center personnel. The issue as they report is that there is a maintenance window at the Coresite facility. This maintenance window was not previously announced, but does not appear to be an emergency window. Information is still flowing.</p><p><b>Investigating</b> (2023-10-27T05:33:41Z): There is an as yet unexplained network outage at IAD3 - CR7. Please be advised that our team is still seeking information on this issue.</p>https://status.8dweb.com/incidents/83.html2023-05-02T19:42:55Z2023-05-01T23:25:21Z<p><b>Resolved</b> (2023-05-02T19:42:55Z): Current Goals with Plesk15 and IAD3 SAN have been met.</p><p><b>Investigating</b> (2023-05-01T23:25:21Z): We are currently doing some upgrades to the XCP platform and SAN which will require Plesk15 Server to be offline for about 30 minutes.</p>https://status.8dweb.com/incidents/82.html2023-04-21T16:43:37Z2023-04-21T15:54:47Z<p><b>Resolved</b> (2023-04-21T16:43:37Z): The issue has be resolved. An update was hung, and needed to be restarted.</p><p><b>Identified</b> (2023-04-21T15:54:47Z): The 8Dweb Portal is currently offline and you have been redirected here. This issue will be resolved soon.</p>https://status.8dweb.com/incidents/81.html2023-04-21T16:43:13Z2023-04-21T15:54:04Z<p><b>Resolved</b> (2023-04-21T16:43:13Z): The issue has been resolved. A Recent Joomla Update was the root cause.</p><p><b>Monitoring</b> (2023-04-21T15:54:04Z): The Primary 8Dweb.com site is currently offline for maintenance.</p>https://status.8dweb.com/incidents/80.html2023-02-02T06:45:41Z2023-02-02T05:34:35Z<p><b>Resolved</b> (2023-02-02T06:45:41Z): The issue has been found and resolved. All SentryServers in IAD3 cloud should be properly running now.</p><p><b>Investigating</b> (2023-02-02T05:34:35Z): Issues with Host updates have caused some SentryServers to not properly reboot. We are examining the issue and will update when we have greater understanding of the problem.</p>https://status.8dweb.com/incidents/79.html2023-01-13T12:49:59Z2023-01-11T12:11:09Z<p><b>Resolved</b> (2023-01-13T12:49:59Z): Plesk10 sites have been migrated. Please keep updated via the maintenance notice</p><p><b>Identified</b> (2023-01-11T12:22:55Z): Plesk10 currently resides in our IAD3 Data Center on our XCP cloud infrastructure. In order to Diversify our CMSdefender servers, we will migrate Plesk10 Customers to Plesk40 which will be located in our IAD4 Data center. The SAN units in both data centers has recently been replaced, and the IAD4 SAN has been upgraded with expanded capacity and network speed. Your sites will be migrated to the new server, and if your DNS is hosted on our Amazon Route53 infrastructure, the IP changes will be transparent. There **WILL BE** SMTP changes - the new incoming and outgoing SMTP server will be smtp40.cmsdefender.com - this only affects you if your email is currently hosted on Plesk10.</p><p><b>Identified</b> (2023-01-11T12:11:09Z): Issues with Plesk10 Continue. Plans to migrate customers in late Fall 2022 had to be scrapped as issues arose with the 8Dweb SAN infrastructure at that time. Plesk10 is End of Life, and as a result, customers will be migrated to Plesk40.cmsdefender.com this week. There will be no priority established for the move, however IF you do not allow 8Dweb to control your DNS entries through our Amazon Route53 infrastructure, you will need to update your DNS records. 24 hour notification of migrations will be sent. The expected migration start time is 6pm Eastern on Thursday, January 12, 2023.</p>https://status.8dweb.com/incidents/78.html2022-12-16T21:31:25Z2022-12-16T21:31:03Z<p><b>Resolved</b> (2022-12-16T21:31:25Z): Plesk10 Server rebooted. Services restored.</p><p><b>Identified</b> (2022-12-16T21:31:03Z): Plesk10 Reboot after Crash.</p>https://status.8dweb.com/incidents/77.html2022-12-02T13:46:17Z2022-12-02T13:31:08Z<p><b>Resolved</b> (2022-12-02T13:46:17Z): Plesk 10 reboot cycle complete</p><p><b>Monitoring</b> (2022-12-02T13:31:08Z): Security update requires a reboot on Plesk10.</p>https://status.8dweb.com/incidents/76.html2022-12-02T13:20:23Z2022-12-02T13:18:30Z<p><b>Resolved</b> (2022-12-02T13:20:23Z): Reboot Cycle complete</p><p><b>Monitoring</b> (2022-12-02T13:18:30Z): Plesk15 has an important security update requiring reboot. Reboot initiated at 8:17am Eastern / 1:17pm GMT</p>https://status.8dweb.com/incidents/75.html2022-11-17T13:04:30Z2022-11-14T13:53:40Z<p><b>Resolved</b> (2022-11-17T13:04:30Z): The issue has been found and resolved.</p><p><b>Investigating</b> (2022-11-14T13:53:40Z): We have found that our R1 Backup platform is unable to pull data from IAD3 data center. The most likely cause is the move of SAN equipment over the weekend. We will update when the issue is clarified and resolved by our team.</p>https://status.8dweb.com/incidents/74.html2022-11-13T02:15:48Z2022-11-12T17:59:28Z<p><b>Resolved</b> (2022-11-13T02:15:48Z): All SentryServers have been safely moved to other SAN devices. The hardware was moved to IAD3 to expedite repairs there.</p><p><b>Monitoring</b> (2022-11-12T17:59:28Z): Due to the Necessity to shift some SAN hardware from IAD4 to IAD3 as part of the recovery process for IAD3 clients affected by SAN02 primary and backup failures, there will be some lag on SentryServers, and some VM&#x27;s will be shut down for short periods of time as we move data onto other SAN units. This is a critical issue to help resolve the IAD3 issue in a more expedient manner. The lag and responsiveness of your SentryServer will return to normal once they are migrated onto new hardware that has not been utilized in IAD4.</p>https://status.8dweb.com/incidents/73.html2022-11-17T13:04:05Z2022-11-11T23:46:44Z<p><b>Resolved</b> (2022-11-17T13:04:05Z): Closing this issue.</p><p><b>Monitoring</b> (2022-11-13T02:17:17Z): The SAN devices in IAD3 have been repaired and all devices and SentryServers brought back online as of 9:38pm Saturday, November 12. This will remain in Monitoring Status for 72 hours. Please open a ticket at https://help.8dweb.com if any problems persist for your SentryServer.</p><p><b>Identified</b> (2022-11-12T17:56:16Z): We have continued to attempt recovery of the failed SAN and backup SAN that service a number of our SentryServer clients in IAD3. This is affecting a handful of customers at this time. Restoration will continue as replacement hardware becomes available over the weekend. At this point, our intent is to have the failed customers migrated or restored from backup systems by Monday morning at 8am. We will not give any specific time-frames to specific customers since the repair and restoration of data must proceed in a particular manner. We know this is a major inconvenience, however, the failure of the primary and backup SAN devices for a portion of our cloud clients at IAD3 almost simultaneously has caused significant delays.</p><p><b>Investigating</b> (2022-11-11T23:46:44Z): We have encountered what appears to be a catastrophic SAN failure in our IAD3 infrastructure. If you cannot currently reach your SentryServer it is likely it is due to this issue. There is currently NO specific timeframe for resolution as we need to work through a number of steps to assess.</p>https://status.8dweb.com/incidents/72.html2022-05-31T21:32:41Z2022-05-31T21:19:23Z<p><b>Resolved</b> (2022-05-31T21:32:41Z): Reboot has solved the issue. An errant process caused issues on the server.</p><p><b>Investigating</b> (2022-05-31T21:19:23Z): Plesk10 Server went offline a short while ago, it is being rebooted since the issue (kernel panic) was not able to be resolved quickly.</p>https://status.8dweb.com/incidents/71.html2022-03-28T12:26:15Z2022-03-24T22:26:11Z<p><b>Resolved</b> (2022-03-28T12:26:15Z): Issues with Plesk 10 resolved late Sunday.</p><p><b>Monitoring</b> (2022-03-26T18:01:01Z): This will now take place at 2pm today. The original window did not permit.</p><p><b>Identified</b> (2022-03-24T22:26:11Z): There will need to be a reboot of the Plesk10 hosting platform. This will commence at 9pm Eastern Daylight today, March 24. Server reboots are typically 1-5 minutes.</p>https://status.8dweb.com/incidents/70.html2022-11-12T17:52:20Z2022-03-24T22:17:19Z<p><b>Resolved</b> (2022-11-12T17:52:20Z): OLD</p><p><b>Monitoring</b> (2022-11-11T23:47:17Z): closing</p><p><b>Monitoring</b> (2022-03-31T12:52:05Z): The Data Center personnel have not provided an RFO (reason for outage) at this point. We will keep this open for one more week in anticipation.</p><p><b>Monitoring</b> (2022-03-24T22:17:19Z): Yesterday there was a major network event at our IAD4 data center. At this juncture, we understand there was a major failure somewhere above the IAD4 facility which affected all fiber feeds. There has been no official Reason for outage (RFO) provided, so 8Dweb is a bit in the dark on the actual issue. We will provide that RFO when presented to us. Network Services resumed around 6:35pm on March 23rd (last evening).</p>https://status.8dweb.com/incidents/69.html2022-01-26T15:19:07Z2022-01-26T15:19:07Z<p><b>Resolved</b> (2022-01-26T15:19:07Z): We will be doing an unscheduled reboot of Plesk20 server. This is to ensure IP changes are consistent and that Nginx on Plesk is properly functioning after reboot. This is considered an emergency matter</p>https://status.8dweb.com/incidents/68.html2022-01-26T14:54:51Z2022-01-26T14:54:51Z<p><b>Resolved</b> (2022-01-26T14:54:51Z): Plesk20 - It was discovered that due to an IP change on the management and backup networks there was an IP conflict. This caused an issue with the Nginx service on Plesk20. The IP conflict has been resolved, however, this will be monitored.</p>https://status.8dweb.com/incidents/67.html2022-01-21T00:19:54Z2022-01-20T23:28:29Z<p><b>Resolved</b> (2022-01-21T00:19:54Z): All Updates and Reboots have been completed. Please open a ticket if any services remain affected.</p><p><b>Identified</b> (2022-01-20T23:28:29Z): Cloud Host updates will be taking place from 5pm-8pm on IAD3 and IAD4 Infrastructure. Most VM’s will automatically live migrate to other hosts. Some infrastructure serves such as Plesk10, 15, 20 will also require reboots during this period. This will cause short outages on those platforms. These updates and reboots are necessary to mitigate several exploits in linux systems that have been revealed this week.</p>https://status.8dweb.com/incidents/66.html2022-01-16T13:14:30Z2022-01-13T13:53:02Z<p><b>Resolved</b> (2022-01-16T13:14:30Z): Plesk10 remains stable after rebuild. This issue is now closed</p><p><b>Monitoring</b> (2022-01-15T13:55:05Z): Plesk 10 Update: Full restore is finalized. After a painstaking rebuild of Plesk10, we are happy to announce that the server is online and running smoothly. We will continue to monitor for the next 24 hours and then move on to customer sites that are experiencing high load.</p><p><b>Investigating</b> (2022-01-15T00:37:35Z): Be aware, the expected downtime for Plesk10 will begin at 8:30pm Eastern. This will affect mail and hosting services on the server. The expected down-time cannot be ascertained at this moment. We will update once restore has begun.</p><p><b>Investigating</b> (2022-01-15T00:36:05Z): After further review, it is evident that Plesk10 will need to be taken offline again. This will commence at 8:30pm Eastern on Friday the 14th. The server will be offline for several hours as a contingency plan is enacted to ensure data integrity and restoration of server data. We apologize for this inconvenience.</p><p><b>Monitoring</b> (2022-01-14T20:34:34Z): Plesk10 is back online. Some issues with disk corruption were found and rectified. Issues with high load may remain as further investigation takes place</p><p><b>Investigating</b> (2022-01-13T17:11:23Z): The issue with Plesk10 are requiring us to make an emergency backup and restore. Downtime will be extended and there is NO ETA at this time.</p><p><b>Investigating</b> (2022-01-13T13:53:02Z): Plesk10 is experiencing very high load. The issue is unclear at the moment. The server will be taken offline for a short period to double check some matters. Expected downtime is 30-60 minutes starting 9:00am Eastern</p>https://status.8dweb.com/incidents/65.html2022-01-06T12:39:52Z2022-01-05T16:43:08Z<p><b>Resolved</b> (2022-01-06T12:39:52Z): No further issues have been observed from this work. This matter is now closed</p><p><b>Monitoring</b> (2022-01-05T16:45:18Z): The non-functioning switch has been removed from service and network systems changed to bypass this particular edge-switching setup. All redundancy has been restored.</p><p><b>Investigating</b> (2022-01-05T16:43:08Z): This incident is unrelated to the earlier incident. An Edge Switch in our IAD3 facility has failed outright. Redundant systems will take over shortly.</p>https://status.8dweb.com/incidents/64.html2022-01-06T12:40:58Z2022-01-05T11:26:52Z<p><b>Resolved</b> (2022-01-06T12:40:58Z): A Future maintenance window will be scheduled to handle some matters left in place during the emergency window on 01-05-2022. This issue is now closed.</p><p><b>Monitoring</b> (2022-01-05T16:43:57Z): Our team has identified and repaired a Storage Area Network switching issue. Replacement hardware is in place and all systems are functioning.</p><p><b>Investigating</b> (2022-01-05T11:26:52Z): Our Team is investigating outages on Plesk10 and a portion of our XCP-ng Cloud at IAD3. This does affect our 8D portal site. Please use help.8dweb.com.</p>https://status.8dweb.com/incidents/63.html2021-12-16T11:29:00Z2021-12-15T20:25:25Z<p><b>Resolved</b> (2021-12-16T11:29:00Z): Issue resolved.</p><p><b>Identified</b> (2021-12-15T20:25:25Z): As of 14:30 Eastern on 12-15-2021 the 8Dweb portal is down. Please use https://help.8dweb.com for any support needs.</p>https://status.8dweb.com/incidents/62.html2021-12-15T20:26:01Z2021-09-28T12:48:52Z<p><b>Resolved</b> (2021-12-15T20:26:01Z): Thanks Plesk... :(</p><p><b>Identified</b> (2021-09-28T13:10:03Z): Please exercise patience as our team works to patch your servers.</p><p><b>Identified</b> (2021-09-28T13:07:57Z): Plesk15 has been patched - Sites loading Plesk10 has been patched - Sites loading Plesk20 has been patched - Sites loading</p><p><b>Identified</b> (2021-09-28T12:59:59Z): 8Dweb is working through the problem as quickly as possible. Plesk has updated their hotfix article 3 times in less than 10 minutes. The plesk patch server is apparently overwhelmed. Please be patient.</p><p><b>Identified</b> (2021-09-28T12:48:52Z): A VERY nasty surprise awaits ANY Plesk server manager this morning... A Plesk update HOSED apache2 service. This is not ONLY an 8Dweb issue, but **all** 8Dweb Plesk servers are affected. There is currently NO estimate on resolution of individual cases. Our team will be working on servers one-by-one to apply the hotfix provided by Plesk.</p>https://status.8dweb.com/incidents/61.html2021-02-17T06:50:04Z2021-02-11T13:46:27Z<p><b>Resolved</b> (2021-02-17T06:50:04Z): Plesk 15 Server - All goals were met without downtimes longer than 5 minutes. 8Dweb personnel were able to devise a method of live migration of data to new hardware node and storage without extended downtime. Most users experienced no downtime, some may have had a short 5 minute outage while final disk sync took place. All goals were met. This window is now closed.</p><p><b>Identified</b> (2021-02-16T20:46:12Z): Plesk15 Server - There will be a MANDATORY Emergency Maintenance on Plesk15 / SMTP15 server tonight beginning at 11pm. This will require the server to be OFFLINE. The Maintenance window will be from 02-16-2021 23:00 EST until 02-17-2021 03:00 EST. It is our hope that the downtime will be minimal, but due to the nature of the work to be performed, this outage could last for up to several hours.</p><p><b>Identified</b> (2021-02-11T13:46:27Z): We have been notified by data center personnel that there are BGP (routing) issues. This follows an emergency maintenance window on 02-10-2021 by the same data center. At this time the matter is considered critical emergency maintenance. This event is outside the scope of 8Dweb personnel, however, it may affect routing to our systems. We will report once the matter is resolved: From Data Center Personnel: Our network engineers received multiple alarms of a BGP network event on our IAD3 core network. Our network engineers continue this investigation to find a resolution to this matter. We are experiencing BGP flap conditions on two known routers. We&#x27;re working with multiple engineers on our team to impose corrective measures. Work is still ongoing and we currently don&#x27;t have an ETR. This emergency is our highest priority. Additional updates will be provided as they become available.</p>https://status.8dweb.com/incidents/60.html2021-02-11T13:43:40Z2021-02-09T15:07:30Z<p><b>Resolved</b> (2021-02-11T13:43:40Z): This issue was resolved. Total outage was 22 minutes.</p><p><b>Identified</b> (2021-02-09T15:07:30Z): We are currently handling a MySQL crash on Plesk15</p>https://status.8dweb.com/incidents/59.html2021-01-24T22:37:00Z2021-01-24T21:42:21Z<p><b>Resolved</b> (2021-01-24T22:37:00Z): Emergency Maintenance Window is now closed. Please contact NOC if any issues are found with your SentryServer VM</p><p><b>Identified</b> (2021-01-24T21:42:21Z): Due to the sudden offlining of the cloud system at IAD3 our team will be performing some further mandatory updates to our cloud systems in IAD3 and IAD4. The updates in IAD3 will result in little to no downtime as various system maintenance takes place. The updates in IAD4 will require all systems to be updated and then fully shut down and restarted. There will be additional hardware added to IAD4 in the near future to help alleviate any such full shut-down in future maintenance cycles. The expected total down-time for IAD4 cloud nodes and their respective VM&#x27;s will be 1 hour starting at 17:00 (5pm) Eastern. This is to be considered an emergency maintenance event.</p>https://status.8dweb.com/incidents/58.html2021-01-23T13:18:23Z2021-01-22T22:27:00Z<p><b>Resolved</b> (2021-01-23T13:18:23Z): As part of the power event there was a hardware failure. The faulty power module has been replaced and all systems reported online as of 6:33pm on 01/22/2021</p><p><b>Investigating</b> (2021-01-22T22:27:00Z): A power event has taken place at our IAD3 data center. Our team is currently evaluating a near total loss of connectivity to the XCP-ng cloud system there. Since this encompasses numerous physical nodes, this is considered an emergency event. Please hold all calls.</p>https://status.8dweb.com/incidents/57.html2021-01-23T13:17:34Z2021-01-19T20:11:50Z<p><b>Resolved</b> (2021-01-23T13:17:34Z): Resolved</p><p><b>Monitoring</b> (2021-01-19T23:52:54Z): We have identified the issue with Plesk15 server. There was a database corruption which was causing issues with many sites as well as the smtp15 mail subsystem. We were able to restore the mail services, but the remaining repairs took several hours. We will continue to monitor the server, but it appears all services have returned to normal.</p><p><b>Investigating</b> (2021-01-19T20:11:50Z): Hello, We are currently investigating connectivity issues with Ples15 and some other servers in IAD3.</p>https://status.8dweb.com/incidents/56.html2020-10-09T16:47:11Z2020-09-28T16:36:32Z<p><b>Resolved</b> (2020-10-09T16:47:11Z): After tests, we were unable to ascertain that a faulty hardware node in one of our IAD3 cloud clusters was the issue. The matter was resolved by our team.</p><p><b>Investigating</b> (2020-09-28T16:36:32Z): Currently we are experiencing connectivity issues at IAD3. The reason has not been ascertained, but our staff is looking into the matter.</p>https://status.8dweb.com/incidents/55.html2020-07-30T02:11:57Z2020-07-30T01:47:56Z<p><b>Resolved</b> (2020-07-30T02:11:57Z): Issue was related to a directory error on /var/qmail. Problem has been resolved, server and mail are now functioning correctly</p><p><b>Investigating</b> (2020-07-30T01:47:56Z): We are currently investigating an issue with the Plesk15.cmsdefender.com (and associated email systems).</p>https://status.8dweb.com/maintenance/46.html2026-01-24T21:00:00ZWeather Advisory – Operational Status Last Updated: Saturday, [DATE] at [TIME] ET We are monitoring a severe weather system impacting the DC Metro / Northern Virginia area. All services are operating normally at this time. For staff safety, on-site and remote-hands dispatches are unavailable from 4:00 PM Saturday through 12:00 PM Monday (ET). Network operations, monitoring, and support remain active. Further updates will be posted as conditions change. — 8Dweb Network Operations (2026-01-24T21:00:00Z to 2026-01-26T17:00:00Z)https://status.8dweb.com/maintenance/1.html2025-11-18T04:57:02ZAs a valued customer, Cogent is committed to keeping you informed about any changes in the status of your service with us. This email is to alert you regarding maintenance we will be performing on our network: Start time: 11/18/25 at 00:01 - America/New_York (05:01 UTC) End time: 11/18/25 at 06:00 - America/New_York (11:00 UTC) Work order number: NA26028-0-0 Order ID(s) impacted: 3-001758376, 3-001761364, 3-001775214 Expected Outage/Downtime: 15-30 minutes (each circuit migrated separately) During this maintenance window, you may will experience one or more brief interruptions in service while we complete the maintenance activities. the interruption is expected to be less than 15-30 minutes (each circuit migrated separately); however, due to the complexity of the work, your downtime may be longer. Customers may also see some reconvergence during the maintenance window. (2025-11-18T04:57:02Z to 2025-11-18T10:57:02Z)https://status.8dweb.com/maintenance/45.html2025-11-12T03:17:24ZThere will be an UNSCHEDULED maintenance on our xcp-ng cluster in VA1. We are currently updating SAN network configurations. Due to the nature of this work, all VM's on the A2-02 Cluster will be PAUSED at 10:30am Eastern. This is so that new configurations can be properly pushed out to the network gear associated with the SAN and Storage Networks. This is an unusual issue, however, in order to maintain integrity of systems, Pausing the VM's is the best approach. Windows VM's will be SHUT DOWN and restarted. All bonding issues have been resolved. All VM's are returned to normal state. (2025-11-12T03:17:24Z to 2025-11-12T04:17:24Z)https://status.8dweb.com/maintenance/44.html2025-09-25T10:58:44ZUpdates are being run on all Plesk and Enhance Servers. All Systems have been patched (2025-09-25T10:58:44Z to 2025-09-25T11:28:44Z)https://status.8dweb.com/maintenance/43.html2025-09-17T19:45:43ZOur staff is currently running updates on our XCP-ng hosts. This will be seamless with no downtime to SentryServer VM's running on 8Dweb cloud servers. Customer hosts running single XCP-ng host pools will need to contact support for scheduled reboots of your host system. (2025-09-17T19:45:43Z to 2025-09-17T20:45:43Z)https://status.8dweb.com/maintenance/42.html2025-08-28T13:21:43ZOur team will be handling some essential Enhance and OS updates on the hosting cluster this morning. There may be some reboots involved, downtimes will be 1-5 minutes at most. (2025-08-28T13:21:43Z to 2025-08-28T14:21:43Z)https://status.8dweb.com/maintenance/41.html2025-08-01T16:27:17ZAll Enhance Servers are being upgraded to 12.9.3. There will be no down-time expected. A vulnerability in LiteSpeed and Open Lite Speed has been noted. All servers running either web server are currently being update. Hello, Please make sure to update to the latest version, as this release includes a critical security fix for a vulnerability that could be exploited. If you are unable to upgrade your server immediately, we recommend disabling HTTP/3 as a temporary precaution to avoid exposure. More details here: https://blog.litespeedtech.com/2025/08/18/litespeed-security-update/ Thanks for your attention! LiteSpeed Team All servers running vulnerable version of LiteSpeed and Open LiteSpeed have been updated, AND rebooted as a precaution. (2025-08-01T16:27:17Z to 2025-08-01T17:27:17Z)https://status.8dweb.com/maintenance/40.html2025-03-10T08:30:00ZPlease See the Announcement ab out Enhance Upgrades here: https://portal.8dweb.com/announcements/71/Subject-Scheduled-Enhance-Hosting-Upgrade--March-10-430-AM-ET.html The Enhance v.11 to v.12 Upgrade is Complete. The old backup servers had to be taken offline and removed for the upgrade process. The data on those servers has been maintained. The new backup01 server is online and sites will begin backups to that server immediately. We have restored the normal 4-7 hour rotation so that sites will backup 4 times daily and those backups will retained for 30 days. (2025-03-10T08:30:00Z to 2025-03-10T11:30:00Z)https://status.8dweb.com/maintenance/39.html2025-02-21T12:21:16ZOur team is running updates on Enhance Cluster this morning. This is mandatory and could not be deferred. recent ssh vulnerabilities noted are being patched. Updates are finalized. (2025-02-21T12:21:16Z to 2025-02-21T13:21:16Z)https://status.8dweb.com/maintenance/38.html2025-02-17T14:11:50Z# 8Dweb WordPress Update & Caching Policy Changes – Effective March 1, 2025 To enhance security and performance, 8Dweb will enforce the following changes: ## Weekly WordPress Updates Starting in 2025, WordPress Core, Themes, and Plugins will be updated every **Monday**, with additional updates for critical vulnerabilities. ## Removal of Insecure Plugins Any plugins that are outdated and flagged as security risks will be **automatically removed**. ## Standardized Caching Plugin Beginning **March 1, 2025**, the **only** caching plugin allowed on our CMSdefender shared hosting platform will be **Litespeed Cache (LSCache)**. All other caching plugins will be **automatically removed** daily. ## REDIS Object Caching Activation To further improve site performance: - **REDIS caching will be enabled** for all WordPress sites. - **LSCache will be automatically installed** on all WordPress sites. - **All other cache plugins will be removed**. These changes ensure optimal security, stability, and efficiency across all hosted websites. If you have any questions, please reach out to our support team. **– 8Dweb Team** (2025-02-17T14:11:50Z to 2025-04-18T14:11:50Z)https://status.8dweb.com/maintenance/37.html2024-09-28T01:00:00ZAt 9pm Tonight, the 23.165.0.0/24 IP Block will undergo BGP routing changes. There will be be a short interruption in services as the IP block is re-assigned. This will not affect DNS, only connectivity. Changes are starting now. At this time, routing via Cogent has not converged. Our team is awaiting updates. Routing Tables across the Internet are now updating properly. 93% at this time. Closing this Window. This concludes the BGP routing changes for 8Dweb. Our New and Existing Owned IPv4 blocks are routing properly. Future IPv6 BGP windows will be opened once all networks have stabilized. (2024-09-28T01:00:00Z to 2024-09-28T04:00:00Z)https://status.8dweb.com/maintenance/36.html2024-09-17T01:00:00ZMonday Evening, September 16th there will be a network update window. There will be a new maintenance window every evening from September 16th-24th form 9pm-1am. (2024-09-17T01:00:00Z to 2024-09-17T05:00:00Z)https://status.8dweb.com/maintenance/35.html2024-08-31T01:00:00ZFrom August 30th until September 30th 8Dweb will be moving customers to our owned IPv4 and IPv6 blocks. This will necessitate changes to both infrastructure, cabling and routing. Most of these changes will take place in Network Update Windows lasting from 9pm-12:00am. Each Change will be announced a minimum of 72 hours in advance. Most changes should take place quickly as DNS converges. Customers utilizing our SentryServers are part of our Amazon Route53 infrastructure, so changes made to your server IP addresses will propagate quickly. (2024-08-31T01:00:00Z to 2024-09-30T01:00:00Z)https://status.8dweb.com/maintenance/34.html2024-08-16T22:00:00ZThe final batch of Plesk15 Migrations will take place on Friday, August 16th between 6pm and midnight. 2 Notifications have been sent. Final notifications will be sent on Thursday August 15th. Plesk Migrations are Finalized. Shared Hosting accounts are now 99.9% running on our Enhance Cluster. Benefits: 3x CPU power, LiteSpeed Hosting (contact us about lscache and redis plugins); 10G connectivity. (2024-08-16T22:00:00Z to 2024-08-17T04:00:00Z)https://status.8dweb.com/maintenance/33.html2024-08-15T01:20:15ZSubsequent to the SSD failures, replacement and restoration of sites and services to the WEB06 server, there is a need for some Operating system updates and performance refinements. The server will be rebooted 3-5 times over the next 10-20 minutes. (2024-08-15T01:20:15Z to 2024-08-15T01:50:15Z)https://status.8dweb.com/maintenance/32.html2024-07-30T11:53:49ZStarting now and ending by October 30th, 2024, all 8Dweb CMSdefender customers on Plesk15 will be moved to our Enhance Hosting Platform. Migration Schedule: July 30th - August 10th: Customers without email accounts or using external email services (Outlook, Gmail, Zoho, etc.) will be migrated without prior notice. After August 10th: Customers with email services will be contacted individually to schedule their migration. They will need to update their mail clients after the migration. If you have special circumstances, our team will work with your IT team to assist with the migration. (2024-07-30T11:53:49Z to 2024-10-30T11:53:49Z)https://status.8dweb.com/maintenance/31.html2024-01-20T13:13:00ZOver the Next Couple of weeks there will be some Vendor updates on our Enhance Panel Servers in both IAD3 and IAD4. These updates will be run **as required** and may cause SHORT (1-3 minutes) outages. The purpose of these updates is substantially upgraded core, admin, and customer facing updates. Enhance 10.2.0 is currently being installed. There will be brief interruptions as system services are updated across the cluster. We are awaiting Enhance 10.3.0 and will update when this upgrade is to be installed. Enhance append 2.2.1 upgdates being rolled out this morning. Expect 1-2 minute pauses on some sites. Enhance 10.4.0 is being installed currently. Upgrade to Enhance 11.0 with NEW mail functionality will be underway this weekend. There will be BRIEF (1-2 minute) outages as servers are updated, rebooted and upgraded. 07-01-2024 - Enhance 11.01 Updates installed. Please open a ticket if your email experiences issues with DKIM. 07-08-2024 - Another round of updates running now. Upcoming Infrastructure Upgrade: Enhancing Your Hosting Experience Beginning on July 26th, 8Dweb will be overhauling our Enhance Hosting Panel Infrastructure. We chose Enhance for our hosting control panel on June 1, 2024, after an eight-month introductory period. On July 26th, we will update our hosting infrastructure in the IAD4 data center with new hardware specifically tailored for Enhance hosting. This upgrade will introduce higher clock speed CPUs and faster NVMe storage. All server roles for web02.my.8dcloud.com, web04.my.8dcloud.com, and web06.my.8dcloud.com will be migrated to the new hardware on web08.my.8dcloud.com. Due to the way Enhance performs migrations, this transition will be seamless for end users. Email will remain on the SMTP server to which your account is already assigned, so there will be no change. The IAD3 data center upgrade will follow in August 2024. Migration of data from web01 and web03 to the replacement web05 will take place tonight. This will be a major upgrade to the hosting platform in IAD3, moving from 2.6Ghz processors to 4.5Ghz processors. This update will also include much faster Gen4 NVME storage for web/mysql data. The move of data will be handled by the 8Dweb team on Friday, July 26 around 6pm Eastern. The move of the sites will be handled utilizing the built-in Enhance server migration tool, so this will be seamless and will minimize down-time. Web01/Web03 will remain online until 6pm Monday to ensure finalization process completes. No customer-side changes or alterations are required. PLESK15 Customers, PLEASE see: https://status.8dweb.com and read about Plesk15 Migrations. Migration of Data from Web02 and Web04 to The New Web06 have begun and will run throughout the evening. Email service will not be affected, DNS services will remain online for the entire cluster. Sites are migrate 2 at a time. Web02 server migrations will be first, followed by web04. REMINDER: All Enhance Web Servers for 8Dweb CMSdefender clients will now be Litespeed Enterprise. This will permit WordPress and Joomla users to utilize the exceptionally fast LSCache Plugins for your your platforms. For Wordpress, the LSCache plugin will replace the existing redis plugin. You may begin utilizing Redis and LSCache Plugins on Monday August 5. (2024-01-20T13:13:00Z to 2025-01-19T13:13:00Z)https://status.8dweb.com/maintenance/30.html2024-01-04T03:05:56ZOur team has refined some network configs after the IAD3 infrastructure replacement that took place at 11pm on January 2, 2024. These are being pushed out. As a precaution, VM's on the affected network segments will be manually paused, and then resumed so no disk errors occur. This will be a 1-5 minute roll-out. All configurations were pushed out without incident. All internal network systems are now redundant, and running 25-100Gb connections now. (2024-01-04T03:05:56Z to 2024-01-04T04:05:56Z)https://status.8dweb.com/maintenance/29.html2024-01-03T04:00:00ZThere will be an emergency network maintenance session on our IAD3 network infrastructure. This will cause several brief outages beginning at roughly 11:00pm Eastern tonight - January 1. We apologize for the late notification. After assessing the situation, our team has decided that we will require 24 additional hours to prepare for the emergency maintenance window. We have stabilized and made some minor changes to the internal setups, and will continue to work on physical layer preparations. This maintenance window will move from tonight at 11pm until Tuesday, January 2nd, at 11:00pm Eastern. Affected systems affected will primarily be the IAD3 XCP cloud systems. Backend Systems and Network Issues have been fully resolved. IAD Backbone internal networks have all been fixed, and also upgraded to 25, 40 and 100Gb as required. (2024-01-03T04:00:00Z to 2024-01-03T08:00:00Z)https://status.8dweb.com/maintenance/28.html2023-12-04T17:00:00Z8Dweb will be migrating Plesk20 WordPress sites to our new Enhance Cluster (https://my.8dcloud.com) over the next several weeks. If you manage your own DNS and/or have Email accounts on Plesk20, you will need to contact our team at noc@8dweb.co. This migration is non-negotiable at this stage. The connectivity from the 8D customer portal will be updated so that you may use our portal to log into the new hosting control panel. 8Dweb has migrated 80% of Plesk20 Wordpress Customers to the Enhance cluster. However, due to issues with migration of email to the new platform, this migration window has been extended until at least November 30th. If you manage your own DNS you or your IT department will need to contact 8Dweb ASAP. Once again, this migration is non-negotiable. Plesk20 Final Migrations will commence on our about December 4, 2023. Please see this announcement for details and what may be required by website owners: https://help.8dweb.com/announcements/article/8dweb-urgent-announcement-final-website-migrations-away-from-plesk20-to-8d-enhance-cmsdefender-hosting-cluster The remaining migrations have been postponed due to timing of vendor support for migration from Plesk to Enhance. You will be individually notified when we begin to proceed. This matter has been extended another 30 days. The remaining migrations have been postponed due to timing of vendor support for migration from Plesk to Enhance. You will be individually notified when we begin to proceed. There have been some vendor delays with Enhance. At this time, our team is assessing the potential to move forward with manual migrations. Migrations have started. Final Customer Migratations from Plesk20 TO our Enhance Hosting Cluster will take place on Monday, January 29th between the hours of 8am and 4pm Eastern. After migrations are finalized, Plesk20 will be taken offline immediately. (2023-12-04T17:00:00Z to 2024-02-02T17:00:00Z)