Dat Freight undefined Analytics の障害履歴

1. 2026年9月3日 22:07 UTCmonitoring

   現在、DATサービスに影響を及ぼす第三者プロバイダの1つに問題があります。 引き続き、当社の提供者と連携し、更新を短時間で行います.

2. 2026年9月3日 22:13 UTCmonitoring

   今後の問題がないか引き続き監視しています。

3. 2026年9月3日 22:39 UTCmonitoring

   弊社では、第3回パーティプロバイダの復旧を予定しておりますが、今後もプラットフォーム全体でサービスの健全性を監視してまいります.

4. 2026年9月3日 23:52 UTCresolved

   当社のエンジニアリングチームは、プラットフォームの健全性を検証し、問題が第三者のプロバイダと解決されることを確認します.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月27日 14:02 UTCinvestigating

   DAT One では、現在、一部のユーザーがロードを投稿または検索できないことを認識しています。 状況:技術者は積極的に問題を調査し、解決しています。 次の手順: リアルタイムの進捗状況の更新については、status.dat.comを監視するか、 すぐに確認してください。 私たちは物事をバックアップし、実行中にあなたの忍耐をありがとう.

2. 2026年7月27日 14:56 UTCidentified

   負荷検索に影響を及ぼす問題を特定し、技術者は解決に積極的に取り組んでいます。 一部のユーザーは、緩和と回復の努力が進んでいる間、中断を経験し続けることがあります。 リアルタイムの更新については、status.dat.comを引き続き監視してください。 私たちは物事をバックアップし、実行中にあなたの忍耐をありがとう.

3. 2026年7月27日 18:53 UTCresolved

   負荷検索に影響する問題は解決され、サービスは正常に動作しています。 エンジニアは、安定性を確保するために密接に監視します。 誠に有難うございます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月21日 14:53 UTCinvestigating

   現在、負荷投稿に影響を及ぼす問題について調査しています。 一部の顧客は、DAT One Web または TMS の統合を介してロードを投稿できない、または遅延が発生することがあります。 当社のエンジニアリングチームは、問題の解決に積極的に取り組んでおり、より多くの情報が利用可能になったらただちに別のアップデートを提供します.

2. 2026年7月21日 16:57 UTCmonitoring

   ロード投稿の問題点を解決し、システムの健全性を監視しています.

3. 2026年7月27日 18:56 UTCresolved

   負荷投稿に影響を及ぼす問題は解決され、サービスは通常再び動作します。 当社のエンジニアリングチームは、継続的な安定性を確保するために、システムを健康に監視し続けます。 ありがとうございます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月20日 16:01 UTCinvestigating

   現在、負荷投稿に影響を及ぼす問題について調査しています。 一部の顧客は、DAT One Web または TMS の統合を介してロードを投稿できない、または遅延が発生することがあります。 当社のエンジニアリングチームは、問題の解決に積極的に取り組んでおり、より多くの情報が利用可能になったらただちに別のアップデートを提供します.

2. 2026年7月20日 17:05 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

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

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

4. 2026年7月11日 2:33 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 2026年7月1日 13:06 UTCidentified

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

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

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

6. 2026年7月1日 16:50 UTCresolved

   This incident has been resolved.

1. 2026年6月24日 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. 2026年6月25日 13:56 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 2026年6月23日 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. 2026年6月23日 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. 2026年6月23日 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. 2026年7月1日 16:07 UTCresolved

   This incident has been resolved.

1. 2026年6月5日 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. 2026年6月8日 15:58 UTCresolved

   This incident has been resolved.

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

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

4. 2026年6月3日 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. 2026年5月6日 3: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. 2026年5月7日 1:09 UTCresolved

   This incident has been resolved.

1. 2026年4月28日 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. 2026年4月28日 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. 2026年4月15日 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. 2026年4月15日 14:27 UTCmonitoring

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

3. 2026年4月15日 15:07 UTCresolved

   This incident has been resolved.

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

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

3. 2026年4月14日 15:03 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 2026年4月1日 16:09 UTCresolved

   This incident has been resolved.

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

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

4. 2026年3月13日 18:52 UTCresolved

   This incident has been resolved.

1. 2026年3月3日 2:42 UTCinvestigating

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

2. 2026年3月3日 3: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. 2026年3月3日 4:05 UTCresolved

   This incident has been resolved.