Platform Science Outage History

Started Oct 21, 2026, 11:40 AM UTC· resolved Oct 22, 2026, 07:45 AM UTC

1. investigating Oct 21, 2026, 11:40 AM UTC

   Dear Customers, We are currently experiencing an outage affecting the solid-transport.com website. Please rest assured that all core applications remain fully functional and unaffected. We apologize for the inconvenience and are working to resolve the situation as quickly as possible. Thank you for your patience.

2. investigating Oct 21, 2026, 01:20 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 21, 2026, 01:21 PM UTC

   We are continuing to investigate this issue.

4. resolved Oct 22, 2026, 07:45 AM UTC

   The maintenance for solid-transport.com is now resolved. All website content and resources have been officially moved to platformscience.eu. Moving forward, please visit platformscience.eu for all updates, information, and direct access to customer portals. Thank you for your patience during this transition.

Read the full incident report →

Started Oct 19, 2026, 08:51 AM UTC· resolved Oct 19, 2026, 12:16 PM UTC

1. investigating Oct 19, 2026, 08:51 AM UTC

   We are currently investigating an issue affecting our Estimated Time of Arrival (ETA) service. While existing ETAs remain visible, new ETA calculations are temporarily unavailable due to a service disruption with one of our mapping providers. Our technical team is actively working to resolve the issue as quickly as possible. We apologize for the inconvenience and will provide further updates as soon as more information becomes available. Thank you for your patience.

2. identified Oct 19, 2026, 10:40 AM UTC

   The root cause affecting the ETA calculation service has been identified. A fix is currently being applied, and we are awaiting a system update to restore normal operations. We will provide another update once the fix is deployed.

3. monitoring Oct 19, 2026, 11:10 AM UTC

   A fix has deployed to resolve the issue. ETA calculations and updates are beginning to recover across all impacted applications. We are closely monitoring system metrics to ensure complete stability.

4. resolved Oct 19, 2026, 12:16 PM UTC

   Services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Oct 07, 2026, 07:20 AM UTC· resolved Oct 07, 2026, 12:57 PM UTC

1. investigating Oct 07, 2026, 07:20 AM UTC

   We are currently investigating an issue affecting the Messages section for individual units in FleetCockpit+. Some users may encounter a "Something went wrong" error when attempting to view vehicle messages. Our engineering team is actively analyzing the cause. Further updates will be provided as soon as more information becomes available. Thank you for your patience.

2. identified Oct 07, 2026, 08:49 AM UTC

   The cause of the "Something went wrong" error on Unit Messages has been identified. A fix is being finalized and will be deployed soon. Thank you for your patience.

3. monitoring Oct 07, 2026, 11:55 AM UTC

   A fix has been deployed. We are currently monitoring system performance to ensure normal service is fully restored. If you still encounter issues, please clear your browser cache. Thank you for your understanding.

4. resolved Oct 07, 2026, 12:57 PM UTC

   The maintenance and deployment have been successfully completed, and the issue affecting the Unit Messages page in FLC+ is now fully resolved. All services are operating normally. If you continue to experience any display issues, please refresh your page or clear your browser cache. Thank you for your patience and understanding.

Read the full incident report →

Started Oct 01, 2026, 06:49 AM UTC· resolved Oct 01, 2026, 12:00 PM UTC

1. investigating Oct 01, 2026, 06:49 AM UTC

   We are currently investigating an issue where some devices are incorrectly displayed as offline in Fleetworks and FleetCockpit , despite being online and operational. Our engineering team is actively working to resolve this display delay. Further updates will be provided as soon as more information is available. Thank you for your patience.

2. identified Oct 01, 2026, 08:47 AM UTC

   The issue has been identified from our side and a fix is being implemented We apologize for any inconvenience this may cause.

3. monitoring Oct 01, 2026, 09:49 AM UTC

   A fix has been applied. Device status updates are recovering, and we are closely monitoring the results to confirm complete resolution.

4. resolved Oct 01, 2026, 12:00 PM UTC

   All services are now operating normally. We have verified full stability, but will continue monitoring closely.

Read the full incident report →

Started Sep 21, 2026, 09:51 PM UTC· resolved Sep 21, 2026, 11:46 PM UTC

1. identified Sep 21, 2026, 10:23 PM UTC

   We’re currently experiencing a network service disruption on our backend systems. Our team is working to identify the root cause and implement a solution. Users may be experiencing login failures or unability to use certain parts of our web applications. We're working hard to fix the issue and will update you as soon as we have more information. Thank you for your patience.

2. monitoring Sep 21, 2026, 10:30 PM UTC

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

3. resolved Sep 21, 2026, 11:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 02:24 PM UTC· resolved Sep 15, 2026, 06:31 PM UTC

1. investigating Sep 15, 2026, 02:24 PM UTC

   We are currently experiencing a service disruption on the FleetHours web application, resulting in a 504 Gateway Time-out error. Our team is working to identify the root cause and implement a solution. We're working hard to fix the issue and will update you as soon as we have more information. Thank you for your patience.

2. identified Sep 15, 2026, 03:16 PM UTC

   We have identified the cause of the issue affecting the FleetHours web application. Our engineering team is currently applying a fix to restore service as quickly as possible.

3. resolved Sep 15, 2026, 06:31 PM UTC

   The issue impacting the FleetHours web application has been fully resolved. Corrective measures have been successfully deployed, and the application service is now fully operational and stable. All systems are back to normal performance. We apologize for any inconvenience this service disruption may have caused and thank you for your patience and understanding.

Read the full incident report →

Started Sep 15, 2026, 12:39 PM UTC· resolved Sep 15, 2026, 12:39 PM UTC

1. resolved Sep 15, 2026, 12:39 PM UTC

   Earlier today, some users experienced temporary issues downloading files via the FleetWorks SOAP API. The issue has been identified and fully resolved, and all file transfer services are now operating normally. We sincerely apologize for any disruption or inconvenience this may have caused to your operations.

Read the full incident report →

Started Jul 30, 2026, 06:58 AM UTC· resolved Jul 30, 2026, 10:57 AM UTC

1. investigating Jul 30, 2026, 06:58 AM UTC

   We are currently investigating this issue.

2. identified Jul 30, 2026, 07:13 AM UTC

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

3. monitoring Jul 30, 2026, 07:13 AM UTC

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

4. resolved Jul 30, 2026, 10:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 14, 2026, 09:40 AM UTC· resolved Jul 14, 2026, 12:46 PM UTC

1. investigating Jul 14, 2026, 09:40 AM UTC

   We’re currently experiencing a service disruption on the customer hub and all applications. Our team is working to identify the root cause and implement a solution. Users may be experiencing: Slow loading times or intermittent error messages. Difficulty logging in to their accounts. Delays in accessing the Customer Hub and applications. We're working hard to fix the issue and will update you here as soon as we have more information. Thank you for your patience.

2. identified Jul 14, 2026, 10:01 AM UTC

   The issue has been identified on our side, and a fix is being implemented. We apologize for any inconvenience this may cause.

3. identified Jul 14, 2026, 10:01 AM UTC

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

4. identified Jul 14, 2026, 10:07 AM UTC

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

5. monitoring Jul 14, 2026, 10:16 AM UTC

   A fix has been successfully implemented, and the Customer Hub, along with all associated applications are now fully accessible again. Our team is continuing to closely monitor system health and performance to ensure ongoing stability. Thank you again for your patience.

6. resolved Jul 14, 2026, 12:46 PM UTC

   Services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Jul 03, 2026, 10:14 AM UTC· resolved Jul 03, 2026, 11:04 AM UTC

1. investigating Jul 03, 2026, 10:14 AM UTC

   We are currently investigating an issue with the DVR Toolkit (VI Legacy) that is preventing device pairing. Customers may be unable to pair devices at this time. Our team is actively investigating the root cause and will provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

2. resolved Jul 03, 2026, 11:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2026, 07:49 AM UTC· resolved Jun 30, 2026, 08:20 AM UTC

1. identified Jun 30, 2026, 07:49 AM UTC

   We’re currently experiencing a service disruption. To apply the fix, the application needs to be restarted. Action Required: > We are requesting that all users manually close and exit the application as soon as possible. Please note that when the platform restarts, any remaining active users will be automatically logged out (kicked out) of the system. We apologize for the brief interruption and appreciate your quick cooperation. We expect the platform to be fully stable and available shortly.

2. monitoring Jun 30, 2026, 08:13 AM UTC

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

3. resolved Jun 30, 2026, 08:20 AM UTC

   Services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started May 13, 2026, 12:11 PM UTC· resolved May 14, 2026, 12:10 PM UTC

1. investigating May 13, 2026, 12:11 PM UTC

   We are currently investigating reports of connectivity issues with Vi Access within the Customer Hub. Users may encounter errors or a blank page when attempting to log in. We're working hard to fix the issue and will update you as soon as we have more information. Thank you for your patience.

2. monitoring May 13, 2026, 01:00 PM UTC

   A fix has been successfully implemented to resolve the connectivity issues with Vi Access within the Customer Hub. Users should now be able to access the service normally. We are currently monitoring the platform to ensure stability.

3. resolved May 14, 2026, 12:10 PM UTC

   The issue has been fully resolved, and service is now operating normally. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Apr 20, 2026, 12:13 PM UTC· resolved Apr 20, 2026, 02:32 PM UTC

1. identified Apr 20, 2026, 12:13 PM UTC

   We are currently experiencing a service disruption affecting device connectivity. Our team has identified that this is due to an issue with data transmission issue with our partner. As a result, some devices may appear as "Offline." We are in direct contact with the provider to resolve this as a priority. We apologize for the repeated interruption.

2. monitoring Apr 20, 2026, 12:58 PM UTC

   Our partner has resolved the transmission issue. We are now processing the backlog of delayed data, and devices should gradually appear back online. We can confirm that no data was lost during this disruption. We are closely monitoring the situation to ensure a full return to normal operations.

3. resolved Apr 20, 2026, 02:32 PM UTC

   Service is fully restored. The issue has been fixed, and all devices are back online. Data ingestion is flowing normally, and no data loss occurred. We apologize for the inconvenience caused by this disruption.

Read the full incident report →

Started Apr 14, 2026, 10:59 AM UTC· resolved Apr 14, 2026, 07:12 PM UTC

1. investigating Apr 14, 2026, 10:59 AM UTC

   We are currently investigating performance issues affecting our trace processing pipeline. As a result, users may experience a delays in data appearing on their dashboards. Our engineering team is fully mobilized to restore normal service as quickly as possible. We sincerely apologize for this disruption.

2. identified Apr 14, 2026, 11:25 AM UTC

   The issue has been identified and a fix is currently being implemented. We are working to restore normal service. We apologize for any inconvenience this may cause

3. monitoring Apr 14, 2026, 12:16 PM UTC

   A fix has been deployed, and we are currently monitoring the recovery. We expect the processing backlog to clear shortly. Thank you for your patience.

4. resolved Apr 14, 2026, 07:12 PM UTC

   Processing delays have been resolved, and the system is back to normal. We will continue to monitor the situation closely to ensure continued stability. We appreciate your patience while we worked to restore our service standards.

Read the full incident report →

Started Apr 09, 2026, 11:24 AM UTC· resolved Apr 09, 2026, 01:04 PM UTC

1. identified Apr 09, 2026, 11:24 AM UTC

   We have identified the cause of the data discrepancy affecting our BI reporting suite. Our engineering team is currently working on a fix to restore full data accuracy. We apologize for any inconvenience this may cause. Thank you for your patience and consideration.

2. resolved Apr 09, 2026, 01:04 PM UTC

   The issue has been resolved and the fix is fully deployed. All BI reports and dashboards are now reflecting the latest data. We apologize for the interruption to your workflow and appreciate your continued support.

Read the full incident report →

Started Apr 02, 2026, 09:47 AM UTC· resolved Apr 03, 2026, 06:44 AM UTC

1. monitoring Apr 02, 2026, 09:47 AM UTC

   The data transmission issue with our partner has been resolved. Service is getting back to normal, and devices are gradually coming back online. We are monitoring the connection's stability to ensure a full recovery for all users.

2. identified Apr 02, 2026, 12:03 PM UTC

   We are currently experiencing a new service disruption affecting device connectivity. Our team has identified that this is due to a recurring data transmission issue with our partner. As a result, some devices may appear as "Offline." We are in direct contact with the provider to resolve this as a priority. We apologize for the repeated interruption.

3. monitoring Apr 02, 2026, 12:46 PM UTC

   The service disruption caused by our partner has been resolved. All systems are getting back to normal, and devices are reconnecting. We are closely monitoring the connection's stability to ensure all services return to 100% functionality. Thank you for your patience during this repeated disruption.

4. resolved Apr 03, 2026, 06:44 AM UTC

   We have confirmed that the connectivity issues have been resolved. All devices are back online and data transmission is stable. We apologize for the inconvenience caused by this double disruption.

Read the full incident report →

Started Mar 19, 2026, 09:18 AM UTC· resolved Mar 24, 2026, 01:15 PM UTC

1. investigating Mar 19, 2026, 09:18 AM UTC

   We’re currently experiencing a service disruption on Fleetworks, FleetCockpit and FleetCockpit+ Users may be experiencing a performance issue on these applications Our team is working to identify the root cause and implement a solution. We're working hard to fix the issue and will update you as soon as we have more information.

2. identified Mar 19, 2026, 10:45 AM UTC

   As part of our ongoing investigation into the recent performance issues, we have temporarily disabled the "Places" feature in FleetCockpit+. This measure is intended to stabilize system resources and prevent further connection pool saturation. Required Action for Users: To ensure these changes take effect and to restore optimal performance on your side, we kindly ask all users to clear their browser cache and cookies before logging back into the applications. Our engineering team is monitoring the impact of this deactivation. Thank you for your cooperation and patience.

3. monitoring Mar 19, 2026, 12:28 PM UTC

   Systems are stable. We are currently monitoring performance to ensure continued reliability.

4. resolved Mar 24, 2026, 01:15 PM UTC

   System stability has been fully restored across FleetWorks, FleetCockpit, and FleetCockpit+. To ensure long-term reliability, the "Places" feature has been temporarily disabled while we implement architectural optimizations and enhanced caching mechanisms. We will provide further updates through standard release notes when the feature is ready to be re-enabled. Thank you for your patience.

Read the full incident report →

Started Mar 17, 2026, 10:58 AM UTC· resolved Mar 17, 2026, 06:55 PM UTC

1. investigating Mar 17, 2026, 10:58 AM UTC

   We are currently experiencing a service disruption affecting FleetWorks, FleetCockpit and FLeetCockpit+. User Impact: Users may experience significant slowness within the applications. Additionally, some users may be automatically logged out and required to log in multiple times. Our engineering team is actively working to identify the root cause and implement a solution as quickly as possible. We will provide another update as soon as more information becomes available.

2. investigating Mar 17, 2026, 11:47 AM UTC

   We have observed that service levels for FleetWorks, FleetCockpit and FLeetCockpit+ have returned to normal. Looking to identify the root cause we keep monitoring the situation.

3. monitoring Mar 17, 2026, 03:08 PM UTC

   Service levels for FleetWorks, FleetCockpit, and FleetCockpit+ have returned to normal. We are closely monitoring the situation to ensure continued stability.

4. monitoring Mar 17, 2026, 03:12 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 17, 2026, 06:55 PM UTC

   Our team has determined that the previously reported issue is now fully resolved. Thank you for your patience during this incident.

Read the full incident report →

Started Mar 11, 2026, 08:25 AM UTC· resolved Mar 12, 2026, 03:45 PM UTC

1. investigating Mar 11, 2026, 08:25 AM UTC

   We are currently experiencing an issue with the mapping display within FleetHours. Customers will temporarily be unable to view or use maps within the FleetHours. Our team is actively working to renew the license and restore service as quickly as possible. We apologize for the inconvenience and will provide updates as they become available.

2. investigating Mar 11, 2026, 08:35 AM UTC

   We are continuing to investigate this issue.

3. identified Mar 11, 2026, 11:38 AM UTC

   The issue has been identified, and a fix is being implemented. We apologize for any inconvenience this may cause. Please contact support if you have further questions.

4. identified Mar 12, 2026, 12:57 PM UTC

   We are currently awaiting final verification from our service provider to restore mapping services. Our team is monitoring the situation closely and will confirm as soon as the maps are back online. We apologize for the continued inconvenience.

5. resolved Mar 12, 2026, 03:45 PM UTC

   We are pleased to announce that the mapping functionality in FleetHours has been fully restored. Thank you for your patience and understanding during this period.

Read the full incident report →

Started Jan 21, 2026, 12:54 PM UTC· resolved Jan 30, 2026, 09:32 AM UTC

1. identified Jan 21, 2026, 12:54 PM UTC

   We are currently investigating reports of slow loading times and degraded performance within Fleet Cockpit Plus. Our engineering teams are working to identify a permanent fix for this issue. Recommended Workaround: To improve application responsiveness and loading speeds, we highly recommend that users apply a global filter to reduce the number of units queried at once. This workaround will significantly enhance performance while we continue to work on a long-term solution. We apologize for the inconvenience and will provide further updates as they become available.

2. identified Jan 22, 2026, 03:04 PM UTC

   The team is preparing an update to improve system performance and stability. This deployment is scheduled to be completed by Thursday evening. Thank you for your patience and consideration. We apologize for any inconvenience this may cause.

3. identified Jan 23, 2026, 11:56 AM UTC

   Some customers have reported issues regarding application performance. Following our recent update, you may notice an error in the "Current Location" column. If you encounter this, we recommend that users clear their browser cache to ensure they are running the latest version of the platform. We are treating this matter with the highest priority. Thank you for your patience.

4. monitoring Jan 29, 2026, 07:53 AM UTC

   To ensure optimal application stability and speed, we are temporarily simplifying how locations are displayed; as a result, you will now see the City name only, rather than the place name, until our upcoming performance optimizations are completed.

5. resolved Jan 30, 2026, 09:32 AM UTC

   Stability is restored. We are now monitoring the platform closely and have transitioned to a streamlined location display to ensure peak performance ahead of our upcoming upgrades.

Read the full incident report →

Started Jan 15, 2026, 01:50 PM UTC· resolved Jan 15, 2026, 03:06 PM UTC

1. identified Jan 15, 2026, 01:50 PM UTC

   We are currently investigating reports of slow loading times within the FleetCockpit+ application. Our team is working to resolve this as quickly as possible. We will provide further updates shortly We apologize for any inconvenience this may cause.

2. monitoring Jan 15, 2026, 02:38 PM UTC

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

3. resolved Jan 15, 2026, 03:06 PM UTC

   Services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Jan 09, 2026, 01:41 PM UTC· resolved Jan 09, 2026, 05:47 PM UTC

1. investigating Jan 09, 2026, 01:41 PM UTC

   We’re currently experiencing a service disruption on FleetCockpit+ Our team is working to identify the root cause and implement a solution. Users may encounter slow response times or intermittent errors when accessing certain pages. We're working hard to fix the issue and will update you as soon as we have more information. Thank you for your patience.

2. monitoring Jan 09, 2026, 01:47 PM UTC

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

3. resolved Jan 09, 2026, 05:47 PM UTC

   Services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Dec 18, 2025, 02:24 PM UTC· resolved Dec 19, 2025, 08:28 AM UTC

1. investigating Dec 18, 2025, 02:24 PM UTC

   We are currently experiencing a service disruption affecting FleetCockpit+. Our teams are actively investigating the issue to identify the root cause and implement a fix. During this time, users may experience slow loading or difficulties accessing certain pages within the application. Further updates will be shared as more information becomes available.

2. identified Dec 18, 2025, 03:23 PM UTC

   The issue has been identified, and a fix is being implemented. We apologize for any inconvenience this may cause.

3. monitoring Dec 18, 2025, 03:30 PM UTC

   A fix has been implemented and we are monitoring the results

4. resolved Dec 19, 2025, 08:28 AM UTC

   Services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Dec 17, 2025, 02:13 PM UTC· resolved Dec 21, 2025, 05:44 PM UTC

1. investigating Dec 17, 2025, 02:13 PM UTC

   We are currently investigating an issue affecting SOLID Expert customers where previously configured locks on expenses and bonuses may no longer be applied, which could lead to unintended automatic changes. In addition, some users may temporarily be unable to lock or unlock expenses and bonuses. Application administrators can review user permissions in the application settings if needed. Our teams are actively working to identify the cause and restore normal behavior. Further updates will be shared as soon as more information becomes available.

2. identified Dec 17, 2025, 02:33 PM UTC

   The issue has been identified, and a fix is being implemented. We apologize for any disruption this may cause and will provide further updates as the situation progresses.

3. identified Dec 18, 2025, 08:36 AM UTC

   A fix addressing the issue affecting expense and bonus locks is currently being tested. Our teams are closely monitoring the situation while validation is ongoing. Further updates will be shared once testing of the fix is completed.

4. identified Dec 19, 2025, 03:42 PM UTC

   The configured locks have been restored, with further improvements ongoing to ensure full stability. We may schedule a maintenance session in the coming days for these improvements. We will keep you informed.

5. resolved Dec 21, 2025, 05:44 PM UTC

   SOLID services are now operating normally, and we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →

Started Dec 16, 2025, 08:49 AM UTC· resolved Dec 16, 2025, 12:00 PM UTC

1. identified Dec 16, 2025, 08:49 AM UTC

   Due to an external issue with our vendor, reports will not be up to date. We are expecting a fix from the vendor later today. We apologize for any inconvenience this may cause.

2. monitoring Dec 16, 2025, 10:35 AM UTC

   We continue to monitor system health as our partner provide a fix. An update will be provided as more information becomes available.

3. resolved Dec 16, 2025, 12:00 PM UTC

   Our partner confirmed that the issue is fixed, we will continue to monitor to ensure stability. We remain actively engaged to ensure system stability is maintained.

Read the full incident report →