Grok Bot's cloud computer has lost DNS functionality, causing failures in hostname-dependent operations and preventing updates

Signals over time

2 observed signals across 1 sources, tracked for 8 days. Confidence: low.

What people are saying Observed

• “Grok Bot computer unreachable 11+ hours after Update/Reset — a month of work in /workspace (Ticket T-H26869). Where does the bug appear (feature/product)? Grok Bot Describe the Bug Hi everyone, and hi to the Cursor team I’m hoping someone from the team can take a look. I’m quite worried. What happened Since 22:19 SGT (UTC+8) on Oct 13, my Grok Bot computer has been unreachable. Every command hangs or times out. ~23:00 I clicked Update Bot’s Computer, but it didn’t help. 23:56 I clicked Reset Bot’s Computer. Still unreachable. Tried another device, same result. Still down as of 09:20 SGT on Oct 14 . Why it matters From Sept 17 to Oct 13 I developed full-time on this computer. Nearly a month of code and all my collected data live only in /workspace, with no other copy. I also had services running there over Tailscale. Support status Ticket T-H26869. The AI assistant escalated it and asked me not to Reset/Update again, which I’ve followed. No human reply yet. What I’m asking Please preserve my data and restore the latest snapshot from before 22:19 SGT Oct 13. An older one would still lose weeks of work. Any rough ETA or confirmation that my data is safe would mean a lot. Thank you so ”

  RSS Feeds · request

• “Grok Bot computer DNS dead (198.18.0.53 times out); Update unavailable: files aren't ready. Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot’s cloud computer lost DNS around Oct 5, 2026, 2:33 PM ET and it’s still broken. The built-in resolver at 198.18.0.53 times out on every lookup. Raw internet and public DNS (8.8.8.8, 1.1.1.1) work from the box, so connectors and bots still work, but anything that needs a hostname (web, pip, GitHub CLI) fails. Update Computer won’t run. It says “Update unavailable: files aren’t ready” even after waiting overnight and retrying this morning (Oct 6). I have not used Reset. Steps to Reproduce Computer. 2. See “Update unavailable: files aren’t ready” (or let it sit overnight and retry). 3. On the box, getent hosts github.com times out. curl https://1.1.1.1 works. UDP DNS to 8.8.8.8 and 1.1.1.1 returns answers. /etc/resolv.conf points only at 198.18.0.53, which times out. Expected Behavior The built-in DNS resolver should answer, or Update Computer should succeed so the box can be moved to a fresh instance that restores DNS, without needing Reset. Screenshots / Screen Recordings Operating System iOS Version Information G”

  RSS Feeds · complaint