Supabase.co domain blocked by Etisalat
Hi,
Since yesterday I am without supabase service on my apps due to the fact that the service provider Etisalat in UAE had apparently blocked the domain.
After contacting them, they have informed the same was due to intellectual property rights infringements….
What is this about @supabase ???
Would Supabase be able to reach out to them to solve the situation?
Thank you
164 Replies
Hey! Was that an official statement you got from Etisalat?
Yes it was
Have you created a support ticket?
Supabase team should contact them ASAP
Thank you! The team is on it
I was asking if you file a support ticket on the SB dashboard
Yes i did - SU-241418
thanks!
The team is already looking into this
Please keep us updated here 🙂
Sure
Several users are reporting that using a VPN works... so this could be an temp workaround for you to keep working on your apps...
Yes VPN or using DU works…. But it does not solve the disruption suffered by consumer users or our apps 🙄
Yeah, agree, what I've personally done in the past is quickly add a banner in my website
But the banner will look bad aince it will cover the whole spectrum of users including those from other countries not affected by any of this
Plus this is very relevant because people may have paid for services in these apps and now its a problem for the developers….
Yeah its a difficult situation, just sharing what I've done in the similar situations.
will cover the whole spectrum of users including those from other countries not affected by any of thisIn this country/ISP specific issues, I would post something like: *UAE users: there is an active connectivity issue with [ISP name]. Our infrastructure provider is already working on this. To use our service, please use a different ISP or a VPN. *
Be the way, tricky to incentivize the usage of VPN in UAE since its illegal and the apps released need to be registered locally. Just a potential side note.
Well, this could imply that developers are prepared for this and it’s simple… depending on the nature of the application this can actually not be that simple… as for example the publishing of new versions of mobile apps in app store etc…
Lets pray for Supabase to be able to revert this situation with Etisalat in the next hours or so. 🙈🫠
tricky to incentivize the usage of VPN in UAE since its illegaloh wow... regional challenges lets hope it gets solved! the SB team is working on it
If its urgent, you can setup a proxy server and that proxy server will make requests to supabase and forward response back to your app. Will add some latency though
Yes but again, that is an architectural change to allow these dynamic changes… not easy to implement in few hours and even less to make things approved and rolled out across platforms
true
It's probably worth it for situations like this which doesn't have any estimated time for when they will be resolved and you would stiļl have the reverse proxy for future use.
I agree but that would not come without a cost… latency and compute overhead and budget required. How much…. Depends on the app itself.
The best is for Supabase to clear itself with providers. Imagine a provider blocking Azure or AWS 🙂
What I'm stating is that whilst Supabase tries to clear itself your users are experiencing downtime which could be resolved by a reverse proxy. Just a suggestion here, not telling you what to do.
will custom domain fix this issue?
No as it's likely the IP that is blocked and not just the
supabase.co domain name.A pool of IPs I suppose?
I understand. My point is that its not an easy route and it probably takes less time for Supabase to sort this with the provider.
This happened on my product hunt launch date 😂😂😂 thinking of seriously migrating at this point… and nothing yet from support
By the way this is happening more than 24 hours ago already
Yes. There were 2 users yesterday afternoon reporting it here. It was not until last night more users reported here so it got escalated. Unclear how many support requests were generated. No Github issues I observed. We need 3 or more issues to escalate from a user helping user forum to the Supabase team.
Yesterday I also created another ticket with the issue. Was still not aware it was a provider blockage situation. 🙁
It's still happening until now. Using VPN does work but as you said it's not a real solution for users
Oh lol and here i thought it was my router 😂
it works on 1.1.1.1
It took me sometime to figure it out lol, until I saw this post
Guys, create support tickets and send the ticket numbers here please so we can speed this up
If anyone wants to go down the path of setting up a proxy server, you can use this config. So far, I've tested with auth, rest api, realtime (postgres_changes) and storage.
docker-compose.yaml
Caddyfile:
Setup with js sdk
Shouldn't take more than 5 minutes
Let me know if some service isn't proxied
Any feedback on if the team was already able to contact Etisalat?
They are working on it, the status page is what you should follow for updates https://status.supabase.com/incidents/spyxwjqn7d2f
🙁 there is no update there. Taking time to solve this. 🫠
That is the update and yes companies take time to respond to companies too.
e& must be busy auditioning their next celebrity ambassador.
Ye think this one is definitely gonna take time, but having the banner on support page is a good indication for me that they won’t remove till sorted so yea
Selling to US customers for now lol
M🙄😶🌫️🫥😳
This is not about selling… is about letting businesses down at the moment in the region. That is not a light thing for sure.
Man, it’s Etisalat.. same way they’re banning voip, and porn and vpn and the list goes on, probably some douche used supabase the wrong way and got us all f***
It sucks I know, this literally happened during my product hunt launch and ruined it all for me
But yea
Setup proxy it works
I’m gonna do it even if this gets solved, can’t afford it happening in the future
The one thing I’d blame supabase for is not being pro active, they started acting 2 days after the issue started, but it is what it is
Again this is not Supabase support and this is where user's reported the issue two days before. Supabase would not be aware of the issue until it gets escalated or there are many support tickets in stating the issue. Also it being reported on a weekend isn't really gonna get it noticed quickly too as there are less Supabase support staff working on the weekend (just like every other company out there and this would be first line support too who cannot really escalate something this big with an ISP).
At the point we notified Supabase when we had enough people reporting the issue is when they started to look into it.
And again, I’m not treating this as supabase support, I’m expressing my opinion.
This is such a long message from you, while I’m literally saying it’s not supabase fault and I added two lines expressing something that could’ve been done better.
So instead of defending supabase as if they pay your salary, you shouldn’t be this salty and understand how frustrating this is to us and our customers and take a step back and report to supabase.
seriously
Any update guys?
@silentworks @inder will custom domain fix this problem?
I see, thanks
Not sure if I should create another discussion for this, but I tried the reverse proxy solution for local development and it didn't workout for me, I get a 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY' from my routes (using NextJs) specifically with the supabase.auth function (I didn't test other function).
I tried to understand the issue and concluded that for development it wouldn't work since the reverse proxy itself would forward the request using the same ISP, so it isn't really solving any issue, but I may be misguided in my understanding here.
I hope I can get some direction on how to set it up for development if there really is a difference between production and development setups.
This is meant to be used on a server. When using locally, you're right that the reverse proxy will be using your own ISP to make http requests.
Is there another solution for development scenarios?
supabase cli
What you mean by some douche?? Supabase should be cleared on all providers as per the services they deliver… its not their fault of how customers end up using the service. Those can be reported and dealt accordingly but they can never trigger a blacklist on a provider.
Imagine a “douche” using Azure app and publishing some weird content and they go and block entire Microsoft Azure customers 😂
That would never happen… why? Microsoft must have some sort of way to clear their services/IP Ranges with the providers no?
Could you expand/explain this a bit more, how can I use supabase cli to workaround the ISP blocking an IP?
I meant use supabase cli to start a local supabase instance and use that for your local development.
Alright, Thank you
I did it in cloudflare, works so far
Hi @inder
Hope you are well
Sorry! I'm new to this but what service did you use to host this?
I tried doing the same using render and created a simple node js app as well.
but it is not working for my client's in UAE?
Any help would be greatly appreciated
I ran the container on an ec2 instance. What error do you get?
5G is now affected too, different ISP
Anyone else?
Here is a repo to quickly deploy a proxy to Supabase, this should allow UAE users to by pass the
supabase.co ban.
https://github.com/singh-inder/proxy-to-supabase-cloud
Please note that:
- This is not an official solution, is a workaround provided by a community member.
- The repo mentions render, but it acutually could be deployed to any other PaaS that supports nodejs.
- It has not been completely tested in production, so there might be things that won't work properly.
- Make sure you read the README.md to understand the scope of the solution.
- If you are testing this, please provide feedback (better to create an issue on github) so this can help other community members while the issue is solved.I’ve done a proxy on digital ocean yesterday, it works on some things and breaks on others, will give this a go thank you
Has Supabase experienced a regional issue like this before, or is this the first time?
Never from my experience, been using supabase since it first came out
Experiencing this on DU network as well.
There have had outages with cloudflare and AWS but never had an ISP ban that I've seen or the ISP was so small the issue was never figured out to be that.
Etisalat having beef with Supabase was the last plot twist I expected this week.
It doesn't even make sense
Hey @DevilsBlade0 let us know how it went
I gave up, waiting on a fix from supabase or a work around, the whole proxy thing does more damage than fixing unfortunately
Yea the carpet ban is quiet lazy from Etisalat engineers in my opinion, but I’m sure they know something we don’t.
Guess we’ll have to wait and see
hi, all just wanted to reiterate I'm facing the same issue. I've raised it with E& as well as Supabase (although I'm currently on a free plan). I've also raised awareness and posted to LinkedIn my frustrations (tagging E& and Supabase). I'm hoping this is resolved asap, but will need to start looking at a work around (reverse proxy as some of you have mentioned), however I'm not that clued up and building my site through Lovable. Let's hope this is fixed asap!
@inder Brother, can you tell me which Fastify GitHub repo I should deploy on Render? I have deployed, as, as you can see in the image, and follow the instructions you have given in your proxy-to-supabase-cloud, and I am getting CORS error. Can you tell me where I am making the mistake?
In the supabase client, are you using the url which was generated by render after deploying?
Yes
I have stored the URL in the .env file
Wait let me check
Okay, thanks, bro
I don't see any cors errors. Are you sure that the values you've added are correct?
This is how it should look. No trailing slashes
and inside app, no trailing slashes
@inder Let me check
@inder Thank you so much, brother, now it's working properly. I was using another GitHub repo.
Hey everyone it appears that now the blockage is global in UAE for both providers Etisalat and DU. DU was working previously for me but now it is not anymore.
Can anyone confirm as well?
How long is this going to take? 🥲
I think i should self-host my future supabase projects
https://status.supabase.com, yep it's official
This is insane :(((
Firebase 🙁
Supabase trying to reach out to them via email or what not is not going to work… this cannot be taken like this. There should be a comms channel to facilitate these issues. Saying they are not responding means the comms channel is far from being the ideal one…
Now to help the situation the Middle East loses a fiber optic cable under sea 😂🙈
Hi , first thanks for your effort
In my project all services are connected except storage , can you help me on this?
Hi, please share the error you get
Solved bro thanks
I had reached to TDRA (the Regulators in UAE) about the blockage, and they have responded as follows;
Case Number BUB-25-10XXXXXXX
Case Date 9/9/2025 12:51:44 PM
Closed Date 9/10/2025 9:53:43 AM
Rejection Reason Dear Applicant, Kindly note that the URL is not blocked on either the Etisalat or Du networks. Please check with your service provider. Thank you for contacting TDRA.
** Sadly, Nobody is taking the ownership and users like us are significantly affected and figuring out move out plans from supabase.
What URL you send them for validation?
supabase.co
That is a lie. I got confirmation from Etisalat os is blocked due to copyright infringement
@Luis Simões sent you a DM could you please check?
I’m not aware of how things work across this organization that you talked with and the ISPs. But I imagine ISPs can take individual actions?
Will check the DM, but yes I spoke to the ISP
A user posted this in one of the other threads. Can anyone in UAE confirm?
Nothing on my side yet unfortunately, hopefully it’s gradual and we all get back online soon.
Network Etisalat WiFi
Can’t find this tweet for some reason
its on his replies section. can search by keyword "supabase uae" filter by latest
I got one workaround for UAE network block. and its working well. no proxy needed.
just change your supabase url from .co to .in
Have you verified with UAE users?
yes, client sent the video.
Thank you guys for the solution and help
@aksh have you verified with all the services?
I think it should work but just to be sure
I am using almost all services of the supabase from auth, database, storage working well.
and realtime?
nah
If the DNS is resolving now, I believe that should work as well. But @Bob365 as you're in UAE can you test if the realtime service works fine?
Will check realtime service. Give me a couple of hours though
Wow this works?
Amazing will give it a shot
A couple of users have reported that it does
Ok will give it a try and report back
I had a chat with supabase support about this and they don't recommend to use
supabase.in for the ISP issue. If you're working locally, then update DNS server to 1.1.1.1 and use proxy in productionIt works but not for storage, gotta update those links too
Ok noted thank you, I will wait
Hi everyone, I used the
.run url and it works for me right now, I'll keep yall updated if something breaksJust want to let you know there are some limitations with this url. The auth callbacks and storage urls still generate with supabase.co domain
i swtiched the auth callback from google so it works but i definetly need to check if the storage one works.
okay it definitely breaks some aspects. well as long as my user doesnt refresh their page, we gucci 😂
You can add a banner, DONT REFRESH
well i havent published my webapp yet so only my uae friends are suffering
Custom domains seem to be working
Some users have mentioned that in reddit posts
Haven't tried it myself
Otherwise the prebuilt proxy is the only solution
I've added a custom domain but the storage URLs are still not accessible even though the users are accessing the new (custom domain) storage links.
What am I missing? followed the guide from YT to create custom domain on Supabase
Do you se your domain ready and confirmed to make the switch on the Supabase dashboard?
Yup .. I've activated the custom domain and made the switch on production.
Got a friend in Dubai to use the platform, open a storage URL link with the custom domain and it failed to load.
Oh.. I believe storage links do get assigned to the Supabase.co domain
So that’s why it does not work
The rest works fine?
https://db.postnitro.ai/storage/v1/object/public/media/editor/external/cd13ea0d-4e09-419b-bf22-0cacfd4d82f3-pexels-photo-2599244.jpeg
This is the storage link .. see how it starts with our custom domain (db.postnitro.ai)
This link opens up fine for me but for the friend in Dubai it would not load
We use these URLs in our editor so we need them as it is .. for all users in UAE they are broken URLs.
The custom domain is still active but I've reverted back to the original domain on production
Hi Muneeb, has your friend shared what error they see in the browser console?
this is what they see .. the main domain postnitro.ai is accessible to them .. the sub domain is not
I'm in the UAE and can confirm that it doesn't work and I'm facing the same issue with my project; however it's not only for storage, but also for authentication and db api.
I think reverse proxy is the only solution which works for now https://github.com/singh-inder/proxy-to-supabase-cloud. Step by step tutorial to set up this proxy: https://discord.com/channels/839993398554656828/1413445192710885446/1414130057202372670
if you want to setup caddy https://discord.com/channels/839993398554656828/1412456024912302171/1412490597473849375
we aren't using auth and all supabase functions are handled from the server not the edge so no issue with them .. the only issue is with the public URL from storage as we are using them directly
seems like a pointless overhead to do this for all users as this issue is isolated to a specific region and also this would increase latency .. good suggestion though
I agree with the latency point. But not completely pointless for people who can't afford downtime while this issue persists.
Or if you have a nexjts app and are not using realtime then this is also a solution https://discord.com/channels/839993398554656828/1413049145215684648/1415375149905088533
This way nextjs server acts as a proxy
I don't think this would work .. the reverse proxy would work I guess with our custom domained storage URLs .. the issue is only primarily for storage URLs in my case
Why? I assume you will deploy nextjs app to either vercel or a standalone build for docker image and deploy it to some cloud. And I don't use nextjs so correct me if I am wrong but as far as I can tell almost everyone is using react 19 and streams jsx from server. This way server makes request to supabase, there won't be an issue of ISP and server responds back
You're right about SSR for API calls, but the issue is with storage URLs specifically. We're using Supabase storage URLs directly in <img> tags (like <img src={slide.image.url} />). Even with React 19 and server-side streaming, the browser still needs to fetch these images directly from Supabase's storage domain.
The server can render the HTML with the image URLs, but the actual image loading happens client-side when the browser makes GET requests to those URLs. Since the ISP blocks Supabase storage domains, users in the UAE can't load the images even if the rest of the app is server-rendered.
We'd have to proxy every image request through our server (not just the initial HTML), which would significantly increase bandwidth costs and latency for all image assets. That's why the reverse proxy solution makes more sense for this specific regional blocking issue.
Yeah we're on the same page about costs. If you already rent a server then caddy will be a better choice. Otherwise you can deploy the nodejs proxy to render
Render has a free tier
So problem is Red Sea cable cut looks like.
https://timesofindia.indiatimes.com/business/international-business/undersea-cables-cut-in-red-sea-internet-disrupted-across-asia-middle-east-india-pakistan-among-affected/amp_articleshow/123744508.cms
The Times of India
Undersea cables cut in Red Sea: Internet disrupted across Asia, Mid...
Internet services faced disruptions across Asia and the Middle East due to severed undersea cables in the Red Sea. The incident impacted connectivity in countries like India and Pakistan, with potential causes ranging from ship activity to deliberate attacks. While the Houthi rebels have denied involvement, Yemen's government accuses them of thr...
Does Supabase use Azure in their backend?
This ISP issue has been going on since Sep. 1. The red sea issue was reported on Sep. 6
Not that I know of. It's mainly AWS and Cloudflare from what I know.
Have anyone confirmed that it seems working recently?
Yes its workig now without VPN or proxies.
For both Etisalat and Du?
Another user has confirmed working for them too
Hi @aksh can you also confirm this with your users
My client has to confirm, as I am not currently in UAE
It's working for me on Etisalat.
DU is still not working
Hey all! Many people confirming Etilasat is working. We are missing confirmations from Du users… anyone using Du can confirm if is working too?
I am using DU, still not working
What is the difference between using .co and .in?
my project is in prototyping so am inclined to use .in for the URL as this seems to be a temporary issue which should be rectified
DU is still not working
New update.
Etisalat works here
So happy, finally
i just finished migration to convex and this happens hahahahaha imma kms
time to roll back
hey everyone, could someone confirm if du is also working now or not yet?
we were informed that they should have restored the access
Will try now
No still, tried on 5G from Icognito chrome
Tested auth and storage
thank you, we will pass this to the UAE authorities. i believe du is working on restoring access now
Prefect thank you guys
hey, sorry for bothering you, but has du started to work again now?
Hey sorry just saw this now.
Yes it’s working on 5G, just tested
Supabase postgres url still not working here in Dubai
and i am using ezlink which is kind of affilated to DU
What error do you get?
0 | res = resolve
41 | rej = reject
42 | }).catch((err) => {
43 | // replace the stack trace that leads to
TCP.onStreamRead with one that leads back to the
44 | // application that created the query
45 | Error.captureStackTrace(err)
^
DNSException: getaddrinfo ENOTFOUND
syscall: "getaddrinfo",
errno: 4,
code: "ENOTFOUND"
at <anonymous> (/Users/himanshum/Projects/bun/whatsappchat/node_modules/pg-pool/index.js:45:11)
when i change to mobile data net of du this work finehave you contacted the provider?
yes
any response?