Atlantic.Net Outage History

Started Sep 14, 2026, 05:56 PM UTC· resolved Sep 16, 2026, 06:55 PM UTC

1. monitoring Sep 14, 2026, 05:56 PM UTC

   Microsoft has confirmed an issue with its September 2026 Windows Security Updates that may cause Remote Desktop Services (RDS) to become unstable or stop responding on affected Windows Servers. Symptoms may include failed RDP connections, sign-in issues, or servers becoming unresponsive after the update is installed. This issue originates with the Microsoft security update and is currently pending remediation from Microsoft. Atlantic.Net is unable to correct the underlying issue or provide a permanent resolution. For customers with Managed Hardware or Services, Atlantic.Net Support can reboot an affected server upon request. A reboot may temporarily restore RDP functionality, but it does not resolve the underlying issue and the problem may recur. Please see our contact info below to request a reboot. Note that customers with On-Demand Cloud VMs can perform a reboot of their VM through the Cloud Control Panel if needed. See here for instructions: https://www.atlantic.net/vps-hosting/atlantic-net-cloud-how-to-soft-or-hard-reboot-a-atlantic-net-cloud-server/ Microsoft is actively working on a permanent resolution and has not yet provided a release date. We will continue to monitor Microsoft's updates and provide additional information as it becomes available. Support Contact Info Email: [email protected] Toll-Free: 1-888-618-DATA (3282) International: +1-321-206-3734

2. resolved Sep 16, 2026, 06:55 PM UTC

   Microsoft has released the following resolution statement: "This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129195. We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one." For more information, please see: https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5124008-windows-11-24h2-25h2-security-update

Read the full incident report →

Started Jul 08, 2026, 10:15 PM UTC· resolved Jul 08, 2026, 10:55 PM UTC

1. identified Jul 08, 2026, 10:15 PM UTC

   This incident only pertains to some customers with cPanel/WHM servers. cPanel has reported an issue that is preventing licenses from updating, which may impact some users' access to WHM/cPanel web GUI. We are currently monitoring the situation, and direct updates from cPanel can be found here: https://support.cpanel.net/hc/en-us/articles/41816676353943-cPanel-License-Update-Failures-July-7th-2026

2. resolved Jul 08, 2026, 10:55 PM UTC

   More information can be found here: https://support.cpanel.net/hc/en-us/articles/41816676353943-cPanel-License-Update-Failures-July-8th-2026 If needed, please SSH into your server (or console into it) and run: /usr/local/cpanel/cpkeyclt

Read the full incident report →

Started Apr 30, 2026, 07:47 PM UTC· resolved May 01, 2026, 06:45 AM UTC

1. monitoring Apr 30, 2026, 07:47 PM UTC

   We are aware of a network-level issue that caused connectivity issues for some customers in the Dallas data center. We have identified and resolved the issue and are continuing to monitor the situation. We will provide more information to affected customers as we gather more details.

2. resolved May 01, 2026, 06:45 AM UTC

   This incident has been resolved.

3. postmortem May 07, 2026, 05:16 AM UTC

   **Location:** DAL2 \(Dallas Data Center\) **Date:** April 30, 2026 **Summary** On April 30, 2026, [Atlantic.Net](http://Atlantic.Net) experienced a service disruption within the DAL2 network infrastructure due to a **Distributed Denial of Service \(DDoS\) attack**. The attack resulted in intermittent connectivity and service degradation for affected customers. The incident was promptly detected by monitoring systems and escalated to the Network Engineering team, who initiated mitigation procedures. Full service restoration was achieved within 28 minutes of the initial impact. **Incident Timeline** **Total Outage Duration:** 28 Minutes **Customer Impact \(SLA\):** 28 Minutes **Impact** * Customers hosted within the DAL2 environment experienced: * Network latency * Packet loss * Intermittent or complete loss of connectivity * The impact duration varied but did not exceed the total outage window of 28 minutes. **Root Cause** The outage was caused by a **Distributed Denial of Service \(DDoS\) attack** targeting [Atlantic.Net](http://Atlantic.Net)’s DAL2 network infrastructure. The volume and nature of malicious traffic temporarily overwhelmed network resources, resulting in degraded performance and partial service disruption. **Detection** The event was identified through: * Automated alerts from **Network Monitoring Services \(NMS\)** * Customer-reported issues via support tickets and inbound calls **Mitigation and Resolution** Upon escalation, the Network Engineering team performed the following actions: * Analyzed inbound traffic patterns to identify malicious sources * Implemented traffic filtering and mitigation controls * Applied rate limiting and/or upstream filtering where applicable * Stabilized affected network segments These actions successfully mitigated the attack and restored normal network operations by 15:40 EST. **Conclusion** This incident was the result of an external malicious DDoS attack. [Atlantic.Net](http://Atlantic.Net)’s monitoring and response procedures enabled rapid identification and mitigation, limiting customer impact to 28 minutes. We remain committed to improving network resilience and minimizing the impact of similar events in the future.

Read the full incident report →

Started Apr 16, 2026, 05:31 AM UTC· resolved Apr 16, 2026, 10:13 AM UTC

1. identified Apr 16, 2026, 05:31 AM UTC

   A Cloud node in the San Francisco data center is currently experiencing unexpected issues which our Cloud Operations team is working to resolve. Virtual machines hosted on the associated node may be affected at this time. We will continue to provide updates as we work toward resolution. Please direct all questions to [email protected]. Thank you for your patience.

2. identified Apr 16, 2026, 06:20 AM UTC

   Our Cloud engineers are continuing to work diligently to return the Cloud node to full functionality. Further updates will be provided as soon as they are available. Thank you for your continued patience.

3. identified Apr 16, 2026, 08:01 AM UTC

   Our Cloud engineers have determine that the Cloud node hardware is not able to be restored to a working state. As such, backups of individual servers affected by this incident will be restored to working nodes at the location. Backups from the following date and time will be used: Wednesday, 4/15/2026, at 6:00PM Eastern Time Our engineering team will continue to investigate the failure in an effort to perform data recovery for any affected VMs. If your services were affected by this incident, you will receive a separate email from our Support team with more information.

4. identified Apr 16, 2026, 09:31 AM UTC

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

5. identified Apr 16, 2026, 09:33 AM UTC

   Our Cloud engineers are still working on restoring servers impacted by this incident. You may observe your services have been restored to the date and time outlined previously. Remaining impacted servers are expected to be restored shortly.

6. resolved Apr 16, 2026, 10:13 AM UTC

   Our Cloud engineers have completed the restoration of all impacted servers to the date and time below. If your server was impacted, you will receive an email from our Support team with further information. This incident has been resolved.

7. postmortem Apr 28, 2026, 07:46 AM UTC

   ## Incident Summary On April 16, 2026, at approximately **1:17 AM ET**, the Cloud Host supporting one or more of your services experienced a critical shutdown due to a hardware failure. This resulted in an unplanned service interruption for the affected servers. Our investigation began immediately at approximately **1:17 AM ET**. After determining that the incident was caused by a critical hardware failure, our Engineering team began recovery efforts using available VM backups at approximately **4:00 AM ET**. All affected servers were restored from the most recently available backup, dated **Wednesday, April 15, 2026, at 6:00 PM ET**. Services were fully restored for all affected servers by approximately **6:00 AM ET**, resulting in a total service interruption of approximately **5 hours and 43 minutes**. Actual downtime may vary by server, as some affected servers were restored earlier than others. ## Root Cause Our investigation determined that the interruption was caused by a hardware failure involving the **storage drive backplane** within the affected Cloud Host. This failure caused the host to stop recognizing the installed storage drives, which resulted in the hypervisor crashing and the affected Cloud services becoming unavailable. ## Immediate Actions Taken To reduce the risk of further disruption, the affected host was removed from active service and marked so that no additional servers could be created on, or migrated to, that system. To restore service as quickly as possible, our Engineering team restored the affected servers from the most recently available backups and brought them online on known-good Cloud Hosts. ## Preventative Measures Our Engineering team will fully service and evaluate the affected host before it is considered for any future production use. No customer workloads will be returned to this system unless and until the evaluation is complete and the host is confirmed fit for continued production operation. We apologize for the disruption this incident caused and appreciate your patience, understanding, and continued trust.

Read the full incident report →

Started Apr 02, 2026, 05:50 PM UTC· resolved Apr 03, 2026, 04:20 AM UTC

1. identified Apr 02, 2026, 05:50 PM UTC

   A Cloud node in the Orlando data center is experiencing unexpected issues which our Cloud Operations team is currently working to resolve. Virtual machines hosted on the relevant node may be affected at this time. We will continue to provide updates as we work toward resolution. Please direct all questions to [email protected].

2. monitoring Apr 02, 2026, 06:04 PM UTC

   The affected Cloud node is now stable. Virtual machines hosted on the relevant node should be online and accessible. We will continue to monitor the node and provide updates as our Cloud Operations team investigates. Please direct all questions to [email protected].

3. resolved Apr 03, 2026, 04:20 AM UTC

   This incident has been resolved.

4. postmortem Apr 06, 2026, 11:20 AM UTC

   **Incident Summary** On April 2, 2026, at approximately 1:20 PM, the Cloud Host supporting one or more of your services experienced an unexpected shutdown, resulting in an unplanned service interruption. The initial outage lasted approximately 15 minutes, with an additional 14 minutes required for service startup and recovery. Services were fully restored by 1:49 PM, for a total interruption of approximately 29 minutes. **Root Cause** Our investigation determined that the interruption was caused by a hardware failure involving a RAM module within the affected Cloud Host. This failure caused the host to crash unexpectedly. **Immediate Actions Taken** To restore service as quickly as possible, our team performed a full reboot of the affected host. Once services were restored, we began a live evacuation of workloads from the host to reduce the risk of any further disruption while additional remediation efforts are completed. **Preventative Measures** Our Engineering team will fully service and evaluate the affected host following the hardware failure. No workloads will be returned to this system unless and until that evaluation is completed and the host is confirmed fit for continued production use.

Read the full incident report →

Started Mar 13, 2026, 02:08 PM UTC· resolved Mar 17, 2026, 11:37 AM UTC

1. identified Mar 13, 2026, 02:08 PM UTC

   We are aware of a recurrence in carrier transport issues in the region that is causing connectivity issues for Cloud and Dedicated services. We are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud and Dedicated servers are inaccessible while our team works to resolve the issue. We sincerely appreciate your patience.

2. identified Mar 13, 2026, 02:14 PM UTC

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

3. identified Mar 13, 2026, 02:43 PM UTC

   We are continuing to work closely with our upstream provider on a fix to restore network connectivity. We will continue to provide further updates as they become available. We sincerely appreciate your continued patience.

4. monitoring Mar 13, 2026, 03:34 PM UTC

   Network connectivity has been restored and affected services are returning to normal operation. We are continuing to monitor the environment closely with our upstream provider to confirm ongoing stability. Once our review is complete, we will provide a full Reason for Outage (RFO). We will continue to share updates as they become available. We sincerely appreciate your continued patience.

5. resolved Mar 17, 2026, 11:37 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 25, 2026, 07:29 PM UTC· resolved Feb 26, 2026, 01:01 PM UTC

1. investigating Feb 25, 2026, 07:29 PM UTC

   We are currently investigating reports of elevated latency and packet loss impacting a portion of our network traffic traversing one of our upstream transport providers. Our Network Operations team has identified abnormal performance metrics and is actively working to isolate the scope and impact. At this time, customers may experience intermittent latency or packet loss affecting connectivity to certain destinations. We have engaged with the transport provider and will provide updates as more information becomes available.

2. resolved Feb 26, 2026, 01:01 PM UTC

   The transport provider has confirmed resolution of the underlying issue, and network performance has returned to normal operating levels. We will continue to monitor proactively, but at this time the incident is considered resolved.

Read the full incident report →

Started Jan 09, 2026, 02:34 PM UTC· resolved Jan 09, 2026, 04:59 PM UTC

1. investigating Jan 09, 2026, 02:34 PM UTC

   We are currently investigating an issue that is affecting services in the Orlando region. We will continue to provide updates as we learn more about the issue.

2. investigating Jan 09, 2026, 02:36 PM UTC

   Our phone systems may be unreachable at this time. If you require assistance, please send an email to [email protected].

3. identified Jan 09, 2026, 03:08 PM UTC

   We have identified the root cause of the issue as a result of instability from one of our upstream carriers. We are currently working closely with them to resolve the issue. You may experience periods where your services are inaccessible while our team works to resolve the issue. We will post further updates as we have more information available.

4. monitoring Jan 09, 2026, 03:47 PM UTC

   Connectivity in the Orlando region has returned to normal. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

5. resolved Jan 09, 2026, 04:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 17, 2025, 04:49 PM UTC· resolved Dec 17, 2025, 08:13 PM UTC

1. investigating Dec 17, 2025, 04:49 PM UTC

   We are currently experiencing issues affecting Cloud services in the London data center. This may result in impaired performance for services in that data center, and you may experience periods where your Cloud Servers are inaccessible as a result. Our Cloud Operations team is actively working to identify the root cause and restore normal performance as quickly as possible.

2. investigating Dec 17, 2025, 05:21 PM UTC

   We are continuing to investigate this issue.

3. resolved Dec 17, 2025, 08:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 08, 2025, 02:44 PM UTC· resolved Dec 08, 2025, 11:00 PM UTC

1. identified Dec 08, 2025, 02:44 PM UTC

   We are currently experiencing transoceanic network transport issues affecting connectivity between the USA and Singapore. This may result in increased latency, intermittent timeouts, or reduced performance for services relying on this route. You may experience periods where your Cloud Servers are inaccessible as a result. Our network operations team is actively working with our upstream providers to identify the cause and restore normal performance as quickly as possible.

2. resolved Dec 09, 2025, 07:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 11:26 PM UTC· resolved Dec 06, 2025, 02:35 AM UTC

1. identified Dec 05, 2025, 11:26 PM UTC

   We are experiencing a switch failure, and our Network Engineering Team is working to mitigate it.

2. monitoring Dec 05, 2025, 11:40 PM UTC

   A fix to the switch has been implemented, and we are currently monitoring for system stability.

3. resolved Dec 06, 2025, 02:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 21, 2025, 07:17 AM UTC· resolved Nov 21, 2025, 10:21 AM UTC

1. identified Nov 21, 2025, 07:17 AM UTC

   We are aware of potential carrier transport issues in the region that is causing higher-than-normal levels of packet loss for services. We are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud Servers are intermittently accessible while our team works to resolve the issue.

2. monitoring Nov 21, 2025, 08:24 AM UTC

   Network connectivity issues in the NYC (New York) region have been mitigated. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

3. resolved Nov 21, 2025, 10:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 12:17 PM UTC· resolved Nov 19, 2025, 02:45 AM UTC

1. identified Nov 18, 2025, 12:17 PM UTC

   We have been made aware that access to our various web portals have been impacted by the Cloudflare Service outage. During this time, you may observe intermittent availability of the following portals as a result: https://atlantic.net/ https://cloud.atlantic.net/ https://helpdesk.atlantic.net/ You may also observe difficulties while provisioning servers via the Cloud API, hosted at https://cloudapi.atlantic.net/ We are currently awaiting further updates from Cloudflare regarding the incident and will provide updates via our status page at https://status.atlantic.net. You may also check Cloudflare's own status page for updates at https://www.cloudflarestatus.com/ Thank you, Atlantic.Net MSP Support Team Toll Free: 1-888-618-DATA (3282) International: +1-321-206-3734

2. resolved Nov 19, 2025, 02:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 11, 2025, 06:37 AM UTC· resolved Nov 11, 2025, 12:25 PM UTC

1. identified Nov 11, 2025, 06:37 AM UTC

   We are aware of potential carrier transport issues in these regions and are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud Servers are inaccessible while our team works to resolve the issue. We will post further updates as we have more information available.

2. monitoring Nov 11, 2025, 07:19 AM UTC

   We have found that the root cause of the connectivity issues reported previously was a carrier connection failure at our Orlando site. Connectivity in the Orlando (ORL) region has returned to normal. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

3. monitoring Nov 11, 2025, 07:34 AM UTC

   We have found that the root cause of the connectivity issues reported previously was a carrier connection failure at our Orlando site. Connectivity in the Orlando (ORL) region has returned to normal. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

4. resolved Nov 11, 2025, 12:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 07:59 PM UTC· resolved Nov 05, 2025, 01:44 AM UTC

1. investigating Nov 04, 2025, 07:59 PM UTC

   Status: Major Outage Started: Nov 04, 2025 14:08 EST Last update: Nov 04, 2025 14:55 EST Impact: Customers may be unable to reach Atlantic.Net Support by phone. Inbound calls may fail to connect; outbound callbacks may be delayed. Workarounds (please use these): Email: [email protected] (urgent tickets will be prioritized) For emergencies affecting production availability, include “SEV-1” in the email subject. We’ll post the next update by 15:30 EST or sooner if status changes.

2. identified Nov 04, 2025, 08:51 PM UTC

   Our phone provider has identified the issue and is in the process of implementing a fix, we'll provide an update as we have more details.

3. identified Nov 04, 2025, 09:55 PM UTC

   Work on this issue is still underway, we'll provide further updates as we receive them.

4. monitoring Nov 05, 2025, 12:32 AM UTC

   Phones have been restored, inbound and outbound calls are functioning; we are monitoring for stability and will post an additional update when we have confirmation that the issue is fully resolved. In

5. resolved Nov 05, 2025, 01:44 AM UTC

   Resolved — Nov 04, 2025 20:30 EST Phone service has been restored. Our provider implemented a fix for the registration issue, and inbound/outbound calls are operating normally. If you encounter any further problems, please email [email protected] .

Read the full incident report →

Started Oct 31, 2025, 06:42 AM UTC· resolved Oct 31, 2025, 09:52 AM UTC

1. identified Oct 31, 2025, 06:42 AM UTC

   We are aware of potential high packet loss due to carrier transport issues in this region and are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud Servers are inaccessible while our team works to resolve the issue. We will post further updates as we have more information available.

2. monitoring Oct 31, 2025, 07:06 AM UTC

   Network connectivity in the ASH (Ashburn) region has returned to normal after switching to the secondary carrier. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

3. monitoring Oct 31, 2025, 08:18 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 31, 2025, 09:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2025, 06:34 AM UTC· resolved Sep 30, 2025, 07:31 AM UTC

1. identified Sep 30, 2025, 06:34 AM UTC

   We are aware of potential high packet loss due to carrier transport issues in this region and are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud Servers are inaccessible while our team works to resolve the issue. We will post further updates as we have more information available.

2. monitoring Sep 30, 2025, 06:51 AM UTC

   Connectivity in the San Francisco (SFO) region has returned to normal. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

3. resolved Sep 30, 2025, 07:31 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 17, 2025, 01:54 PM UTC· resolved Sep 17, 2025, 04:55 PM UTC

1. investigating Sep 17, 2025, 01:54 PM UTC

   We are aware of potential carrier transport issues in this region and are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud Servers are inaccessible while our team works to resolve the issue. We will post further updates as we have more information available.

2. identified Sep 17, 2025, 03:00 PM UTC

   We have identified the root cause of this issue as a power failure at the facility in Clifton, NJ, affecting all carriers and services. Field operations are currently on-site working to restore power and service. Our Network Engineering and Management teams are continuing to communicate with carriers and facility operations regarding this incident. We will continue to provide updates as more information becomes available. We recommend directing all inquiries to [email protected], as phone lines are currently experiencing high volume. We appreciate your patience as we work toward resolution.

3. monitoring Sep 17, 2025, 03:24 PM UTC

   We have begun to observe service restoration in the region at this time. Our Network Engineering and Management teams are continuing to work closely with carriers and facility operations to ensure services are fully restored. We will continue to provide updates as more information becomes available. We appreciate your patience as we work toward resolution.

4. resolved Sep 17, 2025, 04:55 PM UTC

   We have confirmed continued stability over the past hour and can now confirm this outage is fully resolved. Our Network Engineering and Management teams are preparing a formal incident report, which will be shared with all affected customers. If you have any questions regarding this incident or any related concerns, please contact us at [email protected]. Thank you for your continued patience as we investigated this outage.

5. postmortem Oct 16, 2025, 07:41 AM UTC

   **NYC1 Data Center Power Outage — Incident Report** **Date:** September 17, 2025 \(EDT\) **Location:** NYC1 **Severity:** Severity 1 \(Critical\) **Impact:** Full site outage affecting access to all services in NYC1 **Measured outage duration:** 1 hour 28 minutes 36 seconds **Summary** At 09:34:24 EDT on September 17, 2025, our monitoring detected a loss of access to the NYC1 environment. Upstream carrier services feeding the site were unavailable, resulting in a site-wide outage. Service was restored at 11:03:00 EDT. We are awaiting the data center operator’s formal Reason for Outage \(RFO\). Preliminary provider updates indicate the event was related to a power issue within the facility that affected multiple carriers. **Timeline \(EDT\)** * **09:34:24** Detection by network monitoring * **09:42:24** Escalation initiated * **09:47:24** Incident acknowledged; mitigation started and coordinated bridge established * **11:03:00** Service restored **Customer Impact** * Access to NYC1 services was unavailable during the times above. * The SLA outage duration equals the full incident duration. **What We Did** * Activated our incident response and opened a live coordination bridge. * Engaged our carrier partners and the data center operator to confirm scope and restoration activities. * Provided periodic customer updates during the event window. * Verified recovery and confirmed service availability at resolution. **Current Status and Next Steps** * We are awaiting the facility operator’s formal RFO. Once received, we will share a summary of the findings and any confirmed contributing factors. * We are reviewing out-of-band access resiliency and evaluating additional diversity options for this footprint to reduce exposure to similar facility-level events. * We will update customers if any actions are required on your side. **Lessons Noted** * Early and steady communications are critical during facility-level events; we will continue to follow a consistent update cadence in similar incidents. * We are refining our first-hour response checklist to further standardize triage and external messaging. **Questions or Follow-Up** If you have questions about this incident or your specific services, please reply to this notice or contact Support through your usual channel. We will provide a customer summary of the facility RFO once it is available.

Read the full incident report →

Started Aug 26, 2025, 07:01 AM UTC· resolved Aug 26, 2025, 10:24 AM UTC

1. identified Aug 26, 2025, 07:01 AM UTC

   We are aware of potential carrier transport issues in this region and are currently working with our upstream carrier to resolve the issue. You may experience periods where your Cloud Servers are inaccessible while our team works to resolve the issue. We will post further updates as we have more information available.

2. identified Aug 26, 2025, 07:02 AM UTC

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

3. monitoring Aug 26, 2025, 07:20 AM UTC

   Connectivity in the San Francisco (SFO) region has returned to normal. All services are currently accessible, and we will continue to monitor for stability. We will continue to post further updates as necessary.

4. resolved Aug 26, 2025, 10:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 14, 2025, 08:58 PM UTC· resolved Aug 14, 2025, 11:00 PM UTC

1. monitoring Aug 14, 2025, 08:58 PM UTC

   We are aware of potential carrier transport issues in this region and are currently investigation the issue. We will post further updates as we have more information available.

2. monitoring Aug 14, 2025, 09:30 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Aug 14, 2025, 11:00 PM UTC

   Monitoring connectivity between remote probes and our Orlando core has been fully restored. All monitoring metrics are now reporting normally, and no further issues are expected.

Read the full incident report →

Started Jul 25, 2025, 04:45 PM UTC· resolved Jul 26, 2025, 05:30 AM UTC

1. identified Jul 25, 2025, 04:45 PM UTC

   ~~Incident Details~~ Location: Orlando, FL (USA-EAST-1) Services: Networking Impact: There is no impact to service. ~~Incident Summary~~ We are investigating a fiber outage that has reduced network redundancy in the Orlando data center. We have reached out to the relevant carrier to resolve this issue. There is no impact to service. ~~Customer Support~~ If you have any questions regarding this scheduled maintenance, please contact our Customer Support Department. Please note that as this affecting multiple customers, our phone lines may be busy at this time. Toll Free: (888)618-3282 International: +1-321-206-3734 Email: [email protected]

2. resolved Jul 28, 2025, 04:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 14, 2025, 02:57 PM UTC· resolved Jul 14, 2025, 08:54 PM UTC

1. identified Jul 14, 2025, 02:57 PM UTC

   Good morning, We are currently experiencing a major service disruption in the London region due to an outage affecting one of our upstream carriers. Our team has identified the issue and is actively working with the carrier to implement a resolution. We will continue to post updates as they become available at: https://status.atlantic.net We appreciate your patience and understanding as we work to restore full service. Atlantic.Net Support Toll-Free: 1-888-618-DATA (3282) International: +1-321-206-3734

2. identified Jul 14, 2025, 04:09 PM UTC

   Good morning, We are continuing to work closely with our upstream provider to implement the necessary changes and restore services as quickly as possible. Further updates will be posted at: https://status.atlantic.net We sincerely appreciate your continued patience and understanding as we work to fully resolve the issue. Atlantic.Net Support Toll-Free: 1-888-618-DATA (3282) International: +1-321-206-3734

3. identified Jul 14, 2025, 07:09 PM UTC

   Good afternoon, At this time, there is no change in service status. We remain in active communication with our upstream provider and are continuing efforts to fully restore service in the London region. We understand the impact this disruption may be having on your operations and want to assure you that resolving the issue remains our highest priority. Further updates will be posted at: https://status.atlantic.net Thank you again for your continued patience. Atlantic.Net Support Toll-Free: 1-888-618-DATA (3282) International: +1-321-206-3734

4. identified Jul 14, 2025, 08:54 PM UTC

   [Resolved] Services Restored – London Region Time: 4:29 PM EDT Good afternoon, Connectivity has been restored in the London region as of 4:29 PM EDT. Services impacted by the upstream provider outage are now fully operational. We will continue to monitor network stability and follow up with a full incident review and root cause analysis once available. Thank you for your patience and understanding throughout this incident. Atlantic.Net Support Toll-Free: 1-888-618-DATA (3282) International: +1-321-206-3734

5. resolved Jul 14, 2025, 08:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 20, 2025, 07:00 PM UTC· resolved Jun 20, 2025, 08:18 PM UTC

1. investigating Jun 20, 2025, 07:00 PM UTC

   We have had reports of network slowness and dropped connections at our Orlando facility. We are investigating.

2. monitoring Jun 20, 2025, 07:32 PM UTC

   We are still testing and monitoring the situation.

3. resolved Jun 20, 2025, 08:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 13, 2025, 04:40 PM UTC· resolved May 14, 2025, 06:24 AM UTC

1. investigating May 13, 2025, 04:40 PM UTC

   Atlantic.Net’s goal is to provide you with the most dependable and flexible hosting infrastructure in the industry. To ensure the most reliable service, we are notifying you of the below incident. ~~Maintenance Details~~ Location: Dallas, TX (USA-CENTRAL-1) Services: Cloud Impact: Customers may experience extreme latency on servers hosted in the Dallas data center. ~~Incident Summary~~ We are currently observing an outage that is affecting multiple Cloud customers in the Dallas data center. Our Cloud Operations team is actively investigating this issue and we will continue to update this status page as they work toward resolution. ~~Customer Support~~ If you have any questions regarding this scheduled maintenance, please contact our Customer Support Department. Please note that as this affecting multiple customers, our phone lines may be busy at this time. Toll Free: (888)618-3282 International: +1-321-206-3734 Email: [email protected]

2. monitoring May 13, 2025, 04:55 PM UTC

   The incident is resolved; however, the Cloud Operations team is still investigating the issue and we will continue to provide more details as we learn more.

3. monitoring May 13, 2025, 06:46 PM UTC

   Identified – Our Cloud Operations team has identified the root cause of the elevated latency experienced in our Dallas data center. The issue was related to an internal traffic filtering system that temporarily became inactive, allowing excess broadcast traffic to affect overall performance. To fully resolve this, we have a scheduled maintenance window this evening to implement a more robust filtering solution at the infrastructure level. Services remain stable at this time, and we are actively monitoring all systems to ensure continued performance. Additional details about the maintenance window will be shared shortly. We appreciate your patience and will continue to provide updates as we complete this corrective action.

4. resolved May 14, 2025, 06:24 AM UTC

   The incident has been resolved, and the cloud portion of the maintenance has been successfully completed. Changes were implemented to prevent this issue from recurring.

Read the full incident report →

Started May 08, 2025, 04:34 PM UTC· resolved May 08, 2025, 10:26 PM UTC

1. investigating May 08, 2025, 04:34 PM UTC

   There is a problem with networking on cloud servers in Dallas. We are investigating.

2. monitoring May 08, 2025, 05:14 PM UTC

   Everything appears to be functioning now. We are continuing to investigate the problem and monitor the situation.

3. resolved May 08, 2025, 10:26 PM UTC

   After several hours of monitoring, we can confirm that the issue has been fully resolved. All systems are operating normally.

Read the full incident report →