isitdns? it's always dns  until it isn't

wiki/News/Outlook outage, 2026-11-12

News

Outlook outage, 2026-11-12

What happened#

On Thursday afternoon, US time, Microsoft said it was investigating reports of people having trouble reaching their mailboxes.

Getting to Outlook takes two steps. First your computer looks up where Outlook lives (DNS). Then it connects to one of the addresses it was given and asks for the page.

The first step worked: lookups returned addresses on 795 of 797 checks. Overnight, the second step mostly failed: most of the addresses they returned did not answer.

Who was affected#

Microsoft said the problem could reach people in any region (ABC News).

From our three probes (test machines in Phoenix, South Carolina and Amsterdam), Thursday 21:49 to Friday 07:07 UTC:

  • Phoenix and South Carolina: 24 of 1,682 tries reached Outlook. About 1 in 70.
  • Amsterdam: 177 of 834 tries reached Outlook. About 1 in 5.

Timeline#

tries that reached Outlook, all three probes, one cell per 30 minutes: every one 9 in 10 or more half or more under half none no readings

  1. to 21:36 UTC no readings we were not measuring yet
  2. start Microsoft says it is investigating reports of people having trouble reaching their mailboxes (ABC News)
  3. our first reading: DNS answers
  4. our sampler starts: 4 of 46 tries reach Outlook by 22:00
  5. to 11:35 UTC no readings the machine running our sampler restarted at 07:10, and the sampler was started again at 11:35
  6. coming back: 12 of 17 tries reach Outlook, up from 2 of 15 at 11:35
  7. fixed tries from all three probes reach Outlook again; 5 misses in the next 3,024
the readings, cell by cell
UTCtries that reached Outlook, all three probes
to 22:00 UTC4 of 46
to 22:30 UTC8 of 108
to 23:00 UTC18 of 110
to 23:30 UTC23 of 86
to 00:00 UTC17 of 67
to 00:30 UTC17 of 132
to 01:00 UTC7 of 144
to 01:30 UTC6 of 144
to 02:00 UTC18 of 168
to 02:30 UTC5 of 144
to 03:00 UTC10 of 144
to 03:30 UTC11 of 144
to 04:00 UTC5 of 143
to 04:30 UTC7 of 144
to 05:00 UTC12 of 168
to 05:30 UTC8 of 144
to 06:00 UTC6 of 144
to 06:30 UTC11 of 144
to 07:00 UTC7 of 144
to 07:30 UTC1 of 48
to 08:00 UTCno reading
to 08:30 UTCno reading
to 09:00 UTCno reading
to 09:30 UTCno reading
to 10:00 UTCno reading
to 10:30 UTCno reading
to 11:00 UTCno reading
to 11:30 UTCno reading
to 12:00 UTC54 of 99
to 12:30 UTC120 of 167
to 13:00 UTC121 of 144
to 13:30 UTC126 of 144
to 14:00 UTC143 of 144
to 14:30 UTC144 of 144
to 15:00 UTC168 of 168
to 15:30 UTC144 of 144
to 16:00 UTC143 of 144
to 16:30 UTC168 of 168
to 17:00 UTC144 of 144
to 17:30 UTC144 of 144
to 18:00 UTC143 of 144
to 18:30 UTC168 of 168
to 19:00 UTC144 of 144
to 19:30 UTC144 of 144
to 20:00 UTC143 of 144
to 20:30 UTC168 of 168
to 21:00 UTC144 of 144
to 21:30 UTC144 of 144
to 22:00 UTC144 of 144
to 22:30 UTC144 of 144
to 23:00 UTC167 of 168
to 23:30 UTC144 of 144
to 00:00 UTC24 of 24

What it looked like in DNS#

The three Outlook names we asked (outlook.office365.com, outlook.office.com, outlook.cloud.microsoft) pointed to one name, fs.outlook.mira.tm.svc.cloud.microsoft, and that name gave out between 1 and 8 addresses. The set changed from one ask to the next.

what we askedwhat came back
the Outlook names, four public DNS services, 21:36 UTCan answer every time, with a valid signature (ad set)
the address set, three probes, Thu 21:49 to Fri 07:07 and 11:35 to 23:32 UTCaddresses on 795 of 797 asks; 8 addresses on 742 of them
the same question as if asked from five networks (RFC 7871)1 to 8 addresses, a different set per network
the delegation and the DNSSEC chain, 21:36 UTCchecked, no error

Asks 1.1.1.1 for the address set that the three Outlook names end at.

 dig -4 @1.1.1.1 fs.outlook.mira.tm.svc.cloud.microsoft A
; <<>> DiG 9.18.39-0ubuntu0.24.04.9-Ubuntu <<>> -4 @1.1.1.1 fs.outlook.mira.tm.svc.cloud.microsoft A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12875
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;fs.outlook.mira.tm.svc.cloud.microsoft. IN A
;; ANSWER SECTION:
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 52.98.231.2
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 40.99.153.130
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 40.99.215.82
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 40.101.22.196
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 40.101.69.2
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 40.101.69.18
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 52.97.128.2
fs.outlook.mira.tm.svc.cloud.microsoft. 6 IN A 52.97.178.34
;; Query time: 5 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Thu Nov 12 21:40:06 UTC 2026
;; MSG SIZE rcvd: 195

GO NOERROR, ad set, A records

NO GO SERVFAIL, NXDOMAIN, or no A record

what each part of this output means →

From the Amsterdam probe, 21:40:06 UTC. The addresses, the TTL, the id and the Query time change from run to run.

Why#

Microsoft's words, as ABC News quoted them: the problem was "introduced by an issue during an earlier network capacity upgrade," and "This was a technical issue not related to cyber or AI / agents."

Our reading, 00:40 UTC Friday: the path from Phoenix and from Amsterdam to one silent address went into Microsoft's network and stopped there.

What we could not see:

  • Anything before 21:36 UTC Thursday. The start time is Microsoft's, not ours.
  • 07:07 to 11:35 UTC Friday: the machine running our sampler restarted at 07:10, and the sampler was not started again until 11:35.
  • Inside Microsoft's network.
  • IPv6, sign-in, and mail delivery.
  • Your own network: test your own path.

If it happens to you#

  1. Check Microsoft's own status first: Microsoft 365 service health.
  2. Ask the name yourself: four public DNS services side by side.

Receipts#

Two kinds of reading, both from isitdns machines:

  • The isitdns tools, 21:36 to 21:42 UTC Thursday: the Outlook names from the edge over DoH (Cloudflare, Google, Quad9, AdGuard) and 1.1.1.1 from the Phoenix and Amsterdam probes, plus the delegation, the DNSSEC chain and five client subnets.
  • A sampler on three isitdns probes (Phoenix, South Carolina, Amsterdam), started by hand at 21:49 UTC Thursday, after the outage began.
    • Each round it asked 1.1.1.1 for the address set, then requested https://outlook.office365.com/owa/ once at each address: 5 seconds to connect, 8 seconds in all.
    • A try "reached Outlook" when /owa/ answered with its 302 redirect. A 500 or 503 does not count.
    • Its last round before the gap began at 07:06 UTC and ended at 07:07. The machine running it restarted at 07:10 UTC, and it was started again by hand at 11:35 UTC. Its last round was 23:32 UTC Friday.

Each try, by outcome:

probe, window (UTC)302500 or 503TCP, no HTTP answerno TCP
Phoenix, Thu 21:49 to Fri 07:07167134688
South Carolina, same86131692
Amsterdam, same17729255373
Phoenix, Fri 11:35 to 13:321394231
South Carolina, same1522329
Amsterdam, same13011150
Phoenix, Fri 13:32 to 23:321006101
South Carolina, same1007100
Amsterdam, same1006020

One try of each kind, curl -m 8 --connect-timeout 5 --resolve outlook.office365.com:443:<address> https://outlook.office365.com/owa/:

  • 302: Amsterdam, 40.101.69.34, 00:38:04. TCP at 0.024 s, TLS at 0.114 s, HTTP/2 302, location: https://outlook.office365.com/mail/
  • 500: South Carolina, 40.99.165.114, 00:27:53. TCP at 4.18 s, TLS at 4.49 s, HTTP 500
  • TCP, no HTTP answer: Phoenix, 52.96.164.178, 00:37:18. Connected at 4.127 s, client hello sent, SSL connection timeout at 5.0 s
  • no TCP: Phoenix, 52.96.163.34, 00:37:23. connect to 52.96.163.34 port 443 failed: Connection timed out at 5.0 s

The path to the silent 52.96.163.34 entered Microsoft's network (AS8075) from Phoenix and from Amsterdam, and the last hop that answered was in 104.44.52.0/24 (AS8075) from both. The path to 40.101.69.34 answered end to end from both. mtr -T -P 443 from the probes, 00:40 UTC Friday.

The address set per client subnet, from Google with the subnet passed on (RFC 7871), 21:40:18 UTC:

subnetA records
12.0.0.0/248, in 52.96.x and 52.97.x
142.103.0.0/241, 52.96.164.146
200.160.0.0/241, 40.97.63.133
81.2.69.0/245, in 40.98.x, 40.101.x, 52.98.x and 40.99.x
133.11.0.0/241, 40.99.76.114

Asked again at 21:42:20 UTC, the five read 1, 8, 8, 5 and 2.

Ask again:

readingapi
the name, four resolvershttps://isitdns.net/api/query?name=fs.outlook.mira.tm.svc.cloud.microsoft&type=A&resolver=all&transport=doh
from Phoenixhttps://isitdns.net/api/query?name=fs.outlook.mira.tm.svc.cloud.microsoft&type=A&resolver=cloudflare&transport=udp53&from=north-america
from Amsterdamhttps://isitdns.net/api/query?name=fs.outlook.mira.tm.svc.cloud.microsoft&type=A&resolver=cloudflare&transport=udp53&from=europe
with a client subnethttps://isitdns.net/api/query?name=fs.outlook.mira.tm.svc.cloud.microsoft&type=A&resolver=google&transport=doh&dnssec=0&ecs=12.0.0.0%2F24

See also#