Threads
Loading user profile...
If you’ve got any interest in improving our supabase docs/examples, shoot me a message: terry@supabase.io
Have you submitted a support ticket? Please send me the id and i’d be happy to look into it.
It's true actually. You can have as many orgs as you want. The only limitation is that you can only have 2 free projects active at one time. You can store any number of projects inside any number of orgs as long as only 2 are active. **How:** \- Click the project name dropdown in the header \- Click "+ New Organization"
Yes, as others have said, you can have as many projects as you want, you just pay for compute once you're on Pro. There's a calculator on [https://supabase.com/pricing](https://supabase.com/pricing) which helps you estimate what your costs will be. https://preview.redd.it/ew0z02n127qg1.jpeg?width=2514&format=pjpg&auto=webp&s=f757af8b12a6f866b5910e09d87038eae6296097
Vault is how you store and use secrets: [https://supabase.com/docs/guides/database/vault](https://supabase.com/docs/guides/database/vault)
Model as much as you can up front and then just do it as you go. I always use declarative schemas. https://supabase.com/docs/guides/local-development/declarative-database-schemas
Nothing known atm. Anything in your logs?
Thanks for the heads up! Will do. If they recall what the issues were (and/or what guides they went through, please lmk!)
Sounds project related. Nothing known happening in that region at the moment. Does a restart fix it?
Sorry you ran into this one. We make it pretty explicit in a bunch of places that you need to setup your own email server, but agreed this is something that new people might miss. [https://cleanshot.com/share/MG99Mjj5](https://cleanshot.com/share/MG99Mjj5) (The reason we need to do this is probably obvious and not relevant here, but for the sake of completeness...) We host email for every app on the platform, which means deliverability and reputation are shared concerns. If we made email “just work” out of the box (auto-sending from our infrastructure), it would be easy for bad actors or even just misconfigured apps to kill deliverability for everyone. So instead, we lean toward giving you the primitives (Auth emails, SMTP config, etc.) along with integrations to let you do this on your own. Curious what you think might have helped surface this better for you so you would have seen it before launching?
Curious what parts of this we could fold into supabase.com/ui
I work at Supabase, so I'm pretty biased, but my best un-biased take: Both are great, and both would make a good choice. Give Supabase extra consideration if you think you'll want the extras down the road — realtime, storage, auth, edge functions. Edge functions especially give you a lot of flexibility (might be less of an issue, since you've got a separate backend). The real beauty of Supabase imo is that you can add these things in as you need them.
Just had a look and unfortunately I'll need to get our infra team to have a look at this one. Hopefully they won't be too long in getting to it.
Have you submitted a support ticket? Happy to take a look if you give me the id
Might have gotten caught in our spam filters. Are you able to create a support ticket? Happy to take a look for you.
Sticking Ivan's answer to the top to make sure latecomers see it: [https://www.reddit.com/r/Supabase/comments/1rkp1rq/comment/o8r9zwz/](https://www.reddit.com/r/Supabase/comments/1rkp1rq/comment/o8r9zwz/)
Hard to give a conclusive answer on this without seeing logs. If you're open to submitting a support ticket, we'd be happy to take a look at it.
Hi all — sorry about this one. This was related to an issue with our management api. Should be fully resolved now. More details here: [https://status.supabase.com/incidents/m52hrr7th0mj](https://status.supabase.com/incidents/m52hrr7th0mj)
Very sorry you had issues here. This was related to an issue with our management api. Should be fully resolved now. More details here: [https://status.supabase.com/incidents/m52hrr7th0mj](https://status.supabase.com/incidents/m52hrr7th0mj)
Hi all — thankfully, this has been resolved. We very much appreciate your patience as we navigated this. [https://x.com/supabase/status/2028917942910657023](https://x.com/supabase/status/2028917942910657023)
Hi all — thankfully, this has been resolved. We very much appreciate your patience as we navigated this. [https://x.com/supabase/status/2028917942910657023](https://x.com/supabase/status/2028917942910657023)
Hi all — thankfully, this has been resolved. We very much appreciate your patience as we navigated this. [https://x.com/supabase/status/2028917942910657023](https://x.com/supabase/status/2028917942910657023)
Hi all — thankfully, this has been resolved. We very much appreciate your patience as we navigated this. [https://x.com/supabase/status/2028917942910657023](https://x.com/supabase/status/2028917942910657023)
Hi all — thankfully, this has been resolved. We very much appreciate your patience as we navigated this. [https://x.com/supabase/status/2028917942910657023](https://x.com/supabase/status/2028917942910657023)
hours! curious what you're doing if you're open to sharing
Hey there — very sorry for the issues you've had on this. The team is actively looking at this right now. Will communicate further via the support ticket.
Curious how much longer you need. We released background tasks a while back which gives you 6m40s on paid plans. [https://supabase.com/blog/edge-functions-background-tasks-websockets](https://supabase.com/blog/edge-functions-background-tasks-websockets)
Per our status page, discussions with authorities there are progressing and we're hopeful we'll be able to fix this soon. [https://status.supabase.com/](https://status.supabase.com/)
I'm obviously biased, but supabase doesn't lock you in much here. We offer auth integrations with a bunch of providers, and let you use whatever you want — clerk, betterauth, firebase auth, auth0, etc. You can migrate in our out of any of these systems into another one as you want later. If it were me, I'd start with supabase auth and see how it goes. If you decide you want to move later, move later.
Would love to see it! Also: [https://jobs.ashbyhq.com/supabase/bf46e5cf-526a-425c-951b-bf2a7f85bd9d](https://jobs.ashbyhq.com/supabase/bf46e5cf-526a-425c-951b-bf2a7f85bd9d)
Hi there — please submit a support ticket if you're still experiencing issues. Nothing known on the platform at the moment to explain this.
Sorry you've been affected by this. We're doing everything we can to address this. [https://status.supabase.com/](https://status.supabase.com/) has the latest info, particularly this part: The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: [https://1.1.1.1](https://1.1.1.1/) Google [https://developers.google.com/speed/public-dns](https://developers.google.com/speed/public-dns) Quad9: [https://quad9.net/](https://quad9.net/)
Very sorry for this. We keep the latest info up to date on the status page. We’ll continue to post updates there as we have more information. We’re doing everything we can to resolve this as quickly as possible. https://status.supabase.com
This issue has been resolved.
Here's a good place to start: [https://supabase.com/ui/docs/react/client](https://supabase.com/ui/docs/react/client)
Great thanks. Looking.
Do you have a support ticket id?
Submit a support ticket and see if the team can find any clues in the logs.
Sent it up the chain!
This gets updated manually after we know the extent of the outage across each service. It has been updated for last night. Will talk about this during the post-mortem process though to see if we can show something here prior to knowing the exact details of each service's outage.
Happy to send your project along. We get a lot of these every month and there’s limited space, but happy to forward to the team who manages this.
Thanks to you. Glad to have you along as we avoid the villain arc! :\^)
Hey there — quick update on this. We've reopened several threads that were closed during tonight's incident. Our goal with consolidation is to keep communication organized while the team is debugging the issue, but several posts tonight got caught in the crossfire that shouldn't have. We appreciate the feedback and will review our moderation process after this.
This post shouldn't have been closed. We moderated a flood of posts earlier around the outage, but this one should have stayed up. Apologies.
Hey all — apologies. I'm restoring this post. It was deleted when we had a flood of other posts and we wanted to consolidate them around a single source of info. This one shouldn't have been flagged.
Consolidating communication here: [https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase\_auth\_down\_rn/](https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase_auth_down_rn/) We'll be publishing a full post-mortem with all the technical details asap.
Consolidating communication here: [https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase\_auth\_down\_rn/](https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase_auth_down_rn/)
Update: We identified a potential internal networking configuration that may have caused the incident. We have since reverted that change and it appears services are recovering.
**Update:** We are still investigating the root cause for this incident. us-east-2 region isn’t receiving any network traffic at this point. We are still seeing some errors in other US regions, but seems to be recovering.
Consolidating communication here: [https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase\_auth\_down\_rn/](https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase_auth_down_rn/)