VisBook Outage History

VisBook is up right now

VisBook had 10 outages in the last 2 years totaling 368h 11m of downtime — averaging 0.4 incidents per month.

There were 10 VisBook outages since October 3, 2025 totaling 368h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.visbook.com

Minor September 7, 2026

Report data sync issue

Detected by Pingoru
Sep 07, 2026, 07:47 AM UTC
Resolved
Sep 07, 2026, 08:15 AM UTC
Duration
28m
Affected: Visbook Engine
Timeline · 3 updates
  1. identified Sep 07, 2026, 07:47 AM UTC

    We’re currently investigating a data-sync issue affecting some reports. Certain reports may be incomplete or slightly out of date right now. Your bookings and core services are unaffected. We’re working on it and will update once everything is back to normal.

  2. monitoring Sep 07, 2026, 08:02 AM UTC

    Report data-sync issue has been fixed. Reports are accurate and up to date again. Core services were unaffected throughout.

  3. resolved Sep 07, 2026, 08:15 AM UTC

    The incident has been resolved.

Read the full incident report →

Minor August 27, 2026

Investigating ongoing issue

Detected by Pingoru
Aug 27, 2026, 08:39 AM UTC
Resolved
Sep 07, 2026, 07:46 AM UTC
Duration
10d 23h
Affected: Visbook Engine
Timeline · 3 updates
  1. investigating Aug 27, 2026, 08:39 AM UTC

    We are aware of a potential issue and are currently investigating. We will provide updates as we learn more.

  2. monitoring Aug 27, 2026, 08:48 AM UTC

    Service has returned to normal, but we are monitoring to ensure continued stability.

  3. resolved Sep 07, 2026, 07:46 AM UTC

    The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.

Read the full incident report →

Minor June 23, 2026

Monitoring

Detected by Pingoru
Jun 23, 2026, 05:52 PM UTC
Resolved
Jun 24, 2026, 11:53 AM UTC
Duration
18h
Affected: Visbook Engine
Timeline · 2 updates
  1. identified Jun 23, 2026, 05:52 PM UTC

    We experienced database-related issues. The cause has been identified, and mitigation measures have been implemented. Affected users can restart the application to clear the issue. We are continuing to monitor the situation closely.

  2. resolved Jun 24, 2026, 11:53 AM UTC

    Resolved

Read the full incident report →

Minor June 20, 2026

General instability – investigating

Detected by Pingoru
Jun 20, 2026, 11:54 AM UTC
Resolved
Jun 20, 2026, 03:23 PM UTC
Duration
3h 29m
Affected: Visbook Engine
Timeline · 3 updates
  1. investigating Jun 20, 2026, 11:54 AM UTC

    We are currently experiencing general instability across our systems, including login errors affecting some users. The root cause has not yet been identified. Our technical team is actively investigating and working to restore full service as quickly as possible. We apologise for the inconvenience and will provide an update as soon as more information is available.

  2. monitoring Jun 20, 2026, 12:59 PM UTC

    Further investigation has shown that the instability affected only a subset of users. We have applied some changes that appear to have improved the situation. However, we have not yet been able to confirm the underlying root cause. We are actively monitoring the systems and will provide a further update if anything changes or once we can confirm the issue is fully resolved. Thank you for your patience.

  3. resolved Jun 20, 2026, 03:23 PM UTC

    The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.

Read the full incident report →

Minor May 22, 2026

Slow departure list after recent update – fix incoming

Detected by Pingoru
May 22, 2026, 07:01 AM UTC
Resolved
May 22, 2026, 07:41 AM UTC
Duration
40m
Affected: Visbook Engine
Timeline · 4 updates
  1. identified May 22, 2026, 07:01 AM UTC

    We are aware that some users are experiencing slow performance in the departure list after a recent app update. We have located the issue and a fix is on its way. Normal performance should be restored shortly. We apologize for the inconvenience.

  2. resolved May 22, 2026, 07:23 AM UTC

    A new version has been released that fixes the slow departure list. Please update VisBook to get the fix. We apologize for the inconvenience.

  3. investigating May 22, 2026, 07:27 AM UTC

    The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences. We recommend that all customers upgrade to version 7.8.848 as soon as possible. This release includes important improvements that address performance issues in the departure list experienced in earlier versions. To ensure optimal stability and performance, please update at your earliest convenience.

  4. resolved May 22, 2026, 07:41 AM UTC

    The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.We recommend that all customers upgrade to version 7.8.848 as soon as possible. This release includes important improvements that address performance issues in the departure list experienced in earlier versions.To ensure optimal stability and performance, please update at your earliest convenience.

Read the full incident report →

Minor February 17, 2026

Login Crash Issue

Detected by Pingoru
Feb 17, 2026, 03:07 PM UTC
Resolved
Feb 17, 2026, 06:36 PM UTC
Duration
3h 29m
Affected: Visbook Engine
Timeline · 4 updates
  1. identified Feb 17, 2026, 03:07 PM UTC

    VisBook Desktop Client v7.8.824 - Login Crash Issue We are aware of reports that version 7.8.824 is crashing after login for some users. Our team is working on a fix. A new release will be available soon, and we will update you once it’s ready for download. We apologize for the inconvenience.

  2. identified Feb 17, 2026, 04:08 PM UTC

    Update: Fix Identified for VisBook Desktop Client v7.8.824 We have identified the cause of the crash occurring after login in version 7.8.824. A new version is currently being prepared for release. Estimated Time of Arrival (ETA): 30 minutes. We will provide a final update as soon as the new version is available for download. Thank you for your patience.

  3. investigating Feb 17, 2026, 06:14 PM UTC

    Update: Delay in New Release for VisBook Desktop Client v7.8.824 The preparation of the new update is taking longer than initially expected. We are working as quickly as possible to finalize the fix and make it available for download. We will provide a new update as soon as we have a confirmed release time. We apologize for the continued inconvenience.

  4. resolved Feb 17, 2026, 06:36 PM UTC

    We identified the issue and performed a rollback to the last known stable build. Note: Due to our internal build pipeline, the reverted build (originally version 7.8.823) is now labeled as 7.8.827. Functionally, it is identical to 7.8.823.

Read the full incident report →

Minor January 30, 2026

Issues with spa and table reservations

Detected by Pingoru
Jan 30, 2026, 10:59 AM UTC
Resolved
Jan 30, 2026, 02:24 PM UTC
Duration
3h 24m
Affected: api2.visbook.com / Channel Manager Integrations
Timeline · 2 updates
  1. investigating Jan 30, 2026, 10:59 AM UTC

    We are investigating issues with the integration between Visbook and BookVisit affecting table reservations and spa bookings. Synchronization between systems may be delayed or incomplete. Our team is actively working on a resolution. Please manually verify affected bookings until further notice.

  2. resolved Jan 30, 2026, 02:24 PM UTC

    The integration issues between Visbook and BookVisit affecting table reservations and spa bookings have been resolved as of 13:20 CET. All systems are now operating normally. Thank you for your patience.

Read the full incident report →

Minor December 15, 2025

Investigating ongoing issue with login and use of VisBook

Detected by Pingoru
Dec 15, 2025, 07:31 PM UTC
Resolved
Dec 15, 2025, 08:27 PM UTC
Duration
55m
Affected: Visbook Enginereservations.visbook.com / Guest Bookingsapi2.visbook.com / Channel Manager Integrationsapi3.visbook.comvisdoc.visbook.com
Timeline · 3 updates
  1. investigating Dec 15, 2025, 07:31 PM UTC

    We are aware of a potential issue and are currently investigating. We will provide updates as we learn more.

  2. monitoring Dec 15, 2025, 07:51 PM UTC

    Mitigations are in place, and services should be recovering. We are still investigating the root cause.

  3. resolved Dec 15, 2025, 08:27 PM UTC

    The services has been stable for an extended period. Therefore, we are marking the issue as resolved. However, we will continue to investigate the root cause and deploy mitigations if necessary.

Read the full incident report →

Minor December 12, 2025

High Network Latency

Detected by Pingoru
Dec 12, 2025, 05:53 PM UTC
Resolved
Dec 15, 2025, 08:30 PM UTC
Duration
3d 2h
Affected: Visbook Engine
Timeline · 2 updates
  1. investigating Dec 12, 2025, 05:53 PM UTC

    Some customers may experience slowness due to network issues at an internet service provider affecting parts of the Nordic region. We are monitoring the situation and will provide updates as more information becomes available.

  2. resolved Dec 15, 2025, 08:30 PM UTC

    The issue has been resolved. Slowness affecting some customers was related to network issues at an internet service provider in Sweden. Service performance has been stable and operating normally since Friday.

Read the full incident report →