Vendor Status Watch

← all vendors

Axway status history

Current state: operational — “All Systems Operational” per https://status.axway.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

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

How long do Axway incidents last?

0 minmedian incident duration5 measured
60 min90th percentile1 in 10 ran longer
12 minmedian, major/critical only2 incidents

From 5 incidents with a vendor-posted start and resolve time. Longest on record: Axway Platform Intermittent Login Issues — 60 min (2026-08-11 05:50 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 (5)

StartedIncidentStatusImpactDuration
2026-08-18 19:40 UTCAxway Login Issuesresolvedcritical24 min
2026-08-11 05:50 UTCAxway Platform Intermittent Login Issuesresolvedminor1 h 00 min
2026-05-11 14:00 UTCAxway Platform Analytics intermittent query failureresolvedminor0 min
2026-02-19 13:00 UTCAxway Platform Outageresolvedmajor0 min
2025-12-09 06:30 UTCAmplify Studio outage - US & EUresolvednone0 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 Axway with the template

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

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