Kinescope Outage History

10 incidents recorded over the last 365 days, 10 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 Kinescope status99.97% uptime history

Every Recorded Kinescope Incident

Kinescope incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 25, 2026API Down32 minResolved
Sep 25, 2026Player down32 minResolved
Sep 25, 2026Global segment 56 minResolved
Sep 25, 2026DNS down4 minResolved
Sep 24, 2026Dashboard down5 minResolved
Sep 24, 2026Site down6 minResolved
Sep 24, 2026Player down8 minResolved
Sep 24, 2026Dashboard down9 minResolved
Sep 24, 2026API Down14 minResolved
Sep 24, 2026DNS down15 minResolved

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 Kinescope 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 Kinescope 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 Kinescope 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 Kinescope outage in this window ran 56 min, against a mean recovery of 18 min. If you depend on Kinescope 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.