Is it down? · AI apps and model providers
The card here reads Cursor’s status page live. If it reports no problems, the fault is probably on your side, and Kilobat finds where.
Official status: status.cursor.com ↗
brew install seifip/kilobat/kilobat
Cursor CLI
Cursor · status.cursor.com
Live status
This card reads Cursor’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 Cursor, 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 Cursor CLI, then Cursor’s status page. If the page reports an outage and nothing on your side failed, it says “Cursor CLI 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 Cursor CLI.
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
An outage at Cursor, while your line is fine.
One notification per incident, such as “Claude Code: Anthropic reports an outage — not your connection”, and the MCP tool service_status for agents. Free
The path from your Mac to Cursor CLI: DNS, a VPN or proxy, IPv6, or the server’s answer.
“Cursor CLI’s status page reports no problems”, then the layer that broke and what to try next. Free
Cursor CLI 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 Cursor CLI and Kilobat checks your Wi-Fi, DNS, VPN and proxy, the connection and the server’s answer, then asks Cursor’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? Cursor’s status page
$ kilobat down cursor-cliThe 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 Cursor CLI points at Cursor’s status page, not a guess.
status.cursor.com forwards to the feed of Cursor’s page, hosted on status.x.ai. Kilobat counts only its CLI component.
The same status page also covers Cursor.
If Cursor CLI won’t connect
The Cursor CLI uses the same hosts as the editor.
cursor.com, *.cursor.com, *.cursor.sh, *.cursorapi.com, *.cursor-cdn.com and *.cursorvm.com.From Cursor’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 Cursor’s status page, status.cursor.com, which Cursor’s team updates. The card at the top of this page reads it live in your browser and repeats only what it says.
When Cursor’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 Cursor CLI works there, your network is the problem. Kilobat checks each of these and names the one that failed.
Connections from the cursor-agent process, matched to Cursor’s status page, counting only its component CLI. It checks your own line first, then asks the page.
Yes. When Cursor CLI keeps failing to connect while your own line is fine, and Cursor’s status page reports trouble, you get one notification per incident. Turn it off in Settings.
status.cursor.com forwards to the feed of Cursor’s page, hosted on status.x.ai. Kilobat counts only its CLI component.
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