Skip to main content
Updated October 11, 2026 Raff checks every database all the time: the engine itself, the path your apps use to reach it, its storage and its connections. The status in the dashboard says what it found, in plain words.

​
How it works

​
Statuses

​
Checks

  • Engine: whether it is ready, every few seconds.
  • Connection path: every minute, Raff connects through each database’s public address the way your apps do, without logging in.
  • Storage and connections: every minute, faster when storage passes 50%.

​
Emails

Sent to the project’s members:
  • Down: after 2 minutes without answering, and back up when it answers again, with how long it was down.
  • Storage: at 80% and 90% of the plan’s storage, at most once a day each; when PostgreSQL or MySQL become read-only at 95%, and when writes work again.
  • Free databases: before a free database pauses for idleness, when it pauses, and reminders while it stays paused.

​
When to use it

  • Watch the Monitoring tab for trends; rely on the emails for incidents.
  • A Degraded or Down database shows the cause on its Overview tab.

​
Trade-offs

  • A short restart during a resize is expected and does not count as down.
  • Statuses refresh every few seconds in the dashboard; the API returns the same values.

Monitor a database

Charts, slow queries and logs.

Troubleshooting

What to do for each problem.
Last modified on October 11, 2026