Colossyan Outage History

12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Colossyan status99.96% uptime history

Every Recorded Colossyan Incident

Colossyan incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 30, 2026Neo 2 inference is degraded132h 31mResolved
Oct 26, 2026Stock media-related operations are degraded224h 51mResolved
Oct 1, 2026NEO 2 rendering is degraded820h 29mResolved
Sep 30, 2026Agentic features are degrated854h 18mResolved
Aug 14, 2026Text-to-speech generation is degraded1880h 9mResolved
Aug 14, 2026Text-to-speech generation is degraded.1887h 1mResolved
Aug 12, 2026Neo 1 video generation is degraded1929h 44mResolved
Jul 29, 2026Neo 2 video generation is degraded1520h 52mResolved
Jul 23, 2026Voice cloning is degraded1668h 51mResolved
Jul 9, 2026Video generation is degraded2008h 34mResolved
Jun 25, 2026Video generation is degraded1614h 1mResolved
Jun 15, 2026Video generation is degraded1864h 55mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Colossyan incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Colossyan Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Colossyan acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Colossyan outage in this window ran 83d 16h, against a mean recovery of 56d 23h. If you depend on Colossyan in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.