Dat Freight undefined Analytics 中断历史

1. 2026年9月3日 UTC 22:07monitoring

   目前,我们的一个第三方供应商正在影响DAT服务。 我们正在继续与我们的提供者合作,不久将提供最新情况.

2. 2026年9月3日 UTC 22:13monitoring

   我们正在继续监测任何其他问题.

3. 2026年9月3日 UTC 22:39monitoring

   我们正开始从我们的第三党供应商那里看到一些恢复,但我们继续在整个平台上监测服务健康状况.

4. 2026年9月3日 UTC 23:52resolved

   我们的工程团队已经验证了平台健康,确认这个问题已经与我们的第三方供应商解决了.

自动翻译自官方事件更新。

1. 2026年7月27日 UTC 14:02investigating

   我们知道有些用户现在无法在DAT One中发布或搜索负载. 现状:工程师积极调查并解决问题. 下个步骤:请尽快检查或监控状态. dat.com实时更新进度. 感谢你的耐心 在我们恢复和运行的时候.

2. 2026年7月27日 UTC 14:56identified

   我们已查明影响负荷搜索的问题,工程师正在积极研究一项解决办法。 有些用户在减缓和恢复工作进行期间可能继续遭受中断。 请继续监控状态. dat.com实时更新. 感谢你的耐心 在我们恢复和运行的时候.

3. 2026年7月27日 UTC 18:53resolved

   影响负荷搜索的问题已经解决,服务也正常运行. 工程师将继续密切监测,以确保稳定。 谢谢你在努力恢复服务时的耐心.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 14:53investigating

   我们正在调查一个影响载货量的问题。 一些客户可能遭遇滞后,或无法通过DAT One Web或通过他们的TMS集成发布载荷. 我们的工程组正在积极努力解决这一问题,一旦获得更多信息,我们将提供另一个最新情况.

2. 2026年7月21日 UTC 16:57monitoring

   我们已通过载荷公布方式解决这一问题,并正在继续监测我们系统的健康情况.

3. 2026年7月27日 UTC 18:56resolved

   影响载荷张贴的问题已经解决,服务也正常运行. 我们的工程组将继续监测系统的健康,以确保持续稳定。 谢谢你的耐心.

自动翻译自官方事件更新。

1. 2026年7月20日 UTC 16:01investigating

   我们正在调查一个影响载货量的问题。 一些客户可能遭遇滞后,或无法通过DAT One Web或通过他们的TMS集成发布载荷. 我们的工程组正在积极努力解决这一问题,一旦获得更多信息,我们将提供另一个最新情况.

2. 2026年7月20日 UTC 17:05resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月10日 UTC 13:06investigating

   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. 2026年7月10日 UTC 14:13identified

   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. 2026年7月10日 UTC 15:44monitoring

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

4. 2026年7月11日 UTC 02:33resolved

   This incident has been resolved.

1. 2026年7月7日 UTC 13:21investigating

   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. 2026年7月8日 UTC 14:04resolved

   This incident has been resolved.

1. 2026年7月1日 UTC 12:38investigating

   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. 2026年7月1日 UTC 12:39investigating

   We are continuing to investigate this issue.

3. 2026年7月1日 UTC 13:06identified

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

4. 2026年7月1日 UTC 14:05identified

   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. 2026年7月1日 UTC 16:08monitoring

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

6. 2026年7月1日 UTC 16:50resolved

   This incident has been resolved.

1. 2026年6月24日 UTC 14:18investigating

   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. 2026年6月25日 UTC 13:56resolved

   This incident has been resolved.

1. 2026年6月24日 UTC 13:51investigating

   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. 2026年6月24日 UTC 15:04resolved

   This incident has been resolved.

1. 2026年6月23日 UTC 15:06investigating

   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. 2026年6月23日 UTC 16:31identified

   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. 2026年6月23日 UTC 18:09monitoring

   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. 2026年7月1日 UTC 16:07resolved

   This incident has been resolved.

1. 2026年6月5日 UTC 16:37investigating

   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. 2026年6月8日 UTC 15:58resolved

   This incident has been resolved.

1. 2026年6月3日 UTC 19:52investigating

   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. 2026年6月3日 UTC 20:57identified

   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. 2026年6月3日 UTC 21:00identified

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

4. 2026年6月3日 UTC 21:11resolved

   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. 2026年5月6日 UTC 03:39investigating

   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. 2026年5月7日 UTC 01:09resolved

   This incident has been resolved.

1. 2026年4月28日 UTC 19:22identified

   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. 2026年4月28日 UTC 20:35resolved

   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. 2026年4月15日 UTC 12:40investigating

   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. 2026年4月15日 UTC 14:27monitoring

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

3. 2026年4月15日 UTC 15:07resolved

   This incident has been resolved.

1. 2026年4月14日 UTC 13:57investigating

   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. 2026年4月14日 UTC 14:48monitoring

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

3. 2026年4月14日 UTC 15:03resolved

   This incident has been resolved.

1. 2026年4月13日 UTC 15:38investigating

   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. 2026年4月13日 UTC 16:01resolved

   This incident has been resolved.

1. 2026年4月1日 UTC 13:38investigating

   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. 2026年4月1日 UTC 15:21monitoring

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

3. 2026年4月1日 UTC 16:09resolved

   This incident has been resolved.

1. 2026年3月13日 UTC 13:00investigating

   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. 2026年3月13日 UTC 14:56monitoring

   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. 2026年3月13日 UTC 15:02monitoring

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

4. 2026年3月13日 UTC 18:52resolved

   This incident has been resolved.

1. 2026年3月3日 UTC 02:42investigating

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

2. 2026年3月3日 UTC 03:35identified

   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. 2026年3月3日 UTC 04:05resolved

   This incident has been resolved.