Rasket status
All checked systems are operational
Checked at . Our checks run every five minutes, and each row reflects the last fifteen. A row shows as degraded only when at least 35% of it is failing, so a single failed check is not reported as a problem.
- Operational
Website and dashboard
This page was served by the same deployment that serves the dashboard and the API.
- Operational
Database
Your teams, email records, contacts and settings.
- Operational
File storage
Attachments, raw messages and data exports.
- Operational
Encryption
The keys that protect webhook signing secrets, DKIM keys and other stored secrets.
- Operational
API
Requests to the REST API.
- Operational
Sending and delivery
Accepting sends, the send queue, and hand-off to recipients’ mail servers.
- Operational
Receiving email and Rasket Inbox
Inbound mail arriving and being parsed for your inbox or webhook.
- Operational
SMTP relay
smtp.rasket.com on ports 465 and 587, probed the way your mailer connects.
- Operational
Webhook delivery
Delivering events to your endpoints on time.
- Operational
Background jobs
Scheduled sends, campaigns and automations.
What “Not monitored” means
A row says Not monitored when we do not have three of our five-minute checks for it from the last twenty 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. Not checked means the results could not be read at all just now.
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.