Is VisBook down?
Last checked 8m agoNo incidents right now.
VisBook is operational right now. Last checked 8m ago; the most recent incident resolved 10d ago.
Real-time VisBook status, recent outages, and incident history — pulled directly from VisBook's official status page at https://status.visbook.com every 5 minutes. Pingoru tracks 5 VisBook services and has captured 5 incidents in the last 90 days (98.44% uptime). Get email, Slack, Discord, or webhook alerts the moment VisBook reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Visbook Engine
Timeline · 3 updates
- investigating · Jun 03, 2026, 02:16 PM UTC
We are aware of a potential issue and are currently investigating. A VisBook restart should fix the issue. We will provide updates as we learn more.
- monitoring · Jun 03, 2026, 02:23 PM UTC
Service has returned to normal, but we are monitoring to ensure continued stability.
- resolved · Jun 04, 2026, 07:34 AM UTC
The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.
Latest: The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.
-
- Visbook Engine
Timeline · 3 updates
- investigating · Jun 01, 2026, 08:39 AM UTC
We are currently experiencing some instability across our services. Our team is actively investigating and working to resolve the issue as quickly as possible. We will provide updates as we learn more.
- monitoring · Jun 01, 2026, 08:39 AM UTC
Service has returned to normal, but we are monitoring to ensure continued stability.
- resolved · Jun 04, 2026, 07:34 AM UTC
The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.
Latest: The incident has been resolved, and we are conducting a post-mortem to prevent future occurrences.
-
- Visbook Engine
Timeline · 4 updates
- 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.
- 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.
- 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.
- 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.
Latest: 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. Th…
-
- Visbook Engine
Timeline · 3 updates
- 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.
- monitoring · Apr 20, 2026, 06:42 AM UTC
Mitigations are in place, and services should be recovering. We are still investigating the root cause.
- 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.
Latest: 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…
-
- Overall
- Investigating ongoing issue ResolvedStarted Jun 03, 2026, 02:16 PM UTC · Resolved Jun 04, 2026, 07:34 AM UTC · 17h 17m
- Investigating ongoing issue ResolvedStarted Jun 01, 2026, 08:39 AM UTC · Resolved Jun 04, 2026, 07:34 AM UTC · 2d 22h
- Started May 22, 2026, 07:01 AM UTC · Resolved May 22, 2026, 07:41 AM UTC · 40m
- Investigating ongoing issue ResolvedStarted Apr 20, 2026, 06:41 AM UTC · Resolved Apr 20, 2026, 07:36 AM UTC · 55m
- Outage detected on status page ResolvedStarted Apr 19, 2026, 08:50 PM UTC · Resolved Apr 20, 2026, 03:31 PM UTC · 18h 41m