Vasion Outage History

Vasion is up right now

Vasion had 7 outages in the last 2 years totaling 557h 46m of downtime — averaging 0.3 incidents per month.

There were 7 Vasion outages since June 25, 2025 totaling 557h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.vasion.com

Major February 10, 2026

Ricoh CPA Disruption for new installs/reinstalls

Detected by Pingoru
Feb 10, 2026, 05:42 AM UTC
Resolved
Feb 12, 2026, 08:40 PM UTC
Duration
2d 14h
Affected: Control Panel Application (CPA)Control Panel Application (CPA)Control Panel Application (CPA)Control Panel Application (CPA)Control Panel Application (CPA)Control Panel Application (CPA)Control Panel Application (CPA)
Timeline · 7 updates

Read the full incident report →

Minor October 13, 2025

Intermittent timeouts with accessing instance

Detected by Pingoru
Oct 13, 2025, 06:11 PM UTC
Resolved
Oct 13, 2025, 06:53 PM UTC
Duration
42m
Affected: SRS Platform (Maintenance) - North Europe Region
Timeline · 3 updates
  1. investigating Oct 13, 2025, 06:11 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 13, 2025, 06:53 PM UTC

    This incident has been resolved.

  3. postmortem Oct 14, 2025, 02:50 PM UTC

    Monday, October 13th, 2025 ‌ **Intermittent Timeout Issues When Accessing Instance** ‌ **Issue Summary:** On 13 October 2025, between 5:13 PM UTC and 6:38 PM UTC, some users with instances hosted in printercloud6 experienced intermittent timeout or connection failure issues when accessing the platform. ‌ **Root Cause:** Multiple compute nodes became unresponsive, resulting in intermittent issues accessing other resources. ‌ **Resolution:** The affected compute nodes were identified and replaced. ‌ **Mitigation:** To address this issue going forward, additional monitors have been added. Our engineering teams’ investigation is still ongoing. Once further information is identified regarding what caused the nodes to become unresponsive, measures will be implemented to prevent this issue from occurring on compute nodes going forward. ‌ **Conclusion:** We acknowledge that this had an impact on some customers. We thank you for your patience as we resolved this service disruption.

Read the full incident report →