Jostle AP status history
Current state: operational — “All Systems Operational” per https://jostleap.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Jostle AP incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Jostle issue — 22.0 days (2025-11-19 20:15 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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-21 21:11 UTC | Jostle's platform is currently unavailable | resolved | critical | 6 min |
| 2025-11-19 20:15 UTC | Jostle issue | resolved | minor | 21 d 23 h |
| 2025-11-05 17:53 UTC | Jostle's platform is currently unavailable | resolved | critical | 1 min |
| 2025-10-20 16:07 UTC | Jostle issue | resolved | minor | 7 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 Jostle AP with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"jostle-ap"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}