Groq Outage Check
Is Groq Down Right Now?
✅ Groq is up and working normally. Checked: 4:06 AM (GMT+8).
Auto-refreshing live data in 60s
Groq's Official Status Page
- Groq LPU inference API calls
- Apps using Groq for fast LLM responses
- Groq-hosted Llama and Mixtral models
| Component | Status |
|---|---|
| API | Operational |
| Canopy Labs Orpheus Arabic Saudi | Operational |
| Canopy Labs Orpheus English | Operational |
| groq/compound | Operational |
| groq/compound-mini | Operational |
| llama-3.1-8b-instant | Operational |
| llama-3.3-70b-versatile | Operational |
| meta-llama/llama-4-maverick-17b-128e-instruct | Operational |
| meta-llama/llama-4-scout-17b-16e-instruct | Operational |
| meta-llama/llama-guard-4-12b | Operational |
| meta-llama/llama-prompt-guard-2-22m | Operational |
| meta-llama/llama-prompt-guard-2-86m | Operational |
| moonshotai/kimi-k2-instruct-0905 | Operational |
| openai/gpt-oss-120b | Operational |
| openai/gpt-oss-20b | Operational |
| openai/gpt-oss-safeguard-20b | Operational |
| qwen/qwen3-32b | Operational |
| Website | Operational |
| whisper-large-v3 | Operational |
| whisper-large-v3-turbo | Operational |
SLA Grade: B+
Based on 90-day verified uptime
99.444%
Uptime
70m
Mean Resolution Time (MTTR)
7
Avg Incidents / Month
32d ago
Last Incident
90 Days AgoToday
Groq Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Groq Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 52m
Affected: Website, DNS Services
Groq Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 32m
Affected: Website, DNS Services
Groq Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 46m
Affected: Core Service, Website
Groq Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 1h 25m
Affected: Core Service, Website
Are you having problems with Groq?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns. - 3Check with alternative networkTry loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, Groq maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 70 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.