Is Groq down?
Loading the latest status…
Is Groq down right now? Live status from Groq’s status page, our own checks and user reports, updated every minute.
- Official status
- Reachable
- Reports in the last hour
Detailed data for this service is briefly unavailable. The status above comes from our latest check.
Groq’s status page
- API
- llama-3.1-8b-instant Production
- llama-3.3-70b-versatile Production
- openai/gpt-oss-120b Production
- openai/gpt-oss-20b Production
- whisper-large-v3 Production
- whisper-large-v3-turbo Production
- Website
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.groq.com)
By region
| Region | GroqCloud API api.groq.com |
|---|---|
| N. Virginia | |
| Oregon | |
| Frankfurt | |
| Singapore | |
| Tokyo | |
| São Paulo |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked Groq ourselves since Oct 28, 2026. Earlier days come from its status page.
1 day with problems in the last 90 days.
Recent incidents
Incidents: 1 in the last 30 days and 1 in the last 90, lasting a median of 23 min.
- GroqCloud Console Errors Affecting Multiple RegionsDegraded23 min
If Groq isn’t working for you
Groq runs open models on its own LPU chips and offers a fast, OpenAI-compatible inference API through GroqCloud.
Common Groq errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
429 Too Many Requests | Too many requests were sent in the time window your rate limit allows. | Your side | Throttle requests and respect the rate-limit headers before retrying. Source |
498 Flex Tier Capacity Exceeded | A Groq-specific code: the flex tier is at capacity and the request was not processed. | Heavy load | Try again later, or use the on-demand tier for traffic that cannot wait. Source |
503 Service Unavailable | The server is not ready to handle the request, often because of maintenance or overload. | Heavy load | Wait before retrying and check groqstatus.com. Source |
500 Internal Server Error | A generic error on Groq's servers. | An outage | Retry later and contact support if it persists. Source |
401 Unauthorized | The request lacks a valid API key. | Your side | Check that the API key is present and valid. Source |
Is it just you?
- Check the rate-limit headers on your responses; a 429 at your limit is account-level, not an outage.
- Try another model on GroqCloud: capacity problems often hit one model at a time.
- A 498 only affects the flex service tier; requests on the default tier may still work.
- Check groqstatus.com and the reports on this page before changing your code.
Alternatives to Groq
Questions
It is a Groq-specific status that means the flex tier is at capacity and your request was not processed. It is temporary; retry later or use a different service tier.
Check the status code: 429 and 401 are about your limits or key, while 500, 502 and 503 are on Groq's side. This page checks Groq's official status and its API from several regions.
Sources: console.groq.com, groqstatus.com
Get alerted when Groq breaks your app.
If your product depends on Groq, your users feel its outages too. Point a Site Qwality monitor at the Groq endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.