INKY status history
Current state: operational — “All Systems Operational” per https://status.inkyphishfence.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do INKY incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: Mail processing delays in US. — 2.8 days (2025-12-05 17:27 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-08-12 01:29 UTC | Inky Dashboard partial outage | resolved | major | 56 min |
| 2026-04-08 16:03 UTC | INKY - Google Workspace partners - Emails fail to send or receive | postmortem | major | 6 h 59 min |
| 2026-03-31 11:17 UTC | Outbound mail delays in EU region | postmortem | minor | 1 h 49 min |
| 2026-01-22 20:49 UTC | Widespread Microsoft 365 Issue Potentially Impacting Email | resolved | minor | 16 h 15 min |
| 2025-12-23 14:14 UTC | Outbound Mail Delays | resolved | none | 7 h 09 min |
| 2025-12-05 17:27 UTC | Mail processing delays in US. | resolved | none | 2 d 20 h |
| 2025-10-21 13:36 UTC | Dashboard may be slow and show dated information | resolved | minor | 1 h 21 min |
| 2025-08-12 15:02 UTC | Seeing some delay with delivery tied to some O365 Email | resolved | minor | 47 h 44 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 INKY with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"inky"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}