Vendor Status Watch

← all vendors

Payoneer status history

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

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

How long do Payoneer incidents last?

81 minmedian incident duration36 measured
3.4 h90th percentile1 in 10 ran longer
81 minmedian, major/critical only35 incidents

From 36 incidents with a vendor-posted start and resolve time. Longest on record: API - General issue — 22.2 h (2025-11-05 15:27 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 (36)

StartedIncidentStatusImpactDuration
2026-08-03 13:13 UTCAPI - General issueresolvedmajor1 h 39 min
2026-06-18 11:14 UTCAPI - General issueresolvedmajor28 min
2026-06-15 12:18 UTCAPI - General issueresolvedmajor24 min
2026-06-11 13:59 UTCAPI - General issueresolvedmajor1 h 43 min
2026-04-02 17:47 UTCPayoneer general system degradationresolvedcritical2 h 01 min
2026-03-12 11:24 UTCPayoneer general system degradationresolvedcritical1 h 22 min
2026-03-03 07:01 UTCPayoneer general system degradationresolvedcritical1 h 53 min
2026-02-23 14:04 UTCPayoneer MyAccount issuesresolvedcritical3 min
2026-02-23 14:04 UTCAPI - General issueresolvedcritical2 min
2026-02-23 14:04 UTCRegistrations processing issueresolvedcritical4 min
2026-02-23 13:52 UTCMass Payout Account - General Issueresolvedcritical5 min
2026-02-23 13:52 UTCRegistrations processing issueresolvedcritical0 min
2026-02-23 13:46 UTCAPI - General issueresolvedcritical1 min
2026-02-23 13:42 UTCMass Payout Account - General Issueresolvedcritical1 min
2026-02-23 13:35 UTCAPI - General issueresolvedcritical0 min
2026-02-23 13:35 UTCPayoneer MyAccount issuesresolvedcritical19 min
2026-02-23 13:27 UTCAPI - General issueresolvedcritical1 min
2026-02-23 13:16 UTCPayoneer general system degradationresolvedcritical1 h 32 min
2026-02-23 13:09 UTCPayoneer MyAccount issuesresolvedmajor1 min
2026-02-11 08:57 UTCAPI - General issueresolvedmajor1 h 38 min
2025-12-15 08:21 UTCPayoneer MyAccount issuesresolvedmajor4 h 18 min
2025-12-13 07:16 UTCAPI - General issueresolvedmajor1 min
2025-12-13 07:16 UTCPayoneer MyAccount issuesresolvedmajor1 min
2025-12-11 14:50 UTCPayoneer MyAccount issuesresolvedmajor3 h 22 min
2025-12-09 07:28 UTCAPI - General issueresolvedmajor1 h 21 min
2025-11-19 07:14 UTCPayoneer MyAccount issuesresolvedmajor1 h 31 min
2025-11-11 11:19 UTCAPI - General issueresolvedmajor1 h 21 min
2025-11-05 15:27 UTCAPI - General issueresolvedmajor22 h 11 min
2025-10-30 13:53 UTCPayoneer general system degradationresolvedminor35 min
2025-10-08 07:59 UTCAPI - General issueresolvedmajor6 h 26 min
2025-10-08 07:57 UTCAPI - General issueresolvedmajor11 min
2025-09-28 08:42 UTCPayoneer general system degradationresolvedcritical3 h 07 min
2025-09-08 08:49 UTCPayoneer MyAccount issuesresolvedmajor2 h 52 min
2025-08-27 16:39 UTCPayoneer MyAccount issuesresolvedmajor1 h 25 min
2025-08-13 09:52 UTCAPI - General issueresolvedmajor1 h 33 min
2025-08-13 09:22 UTCPayoneer MyAccount issuesresolvedmajor2 h 03 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 Payoneer with the template

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

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