BREAKING: Supabase MINOR π‘ Degraded Log Explorer β Workarounds Inside
Supabase Log Explorer dashboard experiencing degraded performance. Immediate workarounds for indie hackers relying on real-time logs.
BREAKING: Supabase Log Explorer Degraded β What You Need to Know
What's Down & Who's Affected
Supabase is reporting degraded performance in the Log Explorer dashboard feature as of this incident report. This affects your ability to view real-time logs, query history, and debug requests through the web dashboard.
Who this impacts:
What's NOT affected:
This is a partial disruption (Status: Monitoring). Your applications should function normallyβonly dashboard visibility is degraded.
---
Immediate Workarounds β Do This NOW
1. Use the PostgreSQL Query Interface
Instead of Log Explorer, query logs directly via SQL: ```sql SELECT * FROM postgres_logs WHERE created_at > NOW() - INTERVAL '1 hour' ORDER BY created_at DESC LIMIT 100; ```2. Pull Logs via Supabase CLI
If you have the CLI installed: ```bash supabase functions list supabase functions logs <function-name> ``` This bypasses the web dashboard entirely.3. Use Your Application Logs
Log directly to your own infrastructure: ```javascript console.log([${new Date().toISOString()}] Event: , data);
// Send to your own log aggregator
```4. Check Supabase API Logs Programmatically
Query theaudit.audit_log_entries table if you have audit logging enabled:
```sql
SELECT * FROM audit.audit_log_entries
WHERE created_at > NOW() - INTERVAL '2 hours'
ORDER BY created_at DESC;
```---
How to Check If YOUR Project Is Affected
1. Log into your Supabase dashboard 2. Navigate to Logs β Log Explorer in the sidebar 3. Try loading recent logs β if they load slowly or timeout, you're affected 4. Check the Status Page: Visit [status.supabase.com](https://status.supabase.com) for official updates 5. Verify your app still works β run a test API call; if it succeeds, your data layer is fine
---
Alternative Log Monitoring Tools (Right Now)
Quick setup: Most of these integrate via environment variables and take <5 minutes to connect.
---
How to Monitor Recovery
1. Bookmark the status page: [status.supabase.com](https://status.supabase.com) β refresh every 5 minutes 2. Subscribe to status updates β Supabase will email notifications when resolved 3. Test Log Explorer every 10 minutes β try a simple filter to confirm responsiveness 4. Check GitHub discussions: Supabase team often posts updates in the [#incidents channel](https://supabase.com/discord) 5. Set a reminder for 2 hours β if still degraded, escalate to Supabase support
---
Bottom Line
Your data is safe. Your APIs work. You just can't see the logs in the dashboard right now. Use the workarounds above and keep shipping. Supabase is monitoring this actively.
Expected resolution timeline: Monitoring status indicates this should resolve within 1-4 hours.
Stay calm. You've got this.