NASCAR - Notice history

This incident has been resolved. This issue may have also caused some incorrect pit stop data, but going forward as latency is normal, we shouldn't see any issues with either system.

We have narrowed down the cause of the latency and are investigating a fix.

The data flow appeared normal for the NOAPS race. We are marking this issue as resolved, but will re-evaluate before the Cup race 07/05

No longer seeing duplicates. Will continue monitoring.

Engineers are continuing to troubleshoot the issue to identify a potential fix.

Engineers are continuing to troubleshoot the issue to identify a potential fix. Affected ERDP data includes timing data and potentially pit road data. Duplicate messages may be sent inconsistently until a fix can be implemented.

Engineers are working on a potential fix.

We are still investigating, we will post another update in around 45 minutes.

We still do not have a solution to the duplicate messages. We have been investigating consistently and will continue to look into this issue. As of right now, Pit Road data will also be marked as degraded since we are seeing duplicate pitroad messages as well.

As of 07/04 we are still investigating this and working on a solution/workaround

This is also likely to cause increased latency on ERDP and connected systems

We are still investigating this incident. Updates will be posted when we have them.

System has been switched back to main. Monitoring for the next few minutes then will resolve.

Switched services to a backup system. Loop data is now being sent. Working on a more permanent fix for the main system.

Streaming services are not receiving line crossing data. Currently investigating a fix.

Tracking fully lost on the #2, working on a fix now

Beginning to completely lose tracking of the #2 car. Cause is known and a fix is being worked on.

We implemented a fix and are currently monitoring the result. We will confirm and resolve once pit stop data is flowing for the NCTS race.

We implemented a fix and are currently monitoring the result. GPS is now stable.

We implemented a fix and are currently monitoring the result. Seems to have stabilized.

This issue is persisting after the restart. Will continue to investigate.