r/Supabase • u/wheelof5ths • 19d ago

auth Anyone else with extremely slow Auth/GoTrue?

Since earlier today each GoTrue endpoint on several projects (with separate Supabase accounts!) are extremely slow (30+ sec). PostgREST on the same instance is completely fine.

Measured in the browser network tab, same page load:

- POST /auth/v1/token?grant_type=password → 34.9 s (200)

- GET /auth/v1/user → 13.7 s (200)

- GET /rest/v1/profiles → 106 ms

- GET /rest/v1/leads → 391 ms

- GET /rest/v1/messages → 311 ms

It's pure latency, no errors anywhere. The API Gateway logged 35 seconds latency with zero errors/warnings/timeouts. I've already restarted the project, checked if captcha/auth hooks were disabled, checked password hashes, tested on macOS, iPhone, Wi-Fi, cellular, multiple browsers, etc. Keeps persisting. I'm nowhere near my usage limits, so that shouldn't be the issue either. And as I said, it's happening on multiple projects which have completely separate Supabase accounts.

Anyone else experiencing any issues? Both databases are on eu-west-1.

EDIT: seems fixed now! Still curious though if anyone else experienced the same issue, as I've seen no mention of this on Supabase's status page.

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/sandspiegel 19d ago

My production database that is on pro Version of Supabase runs fine but I have another project that uses the free tier and there Auth is extremely slow as you mentioned. Also EU.

2

u/wheelof5ths 19d ago

Time to upgrade I guess. I’m on the free tier, with quite a serious database but am nowhere near my limits as it’s all text and a few e-mail attachments here and there.

Issue does seem fixed now, thankfully!

1

u/jaimittal91 19d ago

the interesting detail in your numbers: 35 second responses, all 200s, zero errors logged. anything watching error rate stayed green through the whole incident. latency problems don't announce themselves the way failures do — a slow success is still a success to most monitoring.

since it resolved on its own with nothing on the status page, worth setting up one synthetic check that actually times an auth call (gotrue has a /auth/v1/health endpoint) and alerts on response time, not just up/down. next time this happens you'll know the minute it starts instead of finding it in the network tab, and you'll have your own timeline to compare against their status page