Your connection, or their outage?
What you notice says a lot about which side the problem is on. Kilobat checks both sides and says which.
You noticeUsually it’sWhat Kilobat does
Only GitHub fails; everything else loads
An outage at GitHub, 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 github.com, then GitHub’s status page. If the page reports an outage and nothing on your side failed, it says “GitHub is down for everyone, not you”. Free
GitHub fails on this network, but works on mobile data
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
Everything is slow, GitHub included
Your own line: Wi-Fi, the router, your provider or DNS. Not GitHub.
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
GitHub’s status page is green, but GitHub still fails
The path from your Mac to GitHub: DNS, a VPN or proxy, IPv6, or the server’s answer.
“GitHub’s status page reports no problems”, then the layer that broke and what to try next. Free
Six links between you and GitHub.
GitHub loads only if every step works. A status page covers the last one; Kilobat checks the five before it too.
- Your MacA VPN, proxy or app in the way
- Wi-FiSignal, noise and band
- RouterLatency and loss to it
- ProviderLatency and loss beyond it
- DNSWhether github.com resolves, and how fast
- GitHubGitHub’s status page, read live
What Kilobat watches
How Kilobat knows it’s GitHub.
Kilobat matches apps and sites to the right status page by bundle ID and domain, so a failing GitHub points at GitHub’s status page, not a guess.
On your Mac
The GitHub app, by its bundle ID.
Kilobat counts GitHub’s core components, such as Git operations, API requests, Actions and Pages. Copilot has its own page here.
The same status page also covers GitHub Copilot.
If GitHub won’t connect
What GitHub needs from your network.
Most networks pass HTTPS but some block SSH on port 22, so git push fails while github.com loads.
- GitHub accepts SSH on port 443 at
ssh.github.com. Test it with ssh -T -p 443 git@ssh.github.com. - To use it for every push, set
Hostname ssh.github.com, Port 443 and User git under Host github.com in ~/.ssh/config. - GitHub needs TCP 22, 80 and 443. Its address ranges are in
api.github.com/meta, but GitHub advises against allowlisting by address because they change.
From GitHub’s own help pages, listed under Sources. Kilobat’s guides cover DNS, VPN and proxy trouble on a Mac.
What’s free, and what Pro adds
Free, for good Free
- Is it them or me? Status pages for 72 services, GitHub included
- The outage at the top of Health, and in a connection check
- A notification per outage while an app keeps failing
- Whether the calling service had an outage, on every call card
kilobat down, kilobat why and the MCP tool service_status- Blocked on this network, or not available in your region, said as measured
Pro, $29 once Pro
- Findings with a fix for router, DNS and login-page trouble
- Possible causes of call freezes
- Outage and latency history for your own line
- Signal radar and channel crowding
Pro is $29 once for two Macs, with a 7-day free trial and 14-day refunds. Free for students.
Next time GitHub stalls, know whose problem it is.