История сбоев Dat Freight undefined Analytics

1. 3 сентября 2026 г. в 22:07 UTCmonitoring

   В настоящее время существует проблема с одним из наших 3-х сторонних поставщиков, которая влияет на услуги DAT. Мы продолжаем работать с нашим провайдером и в ближайшее время предоставим обновленную информацию.

2. 3 сентября 2026 г. в 22:13 UTCmonitoring

   Мы продолжаем отслеживать любые дополнительные проблемы.

3. 3 сентября 2026 г. в 22:39 UTCmonitoring

   Мы начинаем видеть некоторое восстановление от нашего 3-го поставщика услуг, но мы продолжаем следить за здоровьем обслуживания по всей платформе.

4. 3 сентября 2026 г. в 23:52 UTCresolved

   Наши инженерные команды подтвердили работоспособность платформы и подтвердили, что проблема решена с нашим 3-м поставщиком.

Автоматический перевод официального обновления инцидента.

1. 27 июля 2026 г. в 14:02 UTCinvestigating

   Мы знаем, что некоторые пользователи не могут размещать или искать загрузки прямо сейчас в DAT One. Статус: Инженеры активно исследуют и решают вопрос. Следующие шаги: Пожалуйста, вернитесь в ближайшее время или проследите за обновлениями status.dat.com в режиме реального времени. Спасибо за ваше терпение, пока мы возвращаемся и работаем.

2. 27 июля 2026 г. в 14:56 UTCidentified

   Мы определили проблему, влияющую на поиск нагрузки, и инженеры активно работают над решением. Некоторые пользователи могут продолжать испытывать перебои, в то время как усилия по смягчению последствий и восстановлению продолжаются. Пожалуйста, продолжайте следить за обновлениями status.dat.com в режиме реального времени. Спасибо за ваше терпение, пока мы возвращаемся и работаем.

3. 27 июля 2026 г. в 18:53 UTCresolved

   Проблема, влияющая на поиск нагрузки, была решена, и службы снова работают нормально. Инженеры будут продолжать внимательно следить за обеспечением стабильности. Спасибо за ваше терпение, пока мы работали над восстановлением сервиса.

Автоматический перевод официального обновления инцидента.

1. 21 июля 2026 г. в 14:53 UTCinvestigating

   В настоящее время мы расследуем проблему, затрагивающую публикации загрузки. Некоторые клиенты могут испытывать задержку или не могут размещать нагрузки через DAT One Web или через их интеграцию с TMS. Наша инженерная команда активно работает над решением проблемы, и мы предоставим еще одно обновление, как только будет доступна дополнительная информация.

2. 21 июля 2026 г. в 16:57 UTCmonitoring

   Мы решили проблему с загрузкой и продолжаем следить за здоровьем наших систем.

3. 27 июля 2026 г. в 18:56 UTCresolved

   Проблема, затрагивающая размещение грузов, была решена, и службы снова работают нормально. Наша инженерная команда будет продолжать следить за состоянием системы, чтобы обеспечить постоянную стабильность. Спасибо за ваше терпение.

Автоматический перевод официального обновления инцидента.

1. 20 июля 2026 г. в 16:01 UTCinvestigating

   В настоящее время мы расследуем проблему, затрагивающую публикации загрузки. Некоторые клиенты могут испытывать задержку или не могут размещать нагрузки через DAT One Web или через их интеграцию с TMS. Наша инженерная команда активно работает над решением проблемы, и мы предоставим еще одно обновление, как только будет доступна дополнительная информация.

2. 20 июля 2026 г. в 17:05 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 10 июля 2026 г. в 13:06 UTCinvestigating

   We are currently investigating an issue affecting load postings. Some customers may experience a lag or be unable to post loads via DAT One Web or through their TMS integrations. Our engineering team is actively working to resolve the issue, and we will provide another update as soon as more information is available. We apologize for the inconvenience.

2. 10 июля 2026 г. в 14:13 UTCidentified

   Update: Identified Cause & Ongoing Investigation We have identified a potential cause for the load posting issues on DAT One Web and TMS. Our engineering team is currently investigating this lead and working on a resolution. We will provide another update as soon as we have more information. Thank you for your continued patience.

3. 10 июля 2026 г. в 15:44 UTCmonitoring

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

4. 11 июля 2026 г. в 02:33 UTCresolved

   This incident has been resolved.

1. 7 июля 2026 г. в 13:21 UTCinvestigating

   We are currently experiencing an issue affecting the posting, reposting, and copying of loads on the DAT One web platform. Our engineering team is actively investigating and working on a fix. We will provide another update as soon as more information is available. Workaround: If you have an active integration setup (such as a TMS or API connection), you can continue to post your loads through that channel in the meantime. We apologize for the inconvenience.

2. 8 июля 2026 г. в 14:04 UTCresolved

   This incident has been resolved.

1. 1 июля 2026 г. в 12:38 UTCinvestigating

   Identified: We are currently experiencing technical difficulties with the Multi-Shipments feature on the DAT One web platform for brokers being unable to create multi-shipments at this time. Current Action: The engineering team is fully engaged and working on a fix. Next Update: We will post our next status update as new information becomes available. Thank you for your patience while we work to restore full functionality.

2. 1 июля 2026 г. в 12:39 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 июля 2026 г. в 13:06 UTCidentified

   Users are currently unable to process broker multi-shipment uploads or utilize broker workgroups on DAT One (Web).

4. 1 июля 2026 г. в 14:05 UTCidentified

   Users are currently unable to process broker multi-shipment uploads or utilize broker workgroups on DAT One (Web). Current Action: The engineering team is fully engaged and working on a fix. Next Update: We will post our next status update as new information becomes available. Thank you for your patience while we work to restore full functionality.

5. 1 июля 2026 г. в 16:08 UTCmonitoring

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

6. 1 июля 2026 г. в 16:50 UTCresolved

   This incident has been resolved.

1. 24 июня 2026 г. в 14:18 UTCinvestigating

   We are currently experiencing a technical issue where integration is unable to import watchlists for carriers as well as being unable to update carrier insurance. Current Action: Our engineering team has been engaged and is actively working on a resolution. We sincerely apologize for the inconvenience and confusion this may cause. We will provide another update as soon as more information is available or a fix is deployed.

2. 25 июня 2026 г. в 13:56 UTCresolved

   This incident has been resolved.

1. 24 июня 2026 г. в 13:51 UTCinvestigating

   We are currently aware of a service disruption impacting users accessing the carrier load board and our teams are actively investigating the issue. Rest assured that our technical teams are working to identify the root cause and restore normal service as quickly as possible. Please Note: • This only affects carrier access to the load board.. • Tracking and app usage are not affected.. At this time, we do not have an estimated resolution time, but we will continue to provide updates as more information becomes available. We appreciate your patience and understanding while we work through this issue. If you have any additional questions or need assistance, please don't hesitate to reach out.

2. 24 июня 2026 г. в 15:04 UTCresolved

   This incident has been resolved.

1. 23 июня 2026 г. в 15:06 UTCinvestigating

   We are currently investigating a technical issue causing CarrierWatch to send incorrect automated emails that flag some carriers as having inactive authority. Customers may receive alerts stating a carrier's authority is inactive when that status is inaccurate. Our engineering team is actively working on a resolution. We sincerely apologize for the inconvenience and confusion this may cause. We will provide another update as soon as more information is available or a fix has been deployed.

2. 23 июня 2026 г. в 16:31 UTCidentified

   We have identified an issue where Carrierwatch was sending incorrect automated emails that flag some carriers as having inactive authority. Our engineering teams have identified the issue and disabled those alert e-mails. Some previously sent messages may still be queued on customer e-mail systems. We sincerely apologize for the inconvenience and confusion this may have caused.

3. 23 июня 2026 г. в 18:09 UTCmonitoring

   We identified an issue impacting CarrierWatch email notifications and temporarily suspended notifications while we implemented a fix. The fix has now been applied, and email notifications are working again. We will continue to monitor to ensure normal delivery

4. 1 июля 2026 г. в 16:07 UTCresolved

   This incident has been resolved.

1. 5 июня 2026 г. в 16:37 UTCinvestigating

   We are aware of an issue affecting Ratecast forecast projections on select lanes. Our team is actively investigating and working toward a full resolution. We will provide updates as our investigation progresses. We apologize for any inconvenience this may cause.

2. 8 июня 2026 г. в 15:58 UTCresolved

   This incident has been resolved.

1. 3 июня 2026 г. в 19:52 UTCinvestigating

   We are currently investigating reports of intermittent errors and accessibility issues affecting some DAT One users. Our team is actively working to identify the cause and restore full service. We will continue to provide updates as our investigation progresses. We apologize for the inconvenience.

2. 3 июня 2026 г. в 20:57 UTCidentified

   We have identified the cause of the issue affecting some DAT One users and our team is actively working on a resolution. Users may continue to experience intermittent errors while we implement a fix. We will provide updates as we make progress. We apologize for the inconvenience.

3. 3 июня 2026 г. в 21:00 UTCidentified

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

4. 3 июня 2026 г. в 21:11 UTCresolved

   The issue affecting DAT One has been resolved and services are operating normally. We apologize for any inconvenience this may have caused and thank you for your patience while our team worked to restore full service.

1. 6 мая 2026 г. в 03:39 UTCinvestigating

   We are currently experiencing an unexpected interruption of some DAT services. Engineers are working to restore service as soon as possible. We appreciate your business and sincerely apologize for the inconvenience.

2. 7 мая 2026 г. в 01:09 UTCresolved

   This incident has been resolved.

1. 28 апреля 2026 г. в 19:22 UTCidentified

   We're currently experiencing an unscheduled maintenance window that is impacting both broker and carrier ability to log in and interact with the Convoy Platform. Our team is actively working on a fix and this is our top priority right now. We'll send a follow-up as soon as the platform is fully restored. We apologize for any disruption to your operations and appreciate your patience. — The Convoy Team

2. 28 апреля 2026 г. в 20:35 UTCresolved

   The service disruption affecting the Convoy Platform has been resolved. Brokers and carriers should now be able to log in and interact with the platform as normal.

1. 15 апреля 2026 г. в 12:40 UTCinvestigating

   Posting via TMS is currently unavailable. Connectivity to CarrierWatch is impacted, and API rate calls are also affected. Some customers may be unable to post trucks or loads via their TMS or access CarrierWatch. We are actively working to resolve the issue and will provide an update as soon as possible. We apologize for the inconvenience and appreciate your patience.

2. 15 апреля 2026 г. в 14:27 UTCmonitoring

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

3. 15 апреля 2026 г. в 15:07 UTCresolved

   This incident has been resolved.

1. 14 апреля 2026 г. в 13:57 UTCinvestigating

   We are currently experiencing a service disruption affecting TMS postings and CarrierWatch logins. Some customers may be unable to post trucks or loads via their TMS. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as possible. Thank you for your patience.

2. 14 апреля 2026 г. в 14:48 UTCmonitoring

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

3. 14 апреля 2026 г. в 15:03 UTCresolved

   This incident has been resolved.

1. 13 апреля 2026 г. в 15:38 UTCinvestigating

   We are currently experiencing a service disruption affecting editing and positing shipments via DAT One web and TMS postings. Some customers may be unable to post loads via DAT One web and their TMS. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as possible. Please follow status.dat.com for updates.

2. 13 апреля 2026 г. в 16:01 UTCresolved

   This incident has been resolved.

1. 1 апреля 2026 г. в 13:38 UTCinvestigating

   We are currently experiencing a service disruption affecting TMS postings and CarrierWatch logins. Some customers may be unable to post trucks or loads via their TMS. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as possible. Thank you for your patience.

2. 1 апреля 2026 г. в 15:21 UTCmonitoring

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

3. 1 апреля 2026 г. в 16:09 UTCresolved

   This incident has been resolved.

1. 13 марта 2026 г. в 13:00 UTCinvestigating

   We are currently investigating an issue where RateView is not showing rates. Some customers may see missing or unavailable pricing in RateView, CarrierWatch, and rate displays within DAT One. Our engineering teams are working to restore normal rate visibility as quickly as possible. We will provide another update as soon as we have more information

2. 13 марта 2026 г. в 14:56 UTCmonitoring

   We recently experienced an issue where some customers saw missing or unavailable pricing in RateView, CarrierWatch, and rate displays within DAT One. Services have been restored and pricing information should now be available again. Our teams are closely monitoring the systems to ensure they remain stable. If you continue to experience issues, please contact DAT Support

3. 13 марта 2026 г. в 15:02 UTCmonitoring

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

4. 13 марта 2026 г. в 18:52 UTCresolved

   This incident has been resolved.

1. 3 марта 2026 г. в 02:42 UTCinvestigating

   Some users are unable to connect to Keypoint Anywhere. We are currently working on the issue.

2. 3 марта 2026 г. в 03:35 UTCidentified

   Users should now be able to connect to Keypoint Anywhere. Please try logging in and accessing your reports. If you experience any issues, contact the support team.

3. 3 марта 2026 г. в 04:05 UTCresolved

   This incident has been resolved.