Visualsoft incident

Outage

Critical Resolved View vendor source →

Visualsoft experienced a critical incident on July 30, 2026 affecting Admin and Seasonly and 1 more component, lasting 19h 9m. The incident has been resolved; the full update timeline is below.

Started
Jul 30, 2026, 07:14 PM UTC
Resolved
Jul 31, 2026, 02:23 PM UTC
Duration
19h 9m
Detected by Pingoru
Jul 30, 2026, 07:14 PM UTC

Affected components

AdminSeasonlyStorefrontsWyshQuiQR CodesCookeaseSmart Alt

Update timeline

  1. identified Jul 30, 2026, 07:14 PM UTC

    We are aware of an issue impacting our VSCommerce websites & Shopify Apps. Our DevOps team have discovered the problem and are currently at ways to mitigate this. We will supply further updates as soon as we have them.

  2. identified Jul 30, 2026, 10:10 PM UTC

    We are pleased to announce that users of our Shopify Apps are now able to access them with no issues. We are still experiencing intermittent access issues for some of our VSCommerce websites. Our Service Desk & Client Success teams will be available from 8am in the morning to assist clients via phone, email or support tickets.

  3. identified Jul 31, 2026, 08:01 AM UTC

    We are continuing to address an incident that affected access to our visualsoft.co.uk domain via our domain registrar. If you require assistance, please call us, open a support ticket, or email the support team directly.

  4. identified Jul 31, 2026, 09:33 AM UTC

    We are continuing to address an incident that affected access to our visualsoft.co.uk domain via our domain registrar. Please call us or raise a support ticket if you need any guidance.

  5. monitoring Jul 31, 2026, 12:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Jul 31, 2026, 02:23 PM UTC

    We are pleased to inform you that the issue with our domain registrar has now been resolved by them. This means all functionality is now restored. We will be in touch next week with more details on this, and once more - thank you for your patience whilst this issue occurred.