Vendor Status Watch

← all vendors

TestRail status history

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

1incidents, last 30 days
3incidents, last 90 days
4incidents on record
Incidents per week, last 12 weeks:
Get TestRail alerts in your Slack — free templateRSS for TestRail

How long do TestRail incidents last?

36.0 hmedian incident duration4 measured
3.8 days90th percentile1 in 10 ran longer
2.5 hmedian, major/critical only1 incident

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Jira Integration Degradation — 3.8 days (2026-03-20 02: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 (4)

StartedIncidentStatusImpactDuration
2026-08-19 11:32 UTCPerformance issue impacting access to TestRailresolvedmajor2 h 27 min
2026-08-17 12:00 UTCResolved: DNS Issue Affecting Access to TestRailresolvedminor0 min
2026-08-11 18:03 UTCPerformance Degradation Affecting a Subset of Cloud Instancesresolvedminor2 d 21 h
2026-03-20 02:00 UTCJira Integration Degradationresolvedminor3 d 20 h

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 TestRail with the template

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

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