Vendor Status Watch

← all vendors

Magensa status history

Current state: operational — “All Systems Operational” per http://magensa.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
2incidents, last 90 days
12incidents on record
Incidents per week, last 12 weeks:

How long do Magensa incidents last?

77 minmedian incident duration12 measured
6.9 days90th percentile1 in 10 ran longer
3.7 hmedian, major/critical only1 incident

From 12 incidents with a vendor-posted start and resolve time. Longest on record: Magensa service degradation — 30.3 days (2026-04-05 19:00 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 (12)

StartedIncidentStatusImpactDuration
2026-08-19 16:48 UTCNon-Magensa - Worldpay incident.resolvednone53 min
2026-07-23 15:15 UTCService interruptionpostmortemmajor3 h 40 min
2026-05-20 07:30 UTCNon-Magensa Incident: WorldPay, element Express, slow response times.resolvednone0 min
2026-04-05 19:00 UTCMagensa service degradationresolvednone30 d 7 h
2026-04-01 18:08 UTCMagensa Unigate Service Down.resolvednone1 h 40 min
2026-03-25 16:26 UTCMagensa Decryption, Intermittent errors reported.resolvedminor26 h 17 min
2025-11-10 16:10 UTCNon-Magensa transaction errors during processing to HeartlandPortico endpoint impacting MPPGv3/v4 and DAFv3/v4resolvedminor54 min
2025-10-27 21:07 UTCMagensa Azure DC intermittent connection failuresresolvednone20 h 15 min
2025-10-15 19:21 UTCMagensa Services Unavailableresolvednone2 min
2025-09-17 17:44 UTCCustomer Reported Connectivity Issues - researching.resolvednone6 d 21 h
2025-09-17 01:30 UTCIntermittent Processing Errorsresolvednone0 min
2025-08-12 23:58 UTCTSYS Processing errors (721)resolvednone23 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 Magensa with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "magensa"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}