Vendor Status Watch

← all vendors

Ortto status history

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

0incidents, last 30 days
0incidents, last 90 days
8incidents on record
Get Ortto alerts in your Slack — free templateRSS for Ortto

How long do Ortto incidents last?

11.1 hmedian incident duration8 measured
20.7 h90th percentile1 in 10 ran longer
3.4 hmedian, major/critical only2 incidents

From 8 incidents with a vendor-posted start and resolve time. Longest on record: Autopilot Journeys component delay trigger and action shapes experiencing degraded performance — 24.6 h (2025-09-10 22:14 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 (8)

StartedIncidentStatusImpactDuration
2026-04-09 05:23 UTCService Disruptionresolvedminor20 h 40 min
2026-03-19 01:00 UTCKnowledge Base Feature Outage (help.ortto.com)resolvedminor1 h 43 min
2026-01-27 17:55 UTCAutopilot Journeys Web Application loading and email editor issuesresolvedminor6 h 40 min
2026-01-26 16:22 UTCIntermittent loading issues on Autopilot Journey subcomponentresolvedminor17 h 23 min
2026-01-23 21:40 UTC[Autopilot Journeys] - Smart Segment Degradationresolvedminor15 h 28 min
2025-12-01 23:19 UTCPartial Outage of Ortto Web Interface and APIresolvedmajor3 h 56 min
2025-09-10 22:14 UTCAutopilot Journeys component delay trigger and action shapes experiencing degraded performanceresolvedminor24 h 39 min
2025-09-08 06:31 UTCLogin / Authentication issuesresolvedmajor2 h 54 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 Ortto with the template

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

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