Is Postmark down?
Right now
No. Postmark is operational.
No incidents reported.
Read from status.postmarkapp.com · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/postmark/status.agent.json
MCP: upstream_status {"service":"postmark"}
Transactional email sending, inbound and webhooks.
What Postmark reports
Operational
Taken as is from Postmark's own status page API. Incident titles and component names below are theirs.
Open status.postmarkapp.comUpButler's independent probe
API edge is answeringHTTP 401 · 343 ms
One request without credentials to api.postmarkapp.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Postmark components
19 operational
- APIOperational
- SMTPOperational
- InboundOperational
- WebhooksOperational
- Web AppOperational
- AnalyticsOperational
API
- GeneralOperational
- SendingOperational
- ReceivingOperational
- SandboxOperational
SMTP
- GeneralOperational
- SendingOperational
- ReceivingOperational
Web App
- GeneralOperational
- LoginOperational
- Billing & SubscriptionsOperational
Analytics
- GeneralOperational
- StatisticsOperational
- Link TrackingOperational
Postmark incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Delayed Inbound Message Processing | minor | 2 h 6 min | |
| Delayed Message Delivery | minor | 3 h 59 min |
Tell your outage from Postmark's
Declare that your project depends on Postmark. When one of your monitors fails while Postmark has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- postmarkcurl -s https://upbutler.com/status/postmark/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "postmark",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Postmark down right now?
- No. As of 2026-10-10 05:09 UTC, Postmark is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Postmark's own status page API at https://status.postmarkapp.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Postmark's words.
- What does UpButler's own Postmark check prove?
- Every two minutes UpButler sends one request without credentials to the Postmark API edge (api.postmarkapp.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Postmark reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Postmark status?
- Fetch https://upbutler.com/status/postmark/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"postmark"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Postmark's?
- Add "postmark" to the dependencies of your UpButler workspace. When one of your monitors fails while Postmark has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in email
UpButler is not affiliated with Postmark. Status and incident text belong to Postmark and are read from their public status source; the probe result is UpButler's own measurement.