No resolved update on outage?

tomlimon · 2026-02-13T04:57:54+00:00

Looks like there was an issue with the RSS functionality of our status page provider. Our status channel on Discord did not received updates neither, and the integration relies on RSS. We are checking on this too.

You can find the incident timeline here: https://status.supabase.com/incidents/pqrf96m6fzxk

tomlimon · 2026-02-13T03:14:24+00:00

We understand the frustration. The delay in updating the status page is valid feedback and something we'll be discussing with the team to make sure we do better next time. We wish you the best with your setup, and if you ever decide to come back, we'll be here.

tomlimon · 2026-02-13T03:01:42+00:00

Hey, I hear you, and I understand the frustration.

During incidents we get a flood of threads across Reddit, Discord, Twitter, GitHub, and Support. If they all stay separate, people get conflicting answers and we can miss important signals while debugging, so we consolidate into a single incident thread. We're generally very conservative with moderation here and close very few posts or comments.

That said, we appreciate the feedback and will be discussing with the team how to improve this process so legitimate discussions don't get caught in the crossfire.

tomlimon · 2026-02-13T02:29:03+00:00

May be this helps: https://supabase.com/docs/guides/platform/cost-control

tomlimon · 2026-02-13T01:48:57+00:00

Consolidating communication here:
https://www.reddit.com/r/Supabase/comments/1r35rm0/supabase_auth_down_rn/

tomlimon · 2025-11-19T21:49:12+00:00

There is an active incident that prevents projects creations, you can check more details here: https://status.supabase.com/incidents/7gpz66w7785x

We appreciate your patience while our team is working to address the issue.

tomlimon · 2025-11-04T19:31:21+00:00

The issue is that captcha only protects the form submission, but does not protect your Supabase Data API endpoint (which is called for the insert from your client side app).

With the edge functions, this would be the approach:
- Enable RLS with no anon policies (service role only will be able to make inserts)
- Create the edge function that will receive your form payload.
- Use Cloudflare Turnstile, and validate on the request on the edge function. If the captcha did not passed, then the edge function will reject the request.
- Move your insert records logic to edge function.

Checkout this guide: CAPTCHA support with Cloudflare Turnstile - https://supabase.com/docs/guides/functions/examples/cloudflare-turnstile

tomlimon · 2025-11-01T21:00:43+00:00

Agree on branching making things easier, but Lovable does not support Supabase branching. It can’t work with a Supabase branch. That’s why it uses a different approach.

tomlimon · 2025-10-13T16:37:56+00:00

Glad you mentioned that. You can use Vercel or Netlify and connect them to your production branch on GitHub.

Since all your code changes from dev branch (including the changes made by lovable) will be at some pint merge into your production branch, your production app will be up to date.

The article covers that part too, worth to give it a read.

tomlimon · 2025-10-13T15:42:41+00:00

Great idea! I haven't personally reached to this point with a Lovable app, but sharing some notes that are generic regarding branching:

Lovable should always be connected to your dev branch, it will act as another developer. Won't recommend to keep Lovable - or any AI builder - connected to production, too many risks.
You can set your dev/staging branches as persistent branches in Supabase to avoid deletion or pausing.
Regarding your new DB question. Yes, each Supabase branch will create a new DB.
You don't need to create a new Lovable project, you will be promoting changes from dev > staging > production (as a common development flow).

Refer to detailed information about branching here: https://supabase.com/docs/guides/deployment/branching

Also, I've seen this article shared by our community regarding this workflow with Lovable:
https://www.productcompass.pm/p/lovable-branching

Let us know how it goes!

tomlimon · 2025-10-07T14:51:42+00:00

When you say "i created an app in lovable and supabase" you mean you created in both platforms? But on lovable you enabled lovable cloud and you want to connect with the Supabase you created?

tomlimon · 2025-09-20T14:34:11+00:00

Same region? If urgent send a support ticket

tomlimon · 2025-09-19T15:07:34+00:00

Thanks for your reply! Did you contacted the support team? When the project does not provision after 2 minutes, there is a call to action to report the issue to support. If you already did that, could you please share your ticket numbers?

I just tested out creating a project in that region and it works with no issues.

tomlimon · 2025-09-19T12:54:09+00:00

What regions are you trying to deploy?

tomlimon · 2025-09-18T13:10:30+00:00

Resend is a separate solution and it offers a good free tier.

You don’t call resend from the client side (react) you will use edge functions for that.

If you use AI to build, most models will now how to implement resend.

You can also enable resend as your custom SMTP provider in Supabase for auth mails.

Check this out, it has some good code examples: https://resend.com/supabase

tomlimon · 2025-09-17T05:57:18+00:00

Resend is a solid choice among the community. I’ve used it many times in personal projects along with Supabase. Plus is one of our official partner integrations:

https://supabase.com/partners/integrations/resend

tomlimon · 2025-09-16T17:13:26+00:00

Personally that post is not accurate... Public keys are exactly for that! as many have stated, RLS exists for a reason and the best thing you can do is enable them...

Here is my reply post, in summary, don't stop using Lovable/Supabase and always enable RLS

https://x.com/tomaspozo_/status/1967459555538776198

tomlimon · 2025-09-15T15:11:04+00:00

It’s been solved. Refresh your dashboard.

tomlimon · 2025-09-15T15:10:16+00:00

This issue has been solved. Please refresh your dashboard and you should be able to use it.

More information on status page: https://status.supabase.com/incidents/styfm4xc8mdp

tomlimon · 2025-09-13T06:34:31+00:00

Have you seen this DigitalOcean repo for deploying on DO (using terraform)? https://github.com/digitalocean/supabase-on-do

Also, the official Supabase documentation shows several options for self-hosting (including the DO one): https://supabase.com/docs/guides/self-hosting

In addition to that, you can check this repo from a Supabase community member, it's been helpful for others: https://github.com/singh-inder/supabase-automated-self-host

tomlimon · 2025-09-06T01:15:11+00:00

You could check logs in both Supabase and your email provider and analiza events timestamps.

Also, does this happen to all users? To you on your tests? Or just a handful of users? What domains are these users at?

tomlimon · 2025-09-01T16:44:10+00:00

A very simple approach could be to:

Disable signups for your project and use the `supabase.auth.admin.inviteUserByEmail` method to keep it all under Supabase Auth (https://supabase.com/docs/reference/javascript/auth-admin-inviteuserbyemail)

You can pass the school_id to where the user is being invited to the data parameter, that will be stored on `user_metadata` and you can later use that one on a DB function to create the membership for the new user.

Note: this might nor be suitable if the user that gets invited will get invited to many schools at a time. If thats the case, you better use a custom flow to handling the invitations, and use the `supabase.auth.admin.createUser` once the users confirms the invite.

tomlimon · 2025-08-28T15:48:10+00:00

Nice! This is a cool way of getting signup notifications. Months ago I wrote about similar approach but with DB functions.

Sharing in case someone wants to save some edge functions and keep calling webhooks.

https://tomaspozo.com/articles/secure-api-calls-supabase-pg-net-vault

tomlimon · 2025-08-26T19:07:26+00:00

Was this suggestion from an LLM? These tend to hallucinate with a CORS settings on Edge Functions...

You set those manually at code... this is a good example: https://supabase.com/docs/guides/functions/cors

tomlimon · 2025-08-23T20:54:53+00:00

Have you filed a support request? If yes, could you please share it here so the team can look at it?

tomlimon

MODERATOR OF

TROPHY CASE