Baremetal Alert
Update - 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.
Mar 31, 2026 - 06:34 CDT
Update - 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.
Mar 30, 2026 - 20:58 CDT
Update - 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 not properly forwarded at an intermediate point in the path. The team is analyzing potential causes, including routing inconsistencies, firewall or ACL enforcement, and possible issues within the switching fabric.

At this time, the team is continuing to trace packet flow across the network path to identify the exact point of failure and determine root cause. We will provide further updates as additional data becomes available.
Mar 30, 2026 - 19:00 CDT
Update - 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.
Mar 30, 2026 - 18:10 CDT
Update - 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.
Mar 30, 2026 - 17:09 CDT
Update - 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.
Mar 30, 2026 - 16:17 CDT
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.
Mar 30, 2026 - 15:47 CDT
Update - A datacenter engineer has been assigned to the ticket and he is currently reviewing and troubleshooting the issue.
Mar 30, 2026 - 15:15 CDT
Update - 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.
Mar 30, 2026 - 14:48 CDT
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.
Mar 30, 2026 - 14:24 CDT

About This Site

Welcome to Adeptcore, Inc. home of the Adeptcloud. Our status page was designed to give you a quick glance at our commitment to keeping you and your clients running.

Uptime over the past 90 days. View historical uptime.
Adeptcloud Infrastructure Degraded Performance
90 days ago
98.87 % uptime
Today
ACP - Network Degraded Performance
90 days ago
95.57 % uptime
Today
ACP - Storage Operational
90 days ago
100.0 % uptime
Today
ACP - Nodes Operational
90 days ago
99.94 % uptime
Today
ACP - Power Operational
90 days ago
100.0 % uptime
Today
Cloud-Hosted Operational
90 days ago
100.0 % uptime
Today
ACP - Cloud-Hosted Operational
90 days ago
100.0 % uptime
Today
Third Party Tools Operational
Zoom Zoom Cloud Room Connector Operational
Zoom Zoom Software Operational
Zoom Zoom Meetings Operational
mailgun Inbound email processing Operational
mailgun SMTP Operational
mailgun Events & Logs Operational
PagerDuty Notification Delivery Operational
PagerDuty Web Application Operational
PagerDuty REST API Operational
PagerDuty Webhooks Operational
Third Party Service Advisories Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Apr 1, 2026

No incidents reported today.

Mar 31, 2026

Unresolved incident: Baremetal Alert.

Mar 30, 2026
Mar 29, 2026

No incidents reported.

Mar 28, 2026

No incidents reported.

Mar 27, 2026

No incidents reported.

Mar 26, 2026

No incidents reported.

Mar 25, 2026

No incidents reported.

Mar 24, 2026

No incidents reported.

Mar 23, 2026

No incidents reported.

Mar 22, 2026

No incidents reported.

Mar 21, 2026

No incidents reported.

Mar 20, 2026
Baremetal Connectivity Issues
Resolved - This incident has been resolved.
Mar 20, 14:21 CDT
Update - 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. This remains one of two primary areas of focus as the investigation continues.

In parallel, a support ticket has been opened with the vendor responsible for routing and switching, and the matter is being actively escalated to ensure additional expertise is brought in.
Mar 17, 19:21 CDT
Update - 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 the exact nature of the incident and to evaluate the most effective path forward.
Mar 17, 17:47 CDT
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 that the packets may contain malformed headers, which could be preventing them from routing correctly across the virtualized LAN layer. This appears to be a complex issue, and the teams involved are carefully analyzing the situation to better understand the root cause.

In parallel, the data center team is also opening a support ticket with the hardware vendor on their end to bring in additional expertise and help accelerate the resolution.
Mar 17, 16:59 CDT
Update - 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 closely with the data center cloud team to conduct a deeper analysis and move toward implementing a resolution as quickly as possible.

At this time, our colocation and other services remain operational and unaffected. However, we are observing an impact to network connectivity between our colocation environment and the affected bare metal datacenters, which is contributing to the overall disruption.
Mar 17, 16:03 CDT
Update - 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.
Mar 17, 14:42 CDT
Update - 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.
Mar 17, 13:26 CDT
Update - 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.
Mar 17, 12:30 CDT
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.
Mar 17, 11:44 CDT
Mar 19, 2026

No incidents reported.

Mar 18, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage