Know when Cloud goes offline or comes back
Choose how long to watch. We email only when the status changes.
cloud.microsoft · AI tools
Cloud has recorded 100.0% uptime over the last 2 days, with no outage. It answers our checks in 197 ms on average.
Cloud answered our last automated check normally, 15 minutes ago. If it is not working for you, the problem is most likely local - Your connection, your DNS resolver, a cached page, or an extension.
Choose how long to watch. We email only when the status changes.
Check any website now, or jump straight to a similar service.
See all ai toolsCounted in 15-minute buckets from reports submitted on this site. This is a user signal - A tall bar means people are complaining, not that our check failed.
No reports in the last 24 hours.
If Cloud is not working for you, tell us and the chart starts here.
The last 24 checks of https://m365.cloud.microsoft/ from our network. Bar height is the response time; the tallest bar is the slowest.
Tell us what is not working. Reports go straight onto the 24-hour chart above and help other people see a problem before any company admits to one. 0 reports in the last 24 hours.
Cloud sits at number 178 on the worldwide traffic ranking with about 28.5M organic visits a month, and the address it resolves to belongs to Microsoft Corporation. Cloud publishes 10 addresses for the name, reachable over IPv6 as well as IPv4.
Name service for cloud.microsoft is operated by Azure DNS, with the registration held through MarkMonitor Inc., and dated to 2015. Cloud.microsoft signs its zone with DNSSEC and sends an HSTS header, so browsers refuse it over plain HTTP. The certificate cloud.microsoft presented to us was issued by Microsoft Corporation, covering 3 names, with 51 days left on it at first check, and negotiated over TLSv1.3. Our first check of cloud.microsoft returned HTTP 200 in 363 ms, of which 8 ms was name resolution and 8 ms the connection. The request to cloud.microsoft passed through 1 redirect before it settled on https://m365.cloud.microsoft/. Those figures are the baseline this page measures cloud.microsoft against from now on, every 20 minutes.
Our last check reached cloud.microsoft normally, from a different network, resolver and route than yours. If it is broken for you, the fault is most likely local or too narrow for a single probe to see. Our next automated check runs within 20 minutes and this page updates with it.
Distinguish slow from down before reporting. A response that takes ninety seconds is a degradation. Knowing which one you are seeing changes what you should do.
Requests are accepted and take far longer than usual, or return a rate-limit error. Answers may truncate mid-sentence. The interface stays perfectly responsive, which is why this reads as a slow service rather than a broken one. The rest of the steps, and why this category breaks the way it does, are on our ai tools status page, with more background in 429 Too Many Requests explained.
Over the last 30 days Cloud ranks 5 of 6 ai tools services we monitor, measured on recorded uptime. The category averages 100.0%, and Cloud sits at 100.0%. The steadiest in this group is ChatGPT.
On speed, Cloud answers our checks in about 197 ms against a category average of 187 ms - Slower than its peers. Response time is not availability, but a service drifting well above its own normal is often the first sign of trouble.
Across the most recent 24 checks, the quickest response was 90 ms and the slowest 279 ms, against a 30-day average of 197 ms. The chart above plots each one, so a widening spread is visible before it becomes an outage.
All figures are our own measurements, taken every 20 minutes from one network. What that can and cannot see is set out in the methodology, and every ai tools service is listed on the category page.
Five more fields about the server behind cloud.microsoft.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
Read from our last sweep of cloud.microsoft, not requested when you opened this page.
Who issued it, what it covers and exactly when it expires.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
An expired certificate stops browsers loading a site entirely while the server itself stays perfectly healthy, which is why we track it beside the uptime figure.
.Cloud is up and responding normally. This page is refreshed by an automated check that runs every 20 minutes from an independent network, and by reports from visitors.
Because an outage can be partial. Our check runs from one network and asks for one page. Your problem may be regional, may affect only the mobile app, or may be local to your connection, DNS resolver or browser cache.
Cloud has been reachable for 100.0% of the last 2 days we have measured, with 0 seconds of recorded downtime.
Cloud does not publish a public status page, which is why independent monitoring and user reports are the only external signal available during an incident.
Cloud discussion
Useful comments say what broke, roughly where you are and roughly when it started - That is what turns a pile of complaints into something other people can act on. Links are shown as plain text and carry no SEO value, so there is nothing here worth spamming.