Meridian status history
Current state: operational — “All Systems Operational” per http://status.meridiankiosks.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Meridian incidents last?
From 7 incidents with a vendor-posted start and resolve time. Longest on record: Blank screen on some kiosks — 45.6 h (2026-09-09 16:19 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 (7)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-09 16:19 UTC | Blank screen on some kiosks | resolved | none | 45 h 34 min |
| 2026-06-02 23:43 UTC | Reporting endpoint maintenance | resolved | none | 1 h 21 min |
| 2026-03-20 15:39 UTC | Investigating Connectivity Issue | resolved | none | 8 min |
| 2025-12-11 19:00 UTC | Data Processing Delays - Reporting Tools Affected | resolved | none | 0 min |
| 2025-10-20 11:13 UTC | SMS Outage | resolved | major | 8 h 52 min |
| 2025-10-09 19:01 UTC | Payment Processing - Potential Service Interruption | resolved | major | 17 h 57 min |
| 2025-09-08 08:30 UTC | Chase Payment Processing incident (Resolved) | resolved | none | 0 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 Meridian with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"meridian"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
