Status
Every component is operational
This page is a file, not a monitor. Each state below was written when this site was built, and the build you are reading is the deployment that serves it.
OperationalBuilt UTC
- Operational
REST API
Every call under /v1 and /v0: inboxes, threads, messages, keys, domains, webhooks.
- Operational
Inbound mail
The SMTP edge that accepts mail for your inboxes, with DKIM, DMARC and the screener.
- Operational
Outbound delivery
Sending, replying, forwarding and the retries of a message that was deferred.
- Operational
Webhooks
Signed events, the attempt history of each one and the replay.
- Operational
Console
The screens behind /console: mail, tickets, rules, keys, team.
- Operational
MCP server
The same operations as tools, at /mcp, for a coding agent.
A static page cannot see an outage that happens after it was written, and it does not pretend to. For a live answer ask the API: https://api.mueslimail.com/healthz answers with no body while the process is up, and https://api.mueslimail.com/readyz answers 503 while the database is unreachable.
When a component is degraded or in maintenance for a build, the row above says so and the note says what is affected. Nothing here is fetched in the browser: the page carries no script for it and calls no third party.
Something looks wrong that this page does not show? Write to the FAQ first, then to support from the console. Mueslimail is in staging: no uptime commitment yet.