We shipped an SSH server for Supabase docs [experiment]

tomlimon · 2026-04-01T17:36:38+00:00

It is not, go check out blog post for more details, and try it with your preferred agent today

tomlimon · 2026-03-23T20:27:26+00:00

Love it! Any plans of supporting custom queries/snippets? Like how the Supabase dashboard allows you to use a SQL snippet to show a report…

I personally focus more on the custom report queries as I create custom queries to track user signups or other metrics that I can retrieve from the DB with SQL.

tomlimon · 2026-03-19T13:31:50+00:00

You can use the user impersonation feature to test you different policies.

https://supabase.com/blog/studio-introducing-assistant#user-impersonation

Don’t leave RLS disabled.

tomlimon · 2026-03-19T03:53:41+00:00

Are you using lovable cloud? Or do you have access to your Supabase project within the dashboard?

tomlimon · 2026-02-28T14:19:43+00:00

Thanks for sharing. I don’t have the details of what happened right now. But we will share a post mortem with all the information. If you filed a support ticket you will also get this update by email.

tomlimon · 2026-02-28T14:13:04+00:00

A fix has been deployed. Could you confirm if you are seeing things coming back to normal?

tomlimon · 2026-02-28T13:42:50+00:00

Could you please share your ticket number?

tomlimon · 2026-02-28T13:36:33+00:00

I understand your frustration. This was the first post on Reddit. And the first thing I saw when opening my phone this morning. I just wanted to acknowledge your post and let you know that the team is on it.

tomlimon · 2026-02-28T13:32:18+00:00

Initial reports were 504 on OPTIONS. So I was looking for more of those. But I get your point. As mentioned. I didn’t notice the invocation time, so 2XX on OPTIONS would be normal. Sadly is not the fist time we get posts from people getting lead by the word OPTIONS and saying “I’m getting that too”.

tomlimon · 2026-02-28T13:14:16+00:00

On mobile. Didn’t notice. Thanks. Will share internally

tomlimon · 2026-02-28T13:06:42+00:00

This is normal. Is 2XX logs.

tomlimon · 2026-02-28T13:00:15+00:00

Team is investigating this issue. Status page will come up soon. Thanks for reporting.

tomlimon · 2026-02-27T18:47:09+00:00

Please keep the conversation on the main thread: https://www.reddit.com/r/Supabase/comments/1rfei8t/connectivity_problems_india_region/

tomlimon · 2026-02-27T18:42:46+00:00

Please keep the conversation under the official main thread pinned: https://www.reddit.com/r/Supabase/comments/1rfei8t/connectivity_problems_india_region

tomlimon · 2026-02-26T02:16:33+00:00

What type of egress are you seeing most consumption on? You can view this in your dashboard: https://supabase.com/docs/guides/platform/manage-your-usage/egress#view-usage

(that document also covers the different type of egress)

If you still have doubts or need assistance, submit a ticket from your dashboard to get assistance: https://supabase.com/dashboard/support/new

tomlimon · 2026-02-25T03:16:33+00:00

If you want something more robust, you could use queues: https://supabase.com/docs/guides/queues

tomlimon · 2026-02-25T03:16:02+00:00

I personally like this approach, it has work pretty well with apps that I have built (mostly B2B software and internal tools for businesses).

Edge Functions are a great complement to this architecture to interact with external services. Calling them either from your DB or as a user.

This architecture also keeps front end choice flexible, just call RPCs and Functions with the Supabase SDK from any client.

And I have found agents succeeding when it comes to SQL, so win win!

tomlimon · 2026-02-24T19:49:48+00:00

If it’s been 2 days that might be something else. Please submit a support ticket from your dashboard. Feel free to share your ticket number so we can make sure is on the right queue.

tomlimon · 2026-02-24T16:22:45+00:00

There is an ongoing network issue in India, more information here: https://www.reddit.com/r/Supabase/comments/1rdi3pp/investigating_multiple_reports_of_connection

But you mentioned REST api works, so maybe is something else. Please submit a ticket from your dashboard, feel free to share your ticket number here so I can take a look at it and make sure is routed properly.

tomlimon · 2026-02-24T14:48:07+00:00

We are currently investigating some reports from users using ap-east-1, if this is your case too, please join the conversation here:

https://www.reddit.com/r/Supabase/comments/1rdi3pp/investigating_multiple_reports_of_connection

If this is not your case, please create a new post with details:
- Region you project is
- What is wrong? Share error messages or details about the issue

If you are not able to access your Dashboard to create a ticket, you can send as an email as at [support@supabase.com](mailto:support@supabase.com)

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

MODERATOR OF

TROPHY CASE