The Logs page gives you real-time visibility into every API request hitting your project. Use it to debug issues, monitor traffic, and understand usage patterns.

Stats cards

At the top of the page, you'll see summary statistics: total requests, average response time, error rate, and requests by status code.

Request log table

Below the stats, a detailed table lists every request with:

• Timestamp
• HTTP method and path
• Status code (color-coded: green for 2xx, yellow for 4xx, red for 5xx)
• Response time in milliseconds
• Client IP and user agent

Filtering

Use the filter controls to narrow results by HTTP method, status code range, path pattern, or time window. This makes it easy to isolate specific issues — for example, show only 5xx errors on the /api/v1/db/clients endpoint.

SQL history

Logs → SQL history lists every SQL statement sent to the project through the platform: the SQL editor, the multi-statement endpoint, the MCP server and the CLI (anything using a personal access token), plus function bodies, custom RLS policies, migrations and the SQL of cron jobs (when saved or test-run). Each entry shows who sent it, whether it came from a console session or a token, the statement, and the result:

• Ran — with the row count and duration.
• Failed — the database rejected it; the error is shown. In a multi-statement request, the statements before it are listed as failed too (rolled back).
• Refused — the platform's checks stopped it before it reached the database, with the reason.
• Not run — in a multi-statement request, skipped because another statement was refused or failed.

Click an entry for the full statement (the first 8 KB are stored, with its length and SHA-256). Statements can contain your data, so SQL history is visible to project admins only and kept for 30 days. SQL your app runs through the SDK isn't listed here. When a project is deleted, its entries' statement text, error detail and IP address are removed; who sent what, when and with what result is kept until the 30 days are up.