Resolved -
This incident has been resolved.
Apr 18, 11:14 PDT
Identified -
The issue has been identified and a fix is being implemented.
Apr 17, 07:30 PDT
Update -
We are still awaiting the February and March data from the FMCSA, which was originally expected to be published in early March.
Our team has reached back out to the FMCSA for clarification and is actively monitoring the situation. We will begin processing the data as soon as it becomes available and will provide another update once we have more information.
Apr 14, 10:07 PDT
Update -
We previously received corrected January data and have successfully updated RMIS and Saferwatch. However, we are still awaiting February's data from the FMCSA, which was expected to be published in early March.
Our team is actively monitoring the situation and will begin processing the new data as soon as it's available. We appreciate your patience and understanding. Thank you for your continued partnership.
Mar 18, 08:29 PDT
Update -
We are currently awaiting a corrected data set from the FMCSA and remain in active communication with them. Once the FMCSA publishes the updated data, we will begin our CSA calculation process and promptly update RMIS and Saferwatch. Thank you for your continued partnership.
Feb 25, 08:39 PST
Investigating -
We would like to inform you that the FMCSA's SMS update for January carrier measurements contained issues. As a result, we are currently unable to process the latest CSA scores and SMS measures. We are actively working with the FMCSA who expects to post an updated data set soon. Once we have the data from the FMCSA, we will begin our CSA calculation process so that we can publish the scores and measurements to RMIS and Saferwatch. We appreciate your understanding and patience during this time. Thank you for your continued partnership.
Feb 12, 14:13 PST