Critical October 15, 2026 - Detected by Pingoru
- Oct 15, 2026, 08:36 AM UTC
- Resolved
- Oct 15, 2026, 09:52 AM UTC
- Duration
- 1h 16m
Affected: Web Application
Timeline · 4 updates
-
investigating Oct 15, 2026, 08:36 AM UTC
We are aware that some customers are unable to access the Veson Platform Web Application. We are actively investigating the issue and will update when we have further details.
-
identified Oct 15, 2026, 09:43 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 15, 2026, 09:44 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 15, 2026, 09:52 AM UTC
This incident has been resolved.
Read the full incident report →
Notice September 30, 2026 - Detected by Pingoru
- Sep 30, 2026, 09:41 AM UTC
- Resolved
- Sep 30, 2026, 09:41 AM UTC
- Duration
- —
Affected: Mail
Timeline · 1 update
-
resolved Sep 30, 2026, 09:41 AM UTC
We have identified an issue on Veson Mail which has now been resolved.
Read the full incident report →
Critical September 29, 2026 - Detected by Pingoru
- Sep 29, 2026, 11:51 AM UTC
- Resolved
- Sep 29, 2026, 02:22 PM UTC
- Duration
- 2h 31m
Affected: Email Processing
Timeline · 4 updates
-
investigating Sep 29, 2026, 11:51 AM UTC
We are currently investigating this issue.
-
identified Sep 29, 2026, 11:51 AM UTC
We have identified the issue and we are working on a fix
-
monitoring Sep 29, 2026, 12:36 PM UTC
The issue has been mitigated and we are currently processing pending emails
-
resolved Sep 29, 2026, 02:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 10:01 AM UTC
- Resolved
- Sep 21, 2026, 10:17 AM UTC
- Duration
- 16m
Affected: Web ApplicationAPIs
Timeline · 2 updates
-
monitoring Sep 21, 2026, 10:01 AM UTC
Our monitoring systems have identified a degraded performance, we have applied a fix and are monitoring the effect
-
resolved Sep 21, 2026, 10:17 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 03:48 PM UTC
- Resolved
- Sep 15, 2026, 04:21 PM UTC
- Duration
- 32m
Affected: Messaging ServicesWeb Application
Timeline · 3 updates
-
identified Sep 15, 2026, 03:48 PM UTC
We are aware that some customers may be experiencing delayed outbound email notification delivery within the IMOS Platform Messaging Service. We are actively investigating the issue and will update when we have further details.
-
monitoring Sep 15, 2026, 04:18 PM UTC
A fix has been implemented and we are monitoring the situation. Outbound email delivery has resumed. Email sent via the messaging service between 4:00 UTC and 16:04 UTC may have failed delivery. Please reach out to Veson Support if you need assistance re-sending email.
-
resolved Sep 15, 2026, 04:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 08:02 AM UTC
- Resolved
- Sep 09, 2026, 01:24 PM UTC
- Duration
- 5h 22m
Affected: Web Application
Timeline · 4 updates
-
investigating Sep 09, 2026, 08:02 AM UTC
We are aware that some customers are experiencing session timeouts within the IMOS Platform Web Application. We are actively investigating the issue and will update when we have further details.
-
identified Sep 09, 2026, 09:56 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 09, 2026, 01:05 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 09, 2026, 01:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 08:30 PM UTC
- Resolved
- Sep 01, 2026, 07:09 AM UTC
- Duration
- 10h 38m
Affected: Email InboundEmail Outbound
Timeline · 5 updates
-
investigating Aug 31, 2026, 08:30 PM UTC
Customers may experience delays in receiving emails or failures when sending them due to an ongoing Microsoft Exchange Online incident
-
identified Aug 31, 2026, 09:32 PM UTC
We are monitoring Microsoft Exchange Online status page and we will provide update as soon as possible
-
identified Aug 31, 2026, 10:09 PM UTC
We are continuing to monitor Microsoft Exchange Online status page and we will provide update as soon as possible
-
monitoring Sep 01, 2026, 05:31 AM UTC
Microsoft confirms that mail flow is working as expected. We are monitoring the situation
-
resolved Sep 01, 2026, 07:09 AM UTC
We're no longer seeing issues on the Microsoft side, and all pending emails have now been processed.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 05:49 PM UTC
- Resolved
- Aug 31, 2026, 08:36 PM UTC
- Duration
- 2h 46m
Affected: Data Lake
Timeline · 4 updates
-
identified Aug 31, 2026, 05:49 PM UTC
Clients with Datalake environments hosted in the US-EAST-1 region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. We are actively monitoring Snowflake service updates for the region.
-
monitoring Aug 31, 2026, 08:20 PM UTC
Snowflake is showing all systems operational in the US-EAST-1 region. We are reviewing the US-EAST-1 account and will provide an update shortly.
-
monitoring Aug 31, 2026, 08:35 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 31, 2026, 08:36 PM UTC
Successful ingestion of into all Datalake environments in the US-EAST-1 region has been confirmed.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 09:33 AM UTC
- Resolved
- Aug 18, 2026, 09:49 AM UTC
- Duration
- 16m
Affected: Email APIEmail InboundEmail OutboundEmail ProcessingMarket MonitorMapsData InsightsVessel & Port Directory
Timeline · 2 updates
-
monitoring Aug 18, 2026, 09:33 AM UTC
We noticed some slowness for few minutes. A fix has been provided. We are closely monitoring the incident.
-
resolved Aug 18, 2026, 09:49 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 05:11 AM UTC
- Resolved
- Aug 14, 2026, 05:38 AM UTC
- Duration
- 27m
Affected: Email InboundEmail Outbound
Timeline · 5 updates
-
investigating Aug 14, 2026, 05:11 AM UTC
We are currently investigating this issue.
-
identified Aug 14, 2026, 05:12 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Aug 14, 2026, 05:20 AM UTC
The issue is now resolved and we are actively catching up on the delay.
-
monitoring Aug 14, 2026, 05:33 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 14, 2026, 05:38 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 09:44 AM UTC
- Resolved
- Jul 17, 2026, 09:57 AM UTC
- Duration
- 13m
Timeline · 3 updates
-
identified Jul 17, 2026, 09:44 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 17, 2026, 09:54 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 17, 2026, 09:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2026, 09:00 AM UTC
- Resolved
- Jul 14, 2026, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 14, 2026, 09:12 AM UTC
Our systems alerted us to a degraded platform between at 8:45am, the issue was quickly resolved and will continue monitoring.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 08:38 AM UTC
- Resolved
- Jul 01, 2026, 09:44 AM UTC
- Duration
- 1h 6m
Affected: Email APIEmail InboundEmail OutboundEmail Processing
Timeline · 4 updates
-
investigating Jul 01, 2026, 08:38 AM UTC
We are currently investigating this issue.
-
identified Jul 01, 2026, 08:41 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 01, 2026, 09:10 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 01, 2026, 09:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 03:42 PM UTC
- Resolved
- Jun 29, 2026, 04:58 PM UTC
- Duration
- 1h 16m
Affected: Email Processing
Timeline · 4 updates
-
identified Jun 29, 2026, 03:42 PM UTC
We have identified the issue and emails are being processed again at the moment
-
identified Jun 29, 2026, 03:42 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jun 29, 2026, 04:20 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 29, 2026, 04:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 09:34 PM UTC
- Resolved
- Jun 17, 2026, 09:43 PM UTC
- Duration
- 8m
Affected: Web Application
Timeline · 3 updates
-
investigating Jun 17, 2026, 09:34 PM UTC
We are aware that customers with a home region in the US are unable to access the IMOS Platform Web Application. We are actively investigating the issue and will update when we have further details.
-
monitoring Jun 17, 2026, 09:37 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 17, 2026, 09:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 02:09 PM UTC
- Resolved
- Jun 12, 2026, 05:15 PM UTC
- Duration
- 3h 6m
Affected: Web Application
Timeline · 4 updates
-
investigating Jun 12, 2026, 02:09 PM UTC
We are aware that some customers in the EU region may be experiencing performance degradation within the IMOS Platform Web Application. We are actively investigating the issue and will update when we have further details.
-
identified Jun 12, 2026, 02:30 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 12, 2026, 03:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 12, 2026, 05:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 01:40 PM UTC
- Resolved
- Jun 08, 2026, 01:56 PM UTC
- Duration
- 16m
Affected: Email APIEmail InboundEmail OutboundEmail ProcessingMarket MonitorMapsData InsightsVessel & Port Directory
Timeline · 3 updates
-
investigating Jun 08, 2026, 01:40 PM UTC
We are currently investigating some performance issue in production
-
monitoring Jun 08, 2026, 01:50 PM UTC
A fix has been implemented in production and we are now monitoring the platform
-
resolved Jun 08, 2026, 01:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 09:00 AM UTC
- Resolved
- Jun 08, 2026, 10:27 AM UTC
- Duration
- 1h 27m
Affected: APIsVeslink Voyage Reporting
Timeline · 4 updates
-
investigating Jun 08, 2026, 10:19 AM UTC
We are aware that some customers are experiencing delayed form processing within Veslink Voyage Reporting. We are actively investigating the issue and will update when we have further details.
-
identified Jun 08, 2026, 10:20 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 08, 2026, 10:20 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 08, 2026, 10:27 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 10:07 AM UTC
- Resolved
- Jun 05, 2026, 11:07 AM UTC
- Duration
- 1h
Affected: APIs
Timeline · 3 updates
-
investigating Jun 05, 2026, 10:07 AM UTC
We are observing a heightened error rate on the Veslink API DaDesk notifications. We are actively investigating the issue and will update when we have further details.
-
identified Jun 05, 2026, 10:21 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jun 05, 2026, 11:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 01:35 PM UTC
- Resolved
- Jun 02, 2026, 05:46 PM UTC
- Duration
- 4h 11m
Affected: Web Application
Timeline · 3 updates
-
investigating Jun 02, 2026, 01:35 PM UTC
We are aware that some customers in the European Union (EU) region are experiencing service degradation within the IMOS Platform Web Application. We are actively investigating the issue and will update when we have further details.
-
monitoring Jun 02, 2026, 01:45 PM UTC
The service impact has subsided and we are monitoring.
-
resolved Jun 02, 2026, 05:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 09:00 AM UTC
- Resolved
- May 13, 2026, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 13, 2026, 01:54 PM UTC
General slowness of the platform.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 01:26 PM UTC
- Resolved
- Apr 30, 2026, 03:42 PM UTC
- Duration
- 2h 15m
Affected: Email APIEmail InboundEmail OutboundEmail Processing
Timeline · 4 updates
-
investigating Apr 30, 2026, 01:26 PM UTC
We are currently investigating this issue.
-
monitoring Apr 30, 2026, 01:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 30, 2026, 01:58 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 30, 2026, 03:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 04:13 AM UTC
- Resolved
- Mar 24, 2026, 04:58 AM UTC
- Duration
- 45m
Affected: Email InboundEmail Outbound
Timeline · 4 updates
-
investigating Mar 24, 2026, 04:13 AM UTC
We are aware that some clients may be experiencing sending or receiving emails in the Shipfix platform. We will update with further details as our investigation continues.
-
identified Mar 24, 2026, 04:35 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 24, 2026, 04:49 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 24, 2026, 04:58 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 12:02 PM UTC
- Resolved
- Mar 19, 2026, 08:54 PM UTC
- Duration
- 8h 51m
Affected: Web ApplicationAPIsClaims CoCaptain
Timeline · 3 updates
-
identified Mar 19, 2026, 12:02 PM UTC
We are experiencing degraded performance affecting IMOS X UI and workflows, including delayed processing and intermittent errors. Our team is actively investigating and working to resolve the issue.
-
monitoring Mar 19, 2026, 02:45 PM UTC
We have mitigated the performance issue and are continuing to monitor.
-
resolved Mar 19, 2026, 08:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 09:32 AM UTC
- Resolved
- Mar 03, 2026, 03:16 PM UTC
- Duration
- 1d 5h
Affected: Web ApplicationAPIsMessaging Services
Timeline · 6 updates
-
investigating Mar 02, 2026, 09:32 AM UTC
We are aware that some customers hosted in the UAE (me-central-1) region are unable to access the IMOS Platform Web Application. Amazon Web Services (AWS) is currently experiencing an outage affecting multiple datacenters in the region (see https://health.aws.amazon.com/health/status for details). We are actively investigating the issue and will update when we have further details.
-
identified Mar 02, 2026, 09:32 AM UTC
We are working with AWS to understand the scope of the incident and determine a possible timeline for recovery.
-
identified Mar 02, 2026, 01:11 PM UTC
There is a significant outage affecting AWS's UAE (me-central-1) region - two of the three isolated availability zones are offline. One availability zone was struck by objects that created sparks and fire, and another zone is experiencing a localized power outage. Having two out of three availability zones in the UAE offline at the same time is unprecedented. At this time, all IMOS clients hosted in the UAE (me-central-1) region are offline as a result. We have not received an update from AWS since 10:53 AM UTC and we will continue to update as we receive more news.
-
identified Mar 02, 2026, 03:34 PM UTC
The ongoing military conflict in the Middle East has directly impacted AWS operations in the United Arab Emirates. AWS's latest update is that the major outage in the me-central-1 (UAE) region will take at least a day to recover as facilities, power and cooling systems require extensive repairs. Further updates are available directly from AWS at https://health.aws.amazon.com/health/status. We will also update the status page when we have more information. Veson will be in direct contact with affected clients to discuss disaster recovery options.
-
monitoring Mar 02, 2026, 10:40 PM UTC
AWS have partially restored service in the UAE region, and IMOS is now back online. We are continuing to monitor the situation closely, as not all services are fully restored and others are displaying signs of intermittent recovery. Our leadership team will be in touch with affected clients over the coming days to discuss options.
-
resolved Mar 03, 2026, 03:16 PM UTC
IMOS has been stable in the UAE region for 12+ hours. We are closing this incident, and will be closely monitoring activities in the UAE over the next several days.
Read the full incident report →