// status
mxproxy status
Is forwarding working right now, how fast is it, and what went wrong recently. Real numbers from our own checks, updated every minute.
All systems operational
Services
-
Operational
Receiving and forwarding
MX on port 25 (mx.mxproxy.dev) and the forwarding queue
90 days ago 30 days ago 100% uptime Today -
Operational
Authenticated sending
SMTP on port 587, for replying as your domain
90 days ago 30 days ago 100% uptime Today -
Operational
Dashboard and API
app.mxproxy.dev
90 days ago 30 days ago 100% uptime Today -
Operational
MTA-STS policy
The TLS policy senders fetch for our MX
90 days ago 30 days ago 100% uptime Today
Forwarding time
From the moment we accept a message to the moment the destination mailbox server accepts it. Retries (a destination that asked us to try later) are included.
Last 24 hours
Not enough deliveries yet for a meaningful number
Last 7 days
Not enough deliveries yet for a meaningful number
Incidents
No incidents in the last 90 days.
How we measure
- Every minute we connect to our MX (port 25) and to the sending server (587), wait for the SMTP greeting and check that STARTTLS is offered; we load the dashboard's health check and our MTA-STS policy. A slow answer (over 5 s) or a missing STARTTLS counts as degraded; two failed checks in a row, as an outage.
- Receiving also shows as degraded when the forwarding queue is stuck: mail is accepted but has waited more than 15 minutes to leave.
- Uptime counts degraded checks as up. A day is green at 99.9% or more, yellow down to 99%, red below; gray means we have no checks for it. Incidents color the days they span.
- The checks run on our own server, so they see DNS, the ports, TLS and the software, but not the internet between you and us. Problems we learn about another way are posted as incidents.
- Forwarding times and volume come from the delivery queue and usage counters, aggregated across all customers. No address, domain or message is ever shown here.
Machine-readable: /status.json