Paak publishes a public status dashboard at status.paak.club. Real-time service health, no login required.
What the dashboard shows
For clarity, the public page shows only two services:
- The Paak app —
app.paak.club. Green = sign in, manage, register members, collect payments. Red = the management side is down. - Paak.club site —
paak.club. Pricing, help center, blog. Independent of the app.
Several additional internal probes (API, database, staging, Emmara.fr) run behind the scenes for diagnostic purposes but stay off the public page.
How to read the status
- Green — last probe returned HTTP 200.
- Amber (Degraded) — slow or intermittent response.
- Red (Down) — failed 2+ consecutive probes. Incident auto-opened.
Get notified. Click "Subscribe to updates" on the status page to receive an email when an incident opens. No account required.
Our stance on incidents
Paak does not offer a contractual SLA today — the goal is transparency, not empty promises.
- Outages detected by probes open an incident automatically within a minute.
- The team gets an immediate notification (email + push), day or night.
- The incident page is updated as the situation evolves.
- Resolved incidents stay visible in the history (90 days).
- Financial-impact incidents get a direct post-mortem to affected club admins.
Backups
An outage is not data loss. PostgreSQL (OVHcloud, Roubaix) is backed up continuously: hourly + daily snapshots retained 14 days, plus a daily encrypted export to OVHcloud S3 (Strasbourg) retained 30 days.
FAQ
Why does "Degraded" show while the app seems to work?
Response time is above the threshold. The app still works, just slower.
Status is green but I can't log in?
Check your Internet. If your network is fine and Paak is green, the issue is local to your browser — try incognito or clear the cache for app.paak.club.
How long do incidents stay visible?
90 days. Older history on request.
Last updated: May 13, 2026 ID :
help.compliance.platform-status