MxToolbox status history
Current state: operational — “All Systems Operational” per https://mxtoolbox.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do MxToolbox incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: MailFlow Monitoring Down / AWS Outage — 3.0 days (2025-10-20 15:18 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-02-23 20:15 UTC | Red MxError / Parse Syntax in Monitoring and Notification UI | resolved | minor | 19 h 27 min |
| 2026-02-13 16:46 UTC | MailFlow Monitoring Impacted by SpamHaus Blocklisting | resolved | minor | 4 h 49 min |
| 2025-12-10 18:26 UTC | MxToolbox Monitoring & Delivery Center Outage | resolved | major | 1 h 06 min |
| 2025-10-20 15:18 UTC | MailFlow Monitoring Down / AWS Outage | resolved | critical | 3 d 0 h |
| 2025-10-01 14:35 UTC | MailFlow Monitors Latency Issues | resolved | major | 5 h 59 min |
| 2025-09-11 16:17 UTC | MxToolbox Outage 20250911 | resolved | major | 4 h 42 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch MxToolbox with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"mxtoolbox"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
