Veson Nautical incident

Shipfix platform is not accessible

Critical Resolved View vendor source →

Veson Nautical experienced a critical incident on September 18, 2025 affecting Email API and Email Inbound and 1 more component, lasting 6h 32m. The incident has been resolved; the full update timeline is below.

Started
Sep 18, 2025, 06:07 AM UTC
Resolved
Sep 18, 2025, 12:39 PM UTC
Duration
6h 32m
Detected by Pingoru
Sep 18, 2025, 06:07 AM UTC

Affected components

Email APIEmail InboundEmail OutboundEmail ProcessingMarket MonitorMapsData InsightsVessel & Port Directory

Update timeline

  1. identified Sep 18, 2025, 06:07 AM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Sep 18, 2025, 06:23 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Sep 18, 2025, 06:46 AM UTC

    We have identified the issue. The fix is in progress

  4. identified Sep 18, 2025, 07:10 AM UTC

    The fix is still in progress. Our team is dedicated on fixing the issue. Next update in 30 minutes

  5. identified Sep 18, 2025, 08:00 AM UTC

    The fix is still in progress. Our team is dedicated on fixing the issue. Next update in 30 minutes

  6. identified Sep 18, 2025, 09:19 AM UTC

    The root cause has been identified and our team is working on restoring our services as quickly as possible. We are very sorry about this incident and will provide next update in 30 minutes

  7. identified Sep 18, 2025, 10:12 AM UTC

    The restoration of our services is in progress, it should be completed shortly. We will provide another update in the next 30 minutes.

  8. identified Sep 18, 2025, 10:50 AM UTC

    The restoration of our services is still in progress, it should be completed shortly. We will provide another update in the next 30 minutes.

  9. identified Sep 18, 2025, 11:15 AM UTC

    The service is now partially recovered and we are reprocessing emails from this morning

  10. monitoring Sep 18, 2025, 11:32 AM UTC

    The service is restored and we are monitoring email reprocessing

  11. resolved Sep 18, 2025, 12:39 PM UTC

    This incident has been resolved.