Unable to connect to Supabase project - DNS resolution failure for project URL
I'm unable to connect to my Supabase project from a Next.js 15 application. Till yesterday, i was able to connect from my nextjs app but today, the domain cannot be resolved.
Issue details:
When attempting to authenticate using supabase.auth.signInWithPassword(), I receive "Failed to fetch" and "Connect Timeout Error" (code: UND_ERR_CONNECT_TIMEOUT)
DNS lookup fails: Running curl https://[Project_URL] .supabase.co returns "Could not resolve host: jzlddonygtywhhrupgzz.supabase.co"
nslookup also cannot resolve the domain
The domain appears to not exist on the internet despite being shown in my project's API settings
Environment:
Next.js 15.5.2 with App Router
@supabase/ssr (0.7.0) and @supabase/supabase-js packages
Project URL and anon key are correctly set in environment variables (without quotes)
Testing from macOS, no VPN or proxy
I've verified:
The URL exactly matches what's shown in Settings → API → Project URL
The project appears active in the dashboard (no pause warnings)
Network connectivity is working (other APIs accessible)
Same error occurs from multiple network connections
Could you please tell me what is the issue and why a sudden block to my app? The project exists in my dashboard but the domain cannot be reached from the internet. This appears to be a DNS/infrastructure issue rather than a code problem.
24 Replies
Where are you located?
Have you tried a different network provider path.
There seems to be an ISP issue in the UAE. https://discord.com/channels/839993398554656828/1006358244786196510/threads/1412323801135317013
Same issue in Dubai especially when using 8.8.8.8 dns server
What ISP? I think I've seen the name Horizon mentioned.
I also have the same issue using E& as ISP. I just restarted my supabase project and I keep getting 'Fetch Failed' error when running my app (from the middleware).
Basically the same issue that is mentioned above.
Has this happened before? Is there a fix that can be done from our side or is it dependent on the ISP?
Etisalat
I'm also located in Dubai, (E& is the same as Etisalat)
getting this. for all of my supabase projects
If you try another network does it work?
This has been escalated to Supabase, but if it is an ISP issue, not clear what they will be able to do about it directly.
here in het netherlands
jzlddonygtywhhrupgzz.supabase.co gets resolved. initially my pihole gets the request, then 8.8.8.8 or 8.8.4.4 gets to answer
i'm presuming you ran the nslookup locally in your console though.
perhaps somehow configure to use the cloudflare dns? to help isolate the causeI'd need to test it later as I'm using my home network.
If I'm able to test it before it's resolved I'll update this chat.
tried using 1.1.1.1 dns server, I was able to fetch using nslookup
for Du network it is working
See the post I just added!!!!
i am facing issue on UAE network only , for other network working fine. how can resolve this issue? @garyaustin
yes i noticed now only Etisalat network face issue.
Can one of you who are able to reproduce this please do a
dig <yourprojectid>.supabase.co and post the results, please?Here are the results for my project.
Yes servers are unreachable easy to test with a simple nslookup
Do you have any idea when will back for etisalat network ? We are actually stuck with our development.
There is no way for anyone outside of the Supabase devs working it to know, if even they do, as it appears dependent on an ISP to remove blocks. The status page would change if they have useful info.
Well, not adding no update is just frustrating… at least inform that conversations have started and some procedures are being put in place to overcome this…. Not knowing is a killer…
still the issue is not resolved but in the status page shows that the issue has been resolved on Sept 3. All my production app are running in supabase db and clients are pressuring me that the app are not working. It is actually a wall of shame to supabase that they are not able to fix the issue for more than 5 days and not able to disclose the actual reason on supabase. Lost my trust on supabase.
In the Supabase dashboard, where can I set the Allowed CORS Origins? I can't find it. Can anyone help me?
There is no setting for CORs in Supabase. Nothing is blocked.