warp.dev is down?

[jeffreyschultz]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

The warp.dev domain is not able to be resolved for me right now including the necessary subdomains needed for accessing the inference endpoints. I used isitdownrightnow.com to see if it was just my DNS providers having issues resolving the name, but it seems to be down for everyone.

Any sense of what happened and a resolution timeline?

To reproduce

1. Open Warp and attempt to use agent to get this error message.

I'm sorry, I couldn't complete that request.

Request failed with error: Transport(reqwest::Error { kind: Request, url: "https://app.warp.dev/ai/multi-agent", source: hyper_util::client::legacy::Error(Connect, ConnectError("dns error", Os { code: 11002, kind: Uncategorized, message: "This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server." })) })

2. Navigate to warp.dev within a web browser to get a DNS_PROBE_FINISHED_NXDOMAIN error.

This site can’t be reached
Check if there is a typo in warp.dev.

If spelling is correct, [try running Windows Network Diagnostics](javascript:diagnoseErrors()).
DNS_PROBE_FINISHED_NXDOMAIN

Expected behavior

No response

Screenshots, videos, and logs

No response

Operating system (OS)

Windows

Operating system and version

Windows 11

Shell Version

bash 5.2.21

Current Warp version

v0.2025.12.10.08.12.stable_03

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

12/17/2025

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[harryalbert]

Thanks for flagging this Jeffrey!

It seems like there might be a non-warp issue with how the public google DNS is interacting with our hosting provider, so folks who are using that as their local DNS will likely have some issues using warp. Setting your local DNS to 1.1.1.1 (cloudflare) seems to fix the issue (in system settings go to DNS servers and just add 1.1.1.1).

We are actively investigating this and will update this thread if anything comes up!

[jeffreyschultz]

Thanks for flagging this Jeffrey!

It seems like there might be a non-warp issue with how the public google DNS is interacting with our hosting provider, so folks who are using that as their local DNS will likely have some issues using warp. Setting your local DNS to 1.1.1.1 (cloudflare) seems to fix the issue (in system settings go to DNS servers and just add 1.1.1.1).

We are actively investigating this and will update this thread if anything comes up!

Thank you for the quick reply! I am using Google DNS and did not even think about that.

I will give that go!

[harryalbert]

Thanks for flagging this Jeffrey!
It seems like there might be a non-warp issue with how the public google DNS is interacting with our hosting provider, so folks who are using that as their local DNS will likely have some issues using warp. Setting your local DNS to 1.1.1.1 (cloudflare) seems to fix the issue (in system settings go to DNS servers and just add 1.1.1.1).
We are actively investigating this and will update this thread if anything comes up!

Thank you for the quick reply! I am using Google DNS and did not even think about that.

I will give that go!

Great, no problem! Please let me know if that doesn't work and we can troubleshoot further.

[jeffreyschultz]

Thanks for flagging this Jeffrey!
It seems like there might be a non-warp issue with how the public google DNS is interacting with our hosting provider, so folks who are using that as their local DNS will likely have some issues using warp. Setting your local DNS to 1.1.1.1 (cloudflare) seems to fix the issue (in system settings go to DNS servers and just add 1.1.1.1).
We are actively investigating this and will update this thread if anything comes up!

Thank you for the quick reply! I am using Google DNS and did not even think about that.
I will give that go!

Great, no problem! Please let me know if that doesn't work and we can troubleshoot further.

It is working for me now.

[DhairyaPatelYML]

I'm sorry, I couldn't complete that request.

Request failed with error: Transport(reqwest::Error { kind: Request, url: "https://app.warp.dev/ai/multi-agent", source: hyper_util::client::legacy::Error(Connect, ConnectError("dns error", Os { code: 11001, kind: Uncategorized, message: "No such host is known." })) })
Debug information: {"conversation_id":"b72db1d3-88d4-4987-8afe-445bda0e5b99"}

[harryalbert]

I'm sorry, I couldn't complete that request.

Request failed with error: Transport(reqwest::Error { kind: Request, url: "https://app.warp.dev/ai/multi-agent", source: hyper_util::client::legacy::Error(Connect, ConnectError("dns error", Os { code: 11001, kind: Uncategorized, message: "No such host is known." })) }) Debug information: {"conversation_id":"b72db1d3-88d4-4987-8afe-445bda0e5b99"}

Did you try the steps mentioned above (here)?

[DhairyaPatelYML]

Yea, still facing this from last couple of days

[harryalbert]

Yea, still facing this from last couple of days

Sorry about that Dhairya! Could you try running dig app.warp.dev in your terminal and see what's output?

[zachlloyd]

This seems to have been a temporary issue.