BREAKING: Supabase Log Explorer Degraded – Workarounds Available

Supabase dashboard Log Explorer experiencing degradation. Real-time logging still functional via API. Full details and immediate workarounds inside.

What's Down

Supabase is currently experiencing degraded performance in the Log Explorer dashboard feature. This impacts the visual log viewing interface within the Supabase dashboard, making it difficult or impossible to view real-time logs, queries, and system events through the UI.

Important: This appears to be a dashboard UI issue only. Underlying logging infrastructure and API access remain operational.

How to Check If You're Affected

Navigate to your Supabase project dashboard

Click on the "Logs" or "Log Explorer" tab

If the interface fails to load, loads extremely slowly, or shows incomplete/stale data, you're experiencing the degradation

Check [Supabase status page](https://status.supabase.com) for official confirmation

Immediate Workarounds

1. Use the Logs API Directly

Access logs programmatically instead of the dashboard: ```bash curl -X GET 'https://<project-ref>.supabase.co/rest/v1/logs' \ -H "Authorization: Bearer <anon-key>" \ -H "Content-Type: application/json" ```

2. Query Logs via PostgreSQL

If you have database access, query the underlying logs table directly (exact table names vary; consult your project's schema).

3. Use CLI Instead of Dashboard

```bash supabase functions list-logs <function-name> supabase db logs ``` The Supabase CLI bypasses the dashboard UI entirely.

4. Check Application Logs Independently

Don't rely solely on Supabase logging:

Integrate Sentry, LogRocket, or Datadog

Enable CloudFlare Analytics if using Workers

Use application-level logging (console, file-based, etc.)

5. Browser Troubleshooting

Clear dashboard cache: Cmd/Ctrl + Shift + Delete

Try incognito/private browsing mode

Switch browsers

Force refresh the dashboard page

Alternative Log Monitoring Solutions

While Supabase resolves this:

Papertrail – Real-time log aggregation

Logtail – Structured logging service

ELK Stack – Self-hosted logging

Grafana Loki – Lightweight log aggregation

What You Should NOT Do

Don't assume logs aren't being collected (they are)

Don't delete or modify functions due to missing UI access

Don't switch database providers yet

Next Steps

1. Monitor Status: Refresh [status.supabase.com](https://status.supabase.com) regularly 2. Use Workarounds: Switch to CLI or API-based log access immediately 3. Document Issues: If you find problems beyond the dashboard UI, report to Supabase support 4. Contact Support: File a support ticket if this impacts production operations

Unknown/Uncertain Details

I'm unable to confirm:

Exact ETA for resolution (check official status page)

Whether database logs specifically are affected (test with your project)

If regional variations exist

Impact on log retention or historical data access

Stay tuned to [@supabase](https://twitter.com/supabase) on X/Twitter for official updates.