Vendor Status Watch

← all vendors

PairSoft status history

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

0incidents, last 30 days
0incidents, last 90 days
3incidents on record

How long do PairSoft incidents last?

5.3 hmedian incident duration3 measured
20.2 h90th percentile1 in 10 ran longer
5.3 hmedian, major/critical only1 incident

From 3 incidents with a vendor-posted start and resolve time. Longest on record: PaperSaveCloud Service Interruption Alert — 20.2 h (2025-10-29 16: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 (3)

StartedIncidentStatusImpactDuration
2025-11-17 15:46 UTCDocupeak Service Interruption Alertresolvedmajor5 h 17 min
2025-10-29 16:50 UTCPaperSaveCloud Service Interruption Alertresolvednone20 h 12 min
2025-09-29 16:04 UTCDocupeak Cloud Service - Interruption Alertresolvedminor51 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 PairSoft with the template

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

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