Is it down? · Mail, files and documents
The card here reads Google’s status page live. If it reports no problems, the fault is probably on your side, and Kilobat finds where.
Official status: google.com ↗
brew install seifip/kilobat/kilobat
Google Calendar
Google · google.com
Live status
This card reads Google’s status page live when JavaScript is on. If nothing appears, open the page below.
What you notice says a lot about which side the problem is on. Kilobat checks both sides and says which.
An outage at Google, 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 calendar.google.com, then Google’s status page. If the page reports an outage and nothing on your side failed, it says “Google Calendar 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 Google Calendar.
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
The path from your Mac to Google Calendar: DNS, a VPN or proxy, IPv6, or the server’s answer.
“Google Calendar’s status page reports no problems”, then the layer that broke and what to try next. Free
Google Calendar 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 Google Calendar and Kilobat checks your Wi-Fi, DNS, VPN and proxy, the connection and the server’s answer, then asks Google’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? Google’s status page
$ kilobat down google-calendar
# Or me? Every layer from this Mac to Google Calendar
$ kilobat why calendar.google.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 Google Calendar points at Google’s status page, not a guess.
google.com, run by Google
The same status page also covers Google Meet, Gmail, Google Drive, Google Docs and Google Chat.
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 Google’s status page, google.com, which Google’s team updates. The card at the top of this page reads it live in your browser and repeats only what it says.
When Google’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 Google Calendar works there, your network is the problem. Kilobat checks each of these and names the one that failed.
Connections to Google Calendar, and the sites calendar.google.com, matched to Google’s status page. It checks your own line first, then asks the page.
It tells you when you check a connection to calendar.google.com or open Health. Background notifications need an app or a host Kilobat can watch, and Google Calendar is matched by the sites you open.
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