InStride status history
Current state: operational — “All Systems Operational” per https://status.instride.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do InStride incidents last?
From 3 incidents with a vendor-posted start and resolve time. Longest on record: Degraded Performance — 25.1 h (2026-01-15 18:23 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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-01-15 18:23 UTC | Degraded Performance | resolved | minor | 25 h 03 min |
| 2025-10-20 17:36 UTC | Support Ticketing & Chat Service Disruption (External Cloud Outage) | resolved | minor | 19 h 30 min |
| 2025-08-21 18:28 UTC | Partial Outage | resolved | major | 1 h 26 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 InStride with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"instride"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}