Is Adeptcore down?

Product match: components.

Read the provider’s incident report

1. 2026-08-13T18:06:00.231-05:00 · identified

   We have received significant positive progress from the Phoenix datacenter. A third primary chiller has been successfully restored, and facility temperatures are continuing to stabilize. On-site datacenter staff are actively conducting all-hands physical inspections across core hardware and support infrastructure. Network connectivity to our cabinets appears to have been restored. While we await final, official confirmation from the datacenter that facility operations are fully stabilized, our

2. 2026-08-13T16:10:18.258-05:00 · identified

   We have spoken with the datacenter team and have received the following update. Ambient temperatures inside the facility are continuing to decrease and teams are actively following the remediation timeline outlined earlier today. Completed: Primary chiller (Chiller D) restored and temperature reduction underway. Ongoing / On Track: Deployment of temporary on-floor cooling units. In Progress: Restoration of Chiller C. Targeted for ~4:00 PM MST: Installation of additional temporary chillers a

3. 2026-08-13T14:27:00.356-05:00 · identified

   Thermal recovery operations remain underway at the Phoenix facility with the on-site vendor still working through the established remediation schedule to restore remaining chillers. Due to the elevated ambient temperatures, the facility's primary core network routing hardware went offline and has remained offline. As a result, our own connectivity and cloud services remain impacted. Facility engineers tentatively estimate core routing equipment may begin coming back online after 4:00 PM local t

4. 2026-08-13T12:02:03.427-05:00 · identified

   Our datacenter facility in Phoenix is continuing to work on the elevated temperatures which were brought on by severe overnight weather that affected the datacenter chillers. Facility teams have successfully restored primary cooling units and temperatures have begun to decrease. Additional measures are also scheduled with the introduction of additional temporary on-floor cooling equipment that will be deployed at 10:00 AM local time (Arizona time) and the restoration of the secondary chiller wi

5. 2026-08-13T11:07:26.730-05:00 · identified

   The datacenter team is continuing efforts to stabilize facility temperatures. As a precautionary measure while cooling repairs are underway, we have been informed that there may be brief, temporary outages affecting physical equipment across customer cabinets. Any potential interruptions are expected to last between 2 to 4 hours while thermal levels are managed. We will continue to provide further updates as the situation develops.

6. 2026-08-13T10:36:50.695-05:00 · identified

   Datacenter engineers and the hardware vendor remain on-site and are actively working to repair the facility's primary chillers. The elevated ambient temperatures are a direct result of this cooling system degradation. A firm estimated time for full restoration is not yet available from the datacenter but repairs are ongoing. We will provide another update as soon as new information becomes available.

7. 2026-08-13T09:35:39.414-05:00 · identified

   Per our latest conversation with the datacenter engineers, the issue affecting networking at the datacenter is part of a datacenter-wide issue that remains ongoing without an ETA for a resolution at this time. The datacenter facility equipment is currently experiencing issues as a result of higher than normal ambient temperatures in the building. These higher temperatures have affected multiple pieces of the datacenter's critical equipment responsible for routing and networking and as a result

8. 2026-08-13T08:10:07.100-05:00 · identified

   At this time we believe that the issue is originating at the datacenter's core routers. We've verified that our equipment remains operational but it is experiencing issues reaching out to the internet. Based on the troubleshooting performed by us thus far, this appears to be routing related. We have not yet received confirmation if this is an issue affecting the entire datacenter or a limited amount of customers. We are currently working with the datacenter to pinpoint the source of the issue

9. 2026-08-13T07:44:52.952-05:00 · identified

   We have identified the issue as network-related. Our NetOps team is actively investigating the outage. Out-of-band management remains operational and is functioning as expected. The team is currently troubleshooting WAN routing to isolate the source of the connectivity issue and restore normal service.

10. 2026-08-13T07:30:44.697-05:00 · investigating

    We are receiving reports of an outage at our PHX location. We are currently investigating this and will provide updates as soon as information becomes available.

Product match: components.

Read the provider’s incident report

1. 2026-08-05T16:55:15.886-05:00 · monitoring

   All networking at this time has been restored, and we are seeing connectivity being re-established for all affected client machines. NetOps determined that the issue was a WAN routing outage with failover not propagating. We are investigating exactly why the failover has not worked and how to prevent this from occurring in the future. While we investigate, we will route all traffic to the failover route to maintain continued functionality. We will be performing maintenance overnight to bring ELK

2. 2026-08-05T16:11:38.869-05:00 · identified

   We have identified the issue as a network routing problem and are working to resolve it as quickly as possible. We will provide updates as soon as we have more information.

3. 2026-08-05T16:00:43.354-05:00 · investigating

   We are receiving reports of our ELK Datacenter experiencing an outage for some of our clients. We are currently investigating this in tandem with Datacenter staff and will provide updates as we get them.

Product match: components.

Read the provider’s incident report

1. 2026-04-30T22:37:42.657-05:00 · monitoring

   In response to a critical cPanel vulnerability (CVE-2026-41940) disclosed by the vendor, we are proactively patching all cPanel servers across our environment. As a precaution while updates are rolling out, public access to the cPanel/WHM/Webmail management ports (2083, 2087, 2095, 2096) has been temporarily restricted. Your websites, email, and other services are not affected only the browser-based management interfaces. If you need access to cPanel or WHM during this window. Please submit a s

Product match: components.

Read the provider’s incident report

1. 2026-08-27T11:07:41.798-05:00 · postmortem

   # **Root Cause Analysis Report** PHX Datacenter Ransomware Outage & Infrastructure Recovery   ## **Executive Summary** On July 10, 2026, a widespread outage impacted the PHX Datacenter environment, affecting customer virtual machines, storage arrays, and network connectivity. Initial indicators suggested a complex multi-layered hardware, power, or storage failure. However, as troubleshooting progressed, telemetry revealed suspicious activity on a dedicated storage/management server. Subsequ

2. 2026-07-23T14:44:23.262-05:00 · resolved

   Our team has completed the recovery efforts related to the ransomware incident that affected a portion of our hosted environment. All customer environments have now been restored to operational status. We have continued to validate the restored systems to confirm they are stable, complete, and safe to return to production. In parallel, our security investigation and infrastructure review remain ongoing. Based on the evidence reviewed to date, we have found no indication that customer data was c

3. 2026-07-15T14:54:10.033-05:00 · monitoring

   Service Recovery Update Our team continues to work through the remaining recovery efforts related to the ransomware incident affecting a portion of our hosted environment. The majority of customer systems have now been restored and returned to service. We are continuing to work directly with a small number of customers whose systems require additional recovery, validation, or rebuilding. For those remaining environments, our engineers are reviewing all available backups, storage snapshots, vi

4. 2026-07-14T16:14:12.907-05:00 · monitoring

   What Happened An unauthorized third party gained access to an externally accessible system within our data center environment and deployed ransomware that affected a portion of our hosted virtual infrastructure. Once the activity was identified, we contained the affected systems and immediately began our incident response and recovery process. Our investigation into the exact method of initial access is still ongoing. While that investigation and the related remediation work continue, we are

5. 2026-07-13T08:21:26.562-05:00 · identified

   We have restored connectivity for the majority of our clients and virtual machines, and the environment continues to stabilize. Our teams remain actively engaged in resolving the remaining issues. At this time, we are still seeing isolated pockets of network configuration issues affecting a subset of customer environments, along with a number of individual servers that require additional attention. As we work through the recovery process, we continue to encounter small, one-off issues affecting

6. 2026-07-12T23:58:21.412-05:00 · investigating

   We have restored connectivity for the majority of our clients and virtual machines. Our teams are continuing to trace and resolve the remaining network issues so that the rest of the affected environments can be brought back online. We remain actively engaged in the restoration process and will continue to provide updates as additional progress is made.

7. 2026-07-12T20:39:28.144-05:00 · investigating

   We are continuing to restore client systems, with additional customers being brought back online on an ongoing basis. During the recovery process, we identified an issue affecting our virtual networking infrastructure that requires us to manually rebuild customer WAN configurations. Our teams have been working continuously throughout the weekend and will remain engaged through the night to restore connectivity for as many customers as possible before Monday morning. We sincerely apologize for

8. 2026-07-12T10:56:04.458-05:00 · investigating

   Customer environments operating behind our physical networking infrastructure have been brought back online. We are continuing to repair and validate the virtual networking configurations. We anticipate completing the virtual networking restoration today, after which we can begin bringing the virtual machines connected to those networks back online in a controlled manner. We appreciate your continued patience and will provide additional updates as restoration progresses.

9. 2026-07-11T21:38:29.828-05:00 · investigating

   We are currently bringing customer environments back online in a controlled and measured manner. This process is proceeding as planned, but it will take time to complete as we carefully manage the workload to avoid overloading the storage arrays. Our teams are actively monitoring the environment throughout the recovery process. We will continue to provide updates as additional customer environments are restored and progress is made.

10. 2026-07-11T05:14:27.641-05:00 · investigating

    Hello Partners, I want to provide a continued update regarding the outage affecting one of our data center environments and the progress of our recovery efforts. Our teams have remained fully engaged throughout the recovery process. We have now restored approximately 120 TB of data from July 9 and approximately 30 TB of data from July 10. All restored volumes and data are currently showing as healthy through our validation processes, and we remain actively engaged in continued data validation

11. 2026-07-10T20:37:51.404-05:00 · investigating

    Our recovery efforts are continuing and will remain active throughout the night as data restoration progresses. To support validation, we performed immediate volume recoveries into isolated environments. These recovered volumes have now been running for several hours with a limited number of isolated virtual machines powered on for testing. We have also cloned selected environments and data from test systems to further validate stability and integrity. The next stages of recovery will include

12. 2026-07-10T16:34:30.842-05:00 · investigating

    Hello Partners, I want to personally provide an update regarding the major outage affecting one of our data center environments. I also want to be as clear and transparent as possible about the situation and the recovery work currently underway. Early this morning, we identified multiple servers that had lost network connectivity. We immediately engaged both the data center’s network engineering team and our internal network engineering team to begin investigating. Throughout the day, we have

Product match: components.

Read the provider’s incident report

1. 2026-04-30T22:31:46.490-05:00 · resolved

   This incident has been resolved.

2. 2026-04-30T22:31:29.589-05:00 · identified

   We are continuing to work on a fix for this issue.

3. 2026-03-31T06:34:48.165-05:00 · identified

   We understand the impact this issue is having and sincerely appreciate your patience. We are actively reaching out to the assigned engineer and their management team to obtain further clarification and a clearer understanding of the current status and next steps.

4. 2026-03-30T20:58:54.692-05:00 · identified

   We apologize for the delay in communication as we have been actively working to escalate this issue. The case has now been escalated, and a senior network engineer is engaged and reviewing the situation. Recent remediation efforts and repair attempts have not yet resolved the problem. The engineering team continues to perform in-depth analysis to identify the root cause and determine the appropriate corrective actions. We will continue to provide updates as more information becomes available.

5. 2026-03-30T19:00:09.783-05:00 · identified

   We have spoken with the datacenter network engineering team again and are actively working to escalate the case for deeper investigation. The engineering team is currently performing detailed log analysis across the networking stack and has already initiated resets on key networking components as part of their troubleshooting process. Initial observations indicate that packets are successfully entering the network and egressing from upstream interfaces; however, traffic appears to be dropped or

6. 2026-03-30T18:10:29.162-05:00 · identified

   We are continuing to troubleshoot with the datacenter network engineering team. We concluded a call with them approximately 15 minutes ago, and they are actively working to resolve the issue. We expect an update from their troubleshooting efforts within the next 30 minutes.

7. 2026-03-30T17:09:25.571-05:00 · identified

   We are continuing to work with the datacenter networking team to resolve this issue. The team is actively troubleshooting, and we are currently awaiting confirmation and an estimated time to resolution. We are also on a live call with an engineer to review their findings and analyze the available data.

8. 2026-03-30T16:17:17.253-05:00 · identified

   The network engineer has confirmed that traffic flow is currently disrupted on the affected baremetal servers. Incoming, as well as outgoing traffic is currently being dropped. He is continuing to investigate to find the root cause and has engaged an additional team member from the datacenter networking team to get this issue resolved.

9. 2026-03-30T15:47:48.779-05:00 · identified

   The datacenter engineer has determined that the issue is network related and has escalated the ticket to the datacenter network engineering team. A network engineer has been assigned and is currently collecting network traffic logs for the affected bare metal servers. Once the collection of logs is completed, he will be reviewing the logs as well as real time traffic in order to identify the underlying cause.

10. 2026-03-30T15:15:03.077-05:00 · investigating

    A datacenter engineer has been assigned to the ticket and he is currently reviewing and troubleshooting the issue.

11. 2026-03-30T14:48:44.314-05:00 · investigating

    A ticket was opened with the datacenter team after we confirmed we could not access the affected bare metal servers. We are currently awaiting an engineer to be assigned to this ticket to troubleshoot the issue.

12. 2026-03-30T14:24:43.511-05:00 · investigating

    We have received an automated alert from our monitoring system notifying us of an issue reaching certain Baremetal servers. We are reviewing this alert and are engaging with the datacenter team.

Product match: components.

Read the provider’s incident report

1. 2026-03-20T14:21:20.000-05:00 · resolved

   This incident has been resolved.

2. 2026-03-17T19:21:13.090-05:00 · identified

   We have received confirmation that data collection for our environment has now been completed. The engineering teams are currently reviewing the collected data and analyzing the packet captures in detail. At the same time, they are continuing to gather information from one additional affected client to help build a more complete picture of the issue. At this stage, one of the working theories is that this may be related to an internal system automation that could be contributing to the problem.

3. 2026-03-17T17:47:34.158-05:00 · identified

   We have received an update from the data center engineering team indicating that they are close to completing the collection of troubleshooting data for one affected client, after which our environment will be next in line for analysis. They will be gathering detailed data from our systems to support further investigation into the issue. At this time, there is no estimated timeline for resolution. The teams are focused on collecting and analyzing the necessary information to better understand t

4. 2026-03-17T16:59:54.573-05:00 · identified

   We have just spoken with the engineer currently assigned to our ticket at the data center. The issue is being actively worked on in close coordination with the data center cloud team. At this stage, the data center team is performing packet captures and investigating the behavior across multiple locations. The next step in their process is to closely review and troubleshoot the packets being routed out of our bare metal environments. Based on what is known so far, there is a working theory tha

5. 2026-03-17T16:03:10.100-05:00 · investigating

   Our engineering team is still currently investigating a significant issue affecting three of our bare metal environments located in Chicago, Ashburn, and Phoenix. At this time, all three locations are experiencing downtime. Initial findings indicate this may be part of a broader issue affecting multiple accounts, likely related to how intermediary virtual traffic tagging is handled across data centers. We recently completed a call with our Tier 2 engineering team and they are now working closel

6. 2026-03-17T14:42:15.863-05:00 · investigating

   The tier 2 datacenter networking team is still working on identifying and resolving the root cause affecting the three bare metal servers. At the time of writing, we do not yet have an exact root cause. Once the exact cause has been identified, this incident will be updated with the relevant details and the steps taken to resolve the issue.

7. 2026-03-17T13:26:25.208-05:00 · investigating

   Our investigation into this issue is still ongoing. Our support ticket regarding this issue has been escalated to Tier 2 of the datacenter networking team and we are actively working with them in order to resolve the ongoing connectivity issue affecting three bare metal servers. The datacenter team is currently attempting to identify the exact cause of this outage. Once we have confirmation on the exact cause of the outage and the next steps, this incident will be updated with those details.

8. 2026-03-17T12:30:56.190-05:00 · investigating

   We are continuing to investigate this issue alongside the datacenter engineers. We have confirmed that three separate bare-metal servers are currently impacted by the connectivity issue and that the issue does not appear to be caused by any hardware located on the servers themselves. Additional updates will follow as soon as they become available.

9. 2026-03-17T11:44:07.053-05:00 · investigating

   We are receiving reports of some clients on Baremetal servers experiencing connectivity issues. We are working with the datacenter engineers at this time to isolate and resolve this as quickly as possible.

Product match: components.

Read the provider’s incident report

1. 2026-03-09T17:55:33.000-05:00 · resolved

   This incident has been resolved.

2. 2026-03-09T12:43:54.909-05:00 · monitoring

   We have identified the networking issue in cooperation with the datacenter and have implemented a fix for this. We are seeing connectivity being restored at this time and expect everything to be back online within the next few minutes.

3. 2026-03-09T12:20:29.661-05:00 · investigating

   We are currently coordinating with the datacenter team to troubleshoot the issue. We were able to gain access through out-of-band management and are investigating the cause of the WAN side remaining down. We are still actively working on resolving the issue and will provide updates as we learn more.

4. 2026-03-09T12:03:01.121-05:00 · investigating

   We are continuing to work with datacenter engineers at this time to identify and isolate the cause of the issue. We will provide updates as they become available.

5. 2026-03-09T11:39:13.197-05:00 · investigating

   We are receiving reports of an outage at our ELK Datacenter. We are working with Datacenter Engineers to isolate the cause of the issue and get it resolved as quickly as possible. We will update this status as information becomes available.

Product match: components.

Read the provider’s incident report

1. 2026-02-24T12:28:45.000-06:00 · resolved

   This incident has been resolved.

2. 2026-02-22T16:57:35.016-06:00 · monitoring

   At this time, the servers have been rebooted and are returning to normal. We are continuing to monitor for ongoing issues. If you continue to experience issues, please submit a ticket to support@adeptcloud.net.

3. 2026-02-22T16:32:28.733-06:00 · identified

   We have identified the issue to be related to one of our hosts inside of the PHX datacenter. We initiated a reboot and the server is now back online. We will begin the process of rebooting all of the VM's in a staggered manner in order to make sure all of the servers come up in the proper order for Horizon functionality. This could take some time and we will update this status page once the process has been completed.

4. 2026-02-22T16:24:43.585-06:00 · investigating

   We are receiving reports of an outage at our PHX location. This appears to be isolated to certain VM's and we are investigating this internally and with the datacenter. We will provide updates as information becomes available.

Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-10-20T22:16:38.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-19T22:10:00.000Z to 2026-10-20T22:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Adeptcore feature.

The latest status observation was 2026-10-20T22:03:51.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save Adeptcore in this browser’s watchlist, then return to compare its status with other saved services. The watchlist does not send notifications. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.