Microsoft is working to resolve an ongoing Exchange Online outage affecting customers throughout North America, blocking their access to emails.

“We’re investigating an issue affecting a portion of infrastructure in North America, where users may be unable to access their mailbox via any Exchange Online connection method,” the company explained earlier today.

According to user reports on DownDetector, the issue began impacting Microsoft’s customers more than six hours ago and is causing server connection problems, affecting users who attempt to log in to their accounts and access Teams, Outlook, and Hotmail.

While the root cause has yet to be determined and Microsoft hasn’t shared the number of customers affected by this outage, the company said that it’s currently investigating telemetry data and working to mitigate the impacted infrastructure.

“We’re continuing to evaluate service telemetry for potential system irregularities contributing to impact, and in parallel we’re applying some changes to optimize affected mailbox infrastructure,” Microsoft added in a recent update.

Earlier this week, Redmond resolved another issue that caused an anti-spam service to quarantine some emails and mistakenly block Exchange Online and Microsoft Teams users from opening URLs.

The company is also rolling out a fix to address an Exchange Online issue that triggers email access problems for Outlook mobile users who use Hybrid Modern Authentication (HMA).

The issue began impacting Android and iOS users on August 17, causing mailboxes to crash and preventing them from accessing their email and calendars.

Update September 11, 18:12 EDT: According to an admin center update, the outage also impacts customers in South America. Microsoft says it’s seeing signs of recovery after implementing a configuration change to some of the impacted infrastructure.

“We’ve seen some steady improvements in service quality as our manual database optimizations and configuration changes have reduced the impact of the high service utilization on the environment,” the compay notes.

“Additionally, we’re looking into a potential build versioning issue with a subset of machines supporting the service that may be contributing to impact.”

This is a developing story…

Update 7/6/25: Added Ingram Micro’s confirmation it suffered a ransomware attack below. Also updated ransom note with clearer version.

An ongoing outage at IT giant Ingram Micro is caused by a SafePay ransomware attack that led to the shutdown of internal systems, BleepingComputer has learned.

Ingram Micro is one of the world’s largest business-to-business technology distributors and service providers, offering a range of solutions including hardware, software, cloud services, logistics, and training to resellers and managed service providers worldwide.

Since Thursday, Ingram Micro’s website and online ordering systems have been down, with the company not disclosing the cause of the issues.

BleepingComputer has now learned that the outages are caused by a cyberattack that occurred early Thursday morning, with employees suddenly finding ransom notes created on their devices.

The ransom note, seen by BleepingComputer, is associated with the SafePay ransomware operation, which has become one of the more active operations in 2025. It is unclear if devices were actually encrypted in the attack.

It should be noted that while the ransom note claims to have stolen a wide variety of information, this is generic language used in all SafePay ransom notes and may not be true for the Ingram Micro attack.

Do you have information about this or another cyberattack? If you want to share the information, you can contact us securely and confidentially on Signal at LawrenceA.11, via email at lawrence.abrams@bleepingcomputer.com, or by using our tips form.

Sources have told BleepingComputer that it is believed the threat actors breached Ingram Micro through its GlobalProtect VPN platform.

Once the attack was discovered, employees in some locations were told to work from home. The company also shut down internal systems, telling employees not to use the company’s GlobalProtect VPN access, which was said to be impacted by the IT outage.

Systems that are impacted in many locations include the company’s AI-powered Xvantage distribution platform and the Impulse license provisioning platform. However, BleepingComputer was told that other internal services, such as Microsoft 365, Teams, and SharePoint, continue to operate as usual.

As of yesterday, Ingram Micro has not disclosed the attack publicly or to its employees, only stating there are ongoing IT issues, as indicated by company-wide advisories shared with BleepingComputer.

The SafePay ransomware gang is a relatively new operation that was first seen in November 2024, accumulating over 220 victims since then.

The ransomware operation has been previously observed breaching corporate networks through VPN gateways using compromised credentials and password spray attacks.

BleepingComputer contacted Ingram Micro yesterday and today about the outages and ransomware attack, but did not receive a response to our emails.

Update 7/6/25: In a brief Sunday morning announcement, Ingram Micro has confirmed that they suffered a ransomware attack.

“Ingram Micro recently identified ransomware on certain of its internal systems,” reads Ingram Micro’s statement.

“Promptly after learning of the issue, the Company took steps to secure the relevant environment, including proactively taking certain systems offline and implementing other mitigation measures. The Company also launched an investigation with the assistance of leading cybersecurity experts and notified law enforcement.”

“Ingram Micro is working diligently to restore the affected systems so that it can process and ship orders, and the Company apologizes for any disruption this issue is causing its customers, vendor partners, and others.”

Google says an API management issue is behind Thursday’s massive Google Cloud outage, which disrupted or brought down its services and many other online platforms.

Google says the cloud outage started around 10:49 ET and ended at 3:49 ET, after causing issues for millions of users worldwide for over three hours.

Besides Google Cloud, the incident also impacted Gmail, Google Calendar, Google Chat, Google Cloud Search, Google Docs, Google Drive, Google Meet, Google Tasks, Google Voice, Google Lens, Discover, and Voice Search.

However, it also caused widespread issues for third-party platforms that rely on Google Cloud, including but not limited to Spotify, Discord, Snapchat, NPM, Firebase Studio, and a limited number of Cloudflare services relying on the Workers KV key-value store.

“We are deeply sorry for the impact to all of our users and their customers that this service disruption/outage caused. Businesses large and small trust Google Cloud with your workloads and we will do better,” Google said.

While it’s still working on publishing a full incident report, Google revealed today the root cause of what caused an increased number of 503 errors in external API requests during yesterday’s three-hour-long outage.

As the company explained today, its Google Cloud API management platform failed due to invalid data, an issue that wasn’t discovered and remediated promptly because it lacked effective testing and error-handling systems.

“From our initial analysis, the issue occurred due to an invalid automated quota update to our API management system which was distributed globally, causing external API requests to be rejected. To recover we bypassed the offending quota check, which allowed recovery in most regions within 2 hours,” the company added.

“However, the quota policy database in us-central1 became overloaded, resulting in much longer recovery in that region. Several products had moderate residual impact (e.g. backlogs) for up to an hour after the primary issue was mitigated and a small number recovering after that.”

Cloudflare services taken down by Google’s outage

After successfully restoring its own impacted services, Cloudflare also revealed in a post-mortem that yesterday’s incident was not caused by a security incident and that no data was lost.

“The cause of this outage was due to a failure in the underlying storage infrastructure used by our Workers KV service, which is a critical dependency for many Cloudflare products and relied upon for configuration, authentication, and asset delivery across the affected services,” Cloudflare said.

“Part of this infrastructure is backed by a third-party cloud provider, which experienced an outage today and directly impacted the availability of our KV service.”

Even though it didn’t share the name of the cloud provider behind the Thursday outage, a Cloudflare spokesperson told BleepingComputer yesterday that only Cloudflare services relying on Google Cloud were affected.

In response to this incident, Cloudflare says it will migrate KV’s central store to its own R2 object storage to reduce external dependency and prevent similar issues in the future.

Wells Fargo has confirmed a mass outage that has prevented customers from accessing their accounts.

Customers began reporting issues on Saturday morning, with the vast majority unable to log in, according to DownDetector.

Users on social media also reported issues with their account balances, transactions and Zelle transfers, with one frustrated user saying he struggled to get answers.

“Local branch no responses to phone. Mobile banking down. Customer service 57 minutes to get someone and they cannot answer any question.”

The bank told the user to send a direct message for assistance.

The New York City-based news station PIX11 says the bank responded to a request for comment, stating system maintenance is to blame.

“This morning our ATMs and online banking services experienced a brief outage as a result of planned maintenance.”

The bank says all services are now restored.

At time of publishing, DownDetector says some user reports “indicate possible problems at Wells Fargo” with dozens of customers reporting Login, Zelle and debit card issues over the last six hours.

Follow us on X, Facebook and Telegram

Don’t Miss a Beat – Subscribe to get email alerts delivered directly to your inbox

Check Price Action

Surf The Daily Hodl Mix

&nbsp

Disclaimer: Opinions expressed at The Daily Hodl are not investment advice. Investors should do their due diligence before making any high-risk investments in Bitcoin, cryptocurrency or digital assets. Please be advised that your transfers and trades are at your own risk, and any losses you may incur are your responsibility. The Daily Hodl does not recommend the buying or selling of any cryptocurrencies or digital assets, nor is The Daily Hodl an investment advisor. Please note that The Daily Hodl participates in affiliate marketing.

Generated Image: Midjourney

Microsoft says it partially mitigated a week-long Exchange Online outage causing delays or failures when sending or receiving email messages.

While the company didn’t publicly share information on this incident, it tagged it as a critical service issue tracked under EX1027675 on the Microsoft 365 Admin Center.

Microsoft has yet to share more information on what regions were affected by this outage, but it said the incident impacted “any user serviced by the impacted portion of infrastructure.”

Customers worldwide also reported experiencing email delivery failures over the last week, with those impacted saying they were receiving a Non-Delivery Report (NDR) with a “554 5.6.0 Corrupt message content” error.

The company first acknowledged the Exchange Online email delivery issues on March 10, 11:14 AM, but the admin center incident report says the outage started on March 7, 12:30 PM UTC.

“A recent service update, intended to improve our message transport services, introduced a code issue that resulted in impact for a portion of service infrastructure,” Redmond said in the final update regarding this incident on Thursday.

“Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.”

Similar issue still causing email delivery failures

Microsoft continues to track a separate incident with a nearly identical impact under EX1030895 after successfully mitigating EX1027675 with a fix that rolled out Wednesday morning.

This second incident is still ongoing, with the company saying it’s “limited to a small subset of messages” that trigger NDR failures and intermittent plain text calendar invite emails with winmail.dat attachments.

Although it is still working on finding the root cause of these email delivery failures, Redmond says it’s testing a potential fix deployed on an isolated section of its infrastructure.

“We’re conducting multiple targeted restarts of machines containing the fix to ensure the expected relief is achieved,” Microsoft said earlier today. “Additionally, we’re closely monitoring our diagnostic telemetry data to isolate the root cause of the issue, and we’re reviewing the overall service health during this process.”

Two weeks ago, the company linked a weekend Microsoft 365 outage affecting Outlook and Exchange Online authentication to another “code issue.” A subsequent advisory revealed that Exchange Online users still had issues accessing calendars and email messages using the iOS native mail app.

Days later, it mitigated one more Microsoft 365 outage affecting Teams customers and causing call failures.