Decagon outage history

We hold 29 Decagon incidents from Decagon's status page, the newest from Dec 3, 2026. 24 of the 29 listed carry Decagon's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 2d 12h since the last recorded problem.
Operational · 24h
100%
1 incident · no downtime
288 checks
Operational · 7d
99.40%
2 incidents · ≈1h 0m degraded
2015 checks
Operational · 30d
99.65%
4 incidents · ≈2h 30m degraded
8638 checks
Operational · since Jun 22, 2026
98.44%
24 incidents · ≈2d 5h degraded
41199 checks

% of our checks that found Decagon fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Decagon fails

Since Jul 10, 2026, Decagon's status page has marked 6 Decagon components as impaired, across 1,527 of our five-minute readings. [US] Decagon Admin Portal accounts for the most: 400 readings (about 33 hours) on 14 days, 2 of them marked as an outage rather than degraded, most recently on Oct 8, 2026. Next is [US] Voice Channel, with 354 readings on 10 days. We hold 29 Decagon incidents from Decagon's status page, the earliest from Apr 15, 2026. Of the 23 that Decagon closed with an end time, the median lasted 1 h 7 min.

ComponentOutageDegradedMaint.DaysLast
[US] Decagon Admin Portal2398314Oct 8, 2026
[US] Voice Channel6348310Nov 16, 2026
[US] Chat, Email, and SMS Channels—33338Nov 16, 2026
[EU] Decagon Admin Portal2154—9Sep 18, 2026
[EU] Voice Channel6149—3Nov 11, 2026
[EU] Chat, Email, and SMS Channels—129—1Aug 31, 2026

Incidents by month: May 2026: 1 · Aug 2026: 12 · Sep 2026: 7 · Oct 2026: 1 · Nov 2026: 3 · Dec 2026: 1

Counts are five-minute readings of Decagon's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

December 2026 · 1

November 2026 · 3

October 2026 · 1

September 2026 · 7

August 2026 · 12

May 2026 · 1

April 2026 · 4

Incidents and their updates are Decagon's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Decagon.