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

Grok Bot Grok Bot 1.13.1 (15504) · runtime bdf8bab6342e08ac7e7926bce8c63e48b7271724 · embedded bundle · channel production

iOS 26.6.1

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

temporary workaround I got my chief of staff to patch the DNS to get the agentic teams pushed to the repo.

A work around not a resolution

Hi @NKerzman Thanks for reporting! Your Grok Bot box is fully updated and should be restored and working well now. Please let us know if you have any issues going forward.

Thank you I greatly appreciate it.

I just saw this message . Britt I saw it, I saw an attempted to update the computer from desktop and that also worked. That might be because of the cleanup you guys did on the back end.

Really appreciate the timely support!