Topaz Labs outage history

We hold 18 Topaz Labs incidents from Topaz Labs's status page, the newest from Oct 8, 2026. 18 of the 18 listed carry Topaz Labs'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 10h 35m since the last recorded problem.
Operational · 24h
99.65%
0 incidents · ≈5m degraded
288 checks
Operational · 7d
99.35%
0 incidents · ≈1h 5m degraded
2015 checks
Operational · 30d
99.25%
0 incidents · ≈5h 25m degraded
8638 checks
Operational · since Jun 22, 2026
98.78%
7 incidents · ≈2h 5m down · ≈1d 13h degraded
41551 checks

% of our checks that found Topaz Labs 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 Topaz Labs fails

Since Jun 28, 2026, Topaz Labs's status page has marked 12 Topaz Labs components as impaired, across 467 of our five-minute readings. Image API accounts for the most: 233 readings (about 19 hours) on 22 days, most recently on Oct 20, 2026. Next is System Requirements Checker (Windows), with 51 readings on 6 days. We hold 18 Topaz Labs incidents from Topaz Labs's status page, the earliest from Feb 5, 2026. Of the 15 that Topaz Labs closed with an end time, the median lasted 1 h 4 min.

ComponentOutageDegradedMaint.DaysLast
Image API—233—22Oct 20, 2026
System Requirements Checker (Windows)51——6Oct 29, 2026
System Requirements Checker (macOS)48——5Nov 17, 2026
Community32—3213Nov 13, 2026
Store30——8Nov 18, 2026
Video API227—4Oct 10, 2026
Web Apps16——5Oct 8, 2026
Authorization and Billing Services65—1Sep 1, 2026

Incidents by month: Apr 2026: 1 · May 2026: 2 · Jun 2026: 2 · Jul 2026: 3 · Sep 2026: 2 · Oct 2026: 2

Counts are five-minute readings of Topaz Labs'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

October 2026 · 2

September 2026 · 2

July 2026 · 3

June 2026 · 2

May 2026 · 2

April 2026 · 1

March 2026 · 2

February 2026 · 4

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