VisBook incident

Investigating ongoing issue

Minor Resolved View vendor source →
Started
Apr 20, 2026, 06:41 AM UTC
Resolved
Apr 20, 2026, 07:36 AM UTC
Duration
55m
Detected by Pingoru
Apr 20, 2026, 06:41 AM UTC

Affected components

Visbook Engine

Update timeline

  1. investigating Apr 20, 2026, 06:41 AM UTC

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

  2. monitoring Apr 20, 2026, 06:42 AM UTC

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

  3. resolved Apr 20, 2026, 07:36 AM 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.

Looking to track VisBook downtime and outages?

Pingoru polls VisBook's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when VisBook reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track VisBook alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring VisBook for free

5 free monitors · No credit card required