Service disruption
Last checked 33 seconds ago.
- Components operational
- 1/6
- Uptime · 90 days
- 19.25%
- Ongoing incidents
- 0
Components
Website99 ms average
Sem respostaDown90 days ago3.87% uptime
Response time28–206 ms
Login133 ms average
Sem respostaDown90 days ago3.87% uptime
Response time28–302 ms
Customer area193 ms average
Sem respostaDown90 days ago3.87% uptime
Response time41–437 ms
Backoffice266 ms average
Sem respostaDown90 days ago3.87% uptime
Response time72–578 ms
Database214 ms average
Operational90 days ago100.00% uptime
Response time61–464 ms
Emailthird-party service312 ms average
IndisponívelDown90 days ago0.00% uptime
Response time156–570 ms
Get email alerts
We'll email you when we open an incident and when it is resolved. Nothing else — no newsletters, no product news.
Background jobs
- ads-synclast success 33 seconds ago
- analytics-retentionlast success 33 seconds ago
- finance-issuelast success 33 seconds ago
- newsletter-sendlast success 33 seconds ago
- notify-scanlast success 33 seconds ago
- outreach-sendlast success 33 seconds ago
- phone-verifications-purgelast success 33 seconds ago
- report-weeklylast success 33 seconds ago
- social-publishlast success 33 seconds ago
- status-notifylast success 33 seconds ago
- status-probelast success 33 seconds ago
- subscription-expirelast success 33 seconds ago
- visitors-purgelast success 33 seconds ago
- webhook-deliverlast success 33 seconds ago
- whatsapp-sendlast success 33 seconds ago
- whatsapp-window-sweeplast success 33 seconds ago
These checks run on our own servers: they measure component health from the inside, not whether the service is reachable from your network. If the server becomes unreachable this page stops updating — always check the last-checked time above.