Rasket status
Some systems are degraded
Checked at . This page runs our readiness checks again every 30 seconds, and reads what our alerting, which watches Rasket every five minutes, last found.
- Operational
Website and dashboard
This page was served by the same deployment that serves the dashboard and the API.
- Degraded
Database
Your teams, email records, contacts and settings.
- Operational
File storage
Attachments, raw messages and data exports.
- Degraded
Encryption
The keys that protect webhook signing secrets, DKIM keys and other stored secrets.
- Not monitored
API
Requests to the REST API: error rate and response time.
- Not monitored
Sending and delivery
Accepting sends, the send queue, and hand-off to recipients’ mail servers.
- Not monitored
Receiving email and Rasket Inbox
Inbound mail arriving, being parsed and reaching your inbox or webhook.
- Not monitored
SMTP relay
smtp.rasket.com on ports 465 and 587, probed the way your mailer connects.
- Not monitored
Webhook delivery
Delivering events to your endpoints on time.
- Not monitored
Background jobs
Scheduled sends, campaigns and automations.
What “Not monitored” means
A row says Not monitored when our alerting has not reported on it in the last fifteen minutes, or has no check for it yet. It is not a promise that the component is working or that it is not; it means this page has nothing current to tell you about it.
If something is wrong
This page is served by Rasket itself, so if it does not load at all, Rasket is down. If something is not working that this page shows as operational, use the help panel in the dashboard or write to support@rasket.com. The same checks are available to a monitor as JSON at /api/healthz and /api/readyz. What changed and when is in the changelog.