Loading story…
A cooling-system failure at a colocated data center in Phoenix, Arizona triggered a broad service outage that disrupted infrastructure used by Namecheap and MX Guarddog, knocking multiple customer-facing platforms offline. MX Guarddog reported critical temperatures and loss of connectivity at its primary facility, told customers it had no estimated restoration time, and advised them to temporarily repoint MX records directly to their own mail servers to bypass the outage.
Namecheap said the same facility incident affected shared hosting, VPS hosting, dedicated servers, EasyWP, Private Email, parts of DNS management, its website, and support systems, with recovery carried out in phases as cooling capacity and core infrastructure were restored. By the following day, the company reported substantial recovery across most services, including about 97% of affected VPS hosting, 85% of shared hosting, 90% of dedicated servers, and 80% of EasyWP, while some delayed email and customer-specific issues persisted; available reporting indicated an environmental infrastructure failure rather than a cyberattack.
See attribution, scope, and your downstream exposure.
5 events from the most recent confirmed update back to the earliest known activity.
By August 14, Namecheap said most affected services had substantially recovered, including 97% of impacted VPS hosting, about 85% of shared hosting, around 90% of dedicated servers, roughly 80% of EasyWP, and restored Private Email. The company noted some delayed messages and customer-specific outages could remain.
On August 13, Namecheap experienced a major outage after a cooling infrastructure failure at the PhoenixNAP data center in Phoenix caused elevated temperatures and forced affected systems offline to prevent hardware damage. The disruption affected hosting, email, DNS management, Namecheap.com, and support systems.
As recovery progressed, Namecheap directed customers to Microsoft Teams because its normal helpdesk was unavailable and restored services in stages, starting with physical and virtual network devices and core infrastructure. The company also reported two of four chillers back online and temporary cooling capacity installed while repairs continued.
During the MX Guarddog outage, the company advised customers who could do so to change MX records to point directly to their own mail servers to bypass the disruption. A customer reported not receiving emails since 5 AM PST.
MX Guarddog reported a large-scale outage after its primary colocated data center in Phoenix, Arizona suffered a total cooling-system failure, leading to critical temperatures and loss of connectivity. The company said it had no ETA for restoration.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A series of high-profile cloud outages disrupted access to critical services across multiple sectors, affecting organizations such as Starbucks, crypto exchanges, and messaging platforms like Signal. The Amazon Web Services (AWS) outage, triggered by a software bug in DynamoDB, led to a 15-hour disruption in Northern Virginia data centers, while a subsequent Microsoft Azure outage was caused by a configuration error in Azure Front Door. These incidents exposed the fragility of digital infrastructure and raised concerns about the concentration of power among a few dominant cloud providers, prompting advocacy groups to call for increased regulatory scrutiny. The outages also underscored the essential role of DNS in business continuity, as failures in DNS resolution prevented customers and internal services from accessing critical database resources. Experts emphasized that DNS, as the foundational protocol for translating domain names to IP addresses, can create widespread disruptions when it fails, regardless of the underlying cause. The events reignited discussions about the need for greater resilience in both cloud and DNS infrastructure to mitigate the impact of future outages on businesses and the broader digital ecosystem.
Jul 3, 2026
Microsoft reported multiple **service-impacting incidents** across its cloud ecosystem. Administrators in **North America and Canada** experienced an outage and degraded performance in the **Microsoft 365 admin center**, with some users also unable to access the *M365 app* or raise support tickets; Microsoft said it was analyzing telemetry, usage patterns, and **CPU utilization**, and reviewing user-provided **HAR files** to isolate the root cause. Separately, **Exchange Online** quarantined legitimate messages after an updated **URL rule** incorrectly marked some URLs as phishing, disrupting email flow for affected customers while Microsoft worked to release quarantined mail and unblock legitimate URLs. In another disruption, Microsoft attributed **Windows Update** and **Microsoft Store** failures/timeouts (notably impacting Windows 11 users) to a **utility power interruption** at a **West US datacenter**, which cascaded into issues with **Azure storage clusters** supporting content delivery; backup power engaged and power was later stabilized, but service recovery required additional remediation beyond restoring electricity.
Jun 29, 2026
Microsoft reported a **Microsoft 365 service disruption in North America** that affected access to multiple services, including the **Microsoft 365 Admin Center**, limiting administrators’ ability to manage users and view service health/security posture. Microsoft’s investigation, tracked via the Microsoft 365 admin center and service health communications, pointed to a likely **Content Delivery Network (CDN) configuration issue** as the root cause, with engineers iterating through telemetry review and narrowing the suspected trigger to CDN configuration. Amazon also experienced a **partial outage** affecting customer shopping workflows, with widespread user reports of problems loading product pages, using the mobile app, and especially **checkout/add-to-cart** functionality across major US cities. Amazon acknowledged the disruption publicly and stated it was working to resolve the issue, while the underlying cause was not yet confirmed at the time of reporting.
Jun 29, 2026