Is it 364 yet?

Not yet. The 5 is falling. The cake is ordered.

Days of service this year, best case

To be exact: 365.0000. The flap is 0.0% of the way over.

--h--m--s

until it's official, at 8:17 AM Pacific on Friday. Unless somebody fixes it first.

When the clock started

8:17 AM Pacific, Thursday. That is the start time Microsoft gave for incident EX1550543, as reported. A full day later is 8:17 AM Friday.

What counts as back up

Microsoft says so. The clock stops when Microsoft's public status page stops showing a problem for Microsoft 365. "Works for me" does not count. The first all-clear ends it.

Who is keeping score

A script reads that status page every 10 minutes. It has not reported in yet.

While you wait

Email is down, so you have time. Everything here stays in your browser.

Outage bingo

Tap what you've seen today. Five in a row wins nothing.

0 of 25

Call it

When does Microsoft give the all-clear? One pick. Bets are final, like a change freeze. Stakes: one slice of cake. Times are Pacific.

No bet placed.

Root cause machine

The official report takes weeks. This takes a second.

Somebody
did something to
something

Vague update generator

From the Office of Saying Something Every 60 Minutes.

We're investigating reports of reports. Next update in 60 minutes.

Your outage dividend

Emails not received0
Reply-alls dodged0
Meeting invites lost0
"Per my last email"0
Due when service returnsall of it
Payableat once