Vizcom Outage History

29 incidents recorded over the last 365 days, 29 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 Vizcom status100.00% uptime history

Every Recorded Vizcom Incident

Vizcom incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 28, 2026Elevated Generation Latency and Error RatesThis incident has been resolved.1h 59mResolved
Oct 27, 2026Animate IssuesThis incident has been resolved.1h 14mResolved
Jun 5, 2026Degraded performance: Instant RenderThis incident has been resolved.3h 40mResolved
Jun 3, 2026Some AI features may be slower or temporarily unavailableThis incident has been resolved.9 minResolved
May 12, 2026Database performance degradationThe issue has been resolved. We are monitoring closely3h 51mResolved
May 12, 2026Partial site unavailabilityThe issue has been resolved. We are monitoring closely44 minResolved
May 12, 2026Intermittent user site unavailabiltyThe issue has been resolved.1h 20mResolved
May 11, 2026Some users may be experiencing slow loading timesThe incident is resolved.3h 10mResolved
May 11, 2026Some users may be experiencing slow loading timesThe incident has been resolved.1h 40mResolved
May 5, 2026[TEST] Connectivity Test - No Action RequiredThis incident has been resolved.13 minResolved
Apr 30, 2026Some users may be experiencing issues with ModifyThis incident has been resolved.22 minResolved
Apr 28, 2026Some users may be experiencing issues with image generationThis incident has been resolved.37 minResolved
Apr 27, 2026Extract Colors failing on some imagesAn issue affecting a small subset of users was identified and will be resolved in today’s release.2h 2mResolved
Apr 23, 20263d generation outageThis incident has been resolved.42 minResolved
Apr 8, 2026Vizcom App OutageThis incident has been resolved.1h 11mResolved
Apr 8, 2026Some users may be experiencing issues with Modify and AnimateThis incident has been resolved.4h 22mResolved
Mar 24, 2026Partial Service OutageThis incident has been resolved.52 minResolved
Mar 21, 2026Intermittent ErrorsThis incident has been resolved.30 minResolved
Mar 19, 2026Partial Service Outage - RecurrenceThis incident has been resolved. The issue was traced to a recent deployment that introduced a memory leak. The change has been reverted and service has been restored. We are continuing to monitor.1h 40mResolved
Mar 19, 2026Partial Service OutageThe incident has been resolved. Our team continues to monitor the situation to ensure stability.1h 23mResolved
Mar 12, 2026Intermittent errors with ModifyThis incident has been resolved.5h 7mResolved
Mar 10, 2026Vizcom App OutageWe identified an issue introduced during a recent deployment that caused Vizcom to become unavailable. The deployment has been rolled back and service has been restored.-116 minResolved
Feb 25, 2026Some users may be experiencing issues with Modify ProThis incident has been resolved.6h 26mResolved
Feb 24, 2026App OutageEarlier today, the Vizcom app experienced a period of unavailability. The issue has been resolved and service is operating normally. We are taking steps to prevent this from recurring and will continue monitoring.0 minResolved
Feb 19, 2026Some users may be experiencing issues with ModifyService appears to be operating normally and key metrics have returned to baseline. We will continue monitoring5h 1mResolved
Jan 28, 2026Increased latency on ModifyThis incident has been resolved.3h 14mResolved
Jan 26, 2026Some users may be unable to access the appThis incident has been resolved.5 minResolved
Dec 19, 2025Service OutageThis incident has been resolved.25 minResolved
Dec 18, 2025Some users may be experiencing elevated latency when generating images.This incident has been resolved.29 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 Vizcom 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 Vizcom 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 Vizcom 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 Vizcom outage in this window ran 6h 26m, against a mean recovery of 1h 52m. If you depend on Vizcom 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.