Veson Nautical Outage History

Veson Nautical is up right now

Veson Nautical had 27 outages in the last 2 years totaling 4h 43m of downtime — averaging 1.1 incidents per month.

There were 27 Veson Nautical outages since May 19, 2025 totaling 4h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.veson.com

Minor June 9, 2025

IMOS Platform Messaging Service elevated error rate

Detected by Pingoru
Jun 09, 2025, 02:13 AM UTC
Resolved
Jun 09, 2025, 06:14 AM UTC
Duration
4h
Affected: Messaging Services
Timeline · 4 updates
  1. investigating Jun 09, 2025, 02:13 AM UTC

    We are aware that some customers are experiencing scheduled task failures within the IMOS Platform Messaging Service. We are actively investigating the issue and will update when we have further details.

  2. identified Jun 09, 2025, 02:21 AM UTC

    The issue has been identified and is being resolved - impacted clients should see service return to normal momentarily.

  3. monitoring Jun 09, 2025, 05:19 AM UTC

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

  4. resolved Jun 09, 2025, 06:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2025

VIP Web Application - Service degraded

Detected by Pingoru
May 19, 2025, 10:31 PM UTC
Resolved
May 19, 2025, 11:14 PM UTC
Duration
42m
Affected: Web Application
Timeline · 4 updates
  1. investigating May 19, 2025, 10:31 PM UTC

    We are aware that some customers are experiencing service degradation within the VIP Web Application. We are actively investigating the issue and will update when we have further details.

  2. investigating May 19, 2025, 10:35 PM UTC

    We are continuing to investigate this issue.

  3. identified May 19, 2025, 10:58 PM UTC

    The issue has been identified, and a fix is currently being implemented. As part of this process, users may be logged out and will need to log in again

  4. resolved May 19, 2025, 11:14 PM UTC

    This incident has been resolved.

Read the full incident report →