Degraded login via Vercel

What to do

• Check whether your product depends on Groq. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 16h 7m it lasted.

  Anything that failed between 2025-09-18 01:38 UTC and 2025-09-18 17:45 UTC may need a replay.

• Subscribe to Groq's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=groq works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Groq 3

1. investigatingSep 18, 2025, 1:38 AM UTC

   Following the login system upgrade earlier today, we’ve identified an issue with Vercel-initiated logins. Users starting login from Vercel may see an error. Other login methods are unaffected. The team is working to identify the cause to remediate. **Workaround:** Log in directly at the Groq console using your usual method. We will provide an update when there is a material change.

   provider

2. monitoringSep 18, 2025, 2:32 AM UTC

   A small number of Vercel‑initiated logins may error. Direct login at the Groq console works normally. We are coordinating on a fix with our identity provider. We will update this page if impact or timeline changes.

   provider

3. resolvedSep 18, 2025, 5:45 PM UTC

   Vercel‑initiated login is operating normally. Other login methods were unaffected. This incident is now resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.