Keeping status history
Current state: operational — “All Systems Operational” per https://status.keeping.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Keeping incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: Knowledge Base Button Missing When Replying to a Message For Some Users — 5.1 days (2025-09-26 13:57 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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-01 15:31 UTC | Intermittent connection issues | resolved | major | 6 h 17 min |
| 2026-02-27 17:36 UTC | Ticket Delivery Delayed | resolved | none | 3 h 26 min |
| 2026-02-27 07:58 UTC | Ticket Delivery Delayed | resolved | minor | 20 min |
| 2025-11-18 11:58 UTC | Cloudflare Outage | resolved | major | 3 h 35 min |
| 2025-11-10 15:54 UTC | Slow sync and website loading | resolved | major | 2 h 37 min |
| 2025-09-26 13:57 UTC | Knowledge Base Button Missing When Replying to a Message For Some Users | resolved | minor | 5 d 1 h |
| 2025-09-18 15:05 UTC | Keeping customers are having trouble signing in | resolved | minor | 54 min |
| 2025-09-12 13:40 UTC | Sending Errors when Replying to a Ticket in Gmail | resolved | minor | 1 h 59 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 Keeping with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"keeping"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}