Is it down? · Calls and chat
Microsoft’s status page is the official answer. If it reports no problems, the fault is probably on your side, and Kilobat finds where.
Official status: status.cloud.microsoft ↗
brew install seifip/kilobat/kilobat
Microsoft Teams
Microsoft · status.cloud.microsoft
Open the status page
Microsoft’s status page doesn’t let other websites read it, so open it to see the live status.
What you notice says a lot about which side the problem is on. Kilobat checks both sides and says which.
An outage at Microsoft, or something on the path to it only: DNS, a VPN or proxy, a blocked host.
Why can’t it connect? checks every layer to teams.live.com, then Microsoft’s status page. If the page reports an outage and nothing on your side failed, it says “Microsoft Teams is down for everyone, not you”. Free
This network: an office, school, hotel or country rule, or its DNS.
Kilobat compares this network’s DNS with one encrypted lookup and tests the secure connection, then says “looks blocked on this network, not down”, with what it measured. Free
Your own line: Wi-Fi, the router, your provider or DNS. Not Microsoft Teams.
Router and internet latency side by side show whether your own line is slow. Pro names the failing link, Wi-Fi, router, internet or DNS, with a fix. Free Pro
Trouble beyond your router, on the path to Microsoft’s servers.
Each call’s card says whether Microsoft’s status page reported an outage at the time. Pro adds the possible causes of the freezes. Free
The path from your Mac to Microsoft Teams: DNS, a VPN or proxy, IPv6, or the server’s answer.
“Microsoft Teams’s status page reports no problems”, then the layer that broke and what to try next. Free
Microsoft Teams loads only if every step works. A status page covers the last one; Kilobat checks the five before it too.
Why can’t it connect? Free
Name Microsoft Teams and Kilobat checks your Wi-Fi, DNS, VPN and proxy, the connection and the server’s answer, then asks Microsoft’s status page. When the page reports an outage and nothing on your side failed, the verdict leads with it. When your Mac is the problem, it says so first.
# Is it them? Microsoft’s status page
$ kilobat down teams
# Or me? Every layer from this Mac to Microsoft Teams
$ kilobat why teams.live.comThe app’s proxy isn’t answering.
Why can’t it connect? Kilobat tests the request and path the app itself uses, its own proxy, IPv6 and tunnels included, and names the layer that broke.
What Kilobat watches
Kilobat matches apps and sites to the right status page by bundle ID and domain, so a failing Microsoft Teams points at Microsoft’s status page, not a guess.
status.cloud.microsoft, run by Microsoft
The Microsoft Teams app, by its bundle ID.
Microsoft publishes status for Teams for work or school only to signed-in admins, in the Microsoft 365 admin centre. The public page Kilobat reads covers the free, personal Teams.
If Microsoft Teams won’t connect
Microsoft lists the Teams hosts and ports for Microsoft 365. Calls prefer UDP; when it’s blocked, audio and video suffer first.
teams.microsoft.com, *.teams.microsoft.com, teams.cloud.microsoft and *.lync.com on TCP 443 and 80, and UDP 443.From Microsoft’s own help pages, listed under Sources. Kilobat’s guides cover DNS, VPN and proxy trouble on a Mac.
kilobat down, kilobat why and the MCP tool service_statusPro is $29 once for two Macs, with a 7-day free trial and 14-day refunds. Free for students.
The official answer is Microsoft’s status page, status.cloud.microsoft, which Microsoft’s team updates. It doesn’t let other websites read it, so open it directly; Kilobat’s app reads it for you.
When Microsoft’s status page reports no problems, the cause is usually on your side or on the way: your Wi-Fi or router, your provider, DNS, a VPN or proxy, or a network that blocks it. Try mobile data: if Microsoft Teams works there, your network is the problem. Kilobat checks each of these and names the one that failed.
Connections from the Microsoft Teams app, and the sites teams.live.com, matched to Microsoft’s status page. It checks your own line first, then asks the page.
Yes. When Microsoft Teams keeps failing to connect while your own line is fine, and Microsoft’s status page reports trouble, you get one notification per incident. Turn it off in Settings.
Microsoft publishes status for Teams for work or school only to signed-in admins, in the Microsoft 365 admin centre. The public page Kilobat reads covers the free, personal Teams.
No. It sends a plain request to the status page, with no cookies and nothing about you, your network or your apps. Read the privacy notice.
Yes: the status checks, the notifications and Why can’t it connect? are free. Kilobat Pro, $29 once, adds findings with a fix for your own network, possible causes of call freezes and history.
Checked on 6 November 2026.
brew install seifip/kilobat/kilobat