NASCAR Status - Incident history https://status.nascarracedata.com NASCAR Sun, 9 Aug 2026 22:16:01 +0000 Livestream site major outage Type: Incident Duration: 20 minutes Affected Components: Live Stream Aug 9, 22:16:01 GMT+0 - Investigating - We are currently investigating this incident. Most streams seem to be offline Aug 9, 22:36:02 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 20 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>22:16:01</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Most streams seem to be offline.</p> <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>22:36:02</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 9 Aug 2026 22:16:01 +0000 https://status.nascarracedata.com/incident/cmsmd3bxo0ewj0rrpfwk75m4i https://status.nascarracedata.com/incident/cmsmd3bxo0ewj0rrpfwk75m4i Missing telemetry data for #12 cup car Type: Incident Duration: 2 hours and 9 minutes Affected Components: Telemetry Aug 9, 21:01:30 GMT+0 - Investigating - We are currently investigating this incident. Aug 9, 21:09:07 GMT+0 - Identified - There is an issue with the ECU on the car and no data is being received at track, we will investigate, but this is likely to remain for the duration of the race. Aug 9, 23:10:03 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 9 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>21:01:30</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>21:09:07</var> GMT+0</small><br><strong>Identified</strong> - There is an issue with the ECU on the car and no data is being received at track, we will investigate, but this is likely to remain for the duration of the race..</p> <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>23:10:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 9 Aug 2026 21:01:30 +0000 https://status.nascarracedata.com/incident/cmsmafi5y0f1m0zrpimzpk937 https://status.nascarracedata.com/incident/cmsmafi5y0f1m0zrpimzpk937 Reports of duplicate heartbeat messages on erdp Type: Incident Duration: 1 day, 1 hour and 26 minutes Affected Components: Timing Data (Loop) Aug 8, 21:10:08 GMT+0 - Investigating - We are currently investigating this incident. Aug 9, 19:16:14 GMT+0 - Investigating - We will continue to monitor and investigate this during the cup race today, and we will alert if this affects any other systems downstream. Aug 9, 22:35:42 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 1 hour and 26 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>21:10:08</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>19:16:14</var> GMT+0</small><br><strong>Investigating</strong> - We will continue to monitor and investigate this during the cup race today, and we will alert if this affects any other systems downstream..</p> <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>22:35:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 8 Aug 2026 21:10:08 +0000 https://status.nascarracedata.com/incident/cmskvaqq003gb0rrpzj1r62i1 https://status.nascarracedata.com/incident/cmskvaqq003gb0rrpzj1r62i1 Degraded GPS on #22 cup car Type: Incident Duration: 1 hour and 46 minutes Affected Components: GPS Aug 8, 18:52:03 GMT+0 - Investigating - We are currently investigating this incident. Aug 8, 20:37:38 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 46 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>18:52:03</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>20:37:38</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 8 Aug 2026 18:52:03 +0000 https://status.nascarracedata.com/incident/cmskqd5ye0qgd1bn3eto92bzb https://status.nascarracedata.com/incident/cmskqd5ye0qgd1bn3eto92bzb Some in-car cams not showing live on livestream site Type: Incident Duration: 16 minutes Affected Components: Live Stream Aug 8, 18:36:41 GMT+0 - Investigating - We are currently investigating this incident. Aug 8, 18:52:57 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 16 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>18:36:41</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>18:52:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 8 Aug 2026 18:36:41 +0000 https://status.nascarracedata.com/incident/cmskptf1w02pt0zrp4et0yfw6 https://status.nascarracedata.com/incident/cmskptf1w02pt0zrp4et0yfw6 Degraded GPS on #1 cup car Type: Incident Duration: 2 hours and 20 minutes Affected Components: GPS Aug 8, 18:18:13 GMT+0 - Investigating - We are currently investigating this incident. Aug 8, 20:37:44 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 20 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>18:18:13</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>20:37:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 8 Aug 2026 18:18:13 +0000 https://status.nascarracedata.com/incident/cmskp5nt902r01arp3j0qaoy5 https://status.nascarracedata.com/incident/cmskp5nt902r01arp3j0qaoy5 #19 Cup Car Experiencing GPS Hits Type: Incident Duration: 2 hours and 32 minutes Affected Components: GPS Jul 5, 23:10:32 GMT+0 - Investigating - We are currently investigating this incident. The #19 is experiencing hits to GPS accuracy Jul 6, 01:42:14 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 32 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>23:10:32</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. The #19 is experiencing hits to GPS accuracy.</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>01:42:14</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 5 Jul 2026 23:10:32 +0000 https://status.nascarracedata.com/incident/cmr8emm6713in0kqfubfpkym3 https://status.nascarracedata.com/incident/cmr8emm6713in0kqfubfpkym3 Reports of high latency on timing data Type: Incident Duration: 1 hour and 20 minutes Affected Components: Timing Data (Loop) Jul 5, 23:40:20 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 5, 22:40:32 GMT+0 - Investigating - We are currently investigating this incident. Jul 5, 23:26:15 GMT+0 - Identified - We have narrowed down the cause of the latency and are investigating a fix. Jul 6, 00:00:37 GMT+0 - Resolved - 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. Type: Incident

Duration: 1 hour and 20 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>23:40:20</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>22:40:32</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>23:26:15</var> GMT+0</small><br><strong>Identified</strong> - We have narrowed down the cause of the latency and are investigating a fix..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>00:00:37</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Sun, 5 Jul 2026 22:40:32 +0000 https://status.nascarracedata.com/incident/cmr8dk13s10nn0kmj16dglt0m https://status.nascarracedata.com/incident/cmr8dk13s10nn0kmj16dglt0m Intermittent GPS loss for the #88 and #9 NOAPS Type: Incident Duration: 2 hours and 45 minutes Affected Components: GPS Jul 5, 02:11:07 GMT+0 - Investigating - We are currently investigating this incident. Both cars are having trouble holding GPS signal. Jul 5, 04:55:39 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 45 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>02:11:07</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Both cars are having trouble holding GPS signal. .</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>04:55:39</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 5 Jul 2026 02:11:07 +0000 https://status.nascarracedata.com/incident/cmr75n0dz0m0s1aqfac78zpfm https://status.nascarracedata.com/incident/cmr75n0dz0m0s1aqfac78zpfm Reports of high volume of heartbeat messages on ERDP Type: Incident Duration: 1 day, 6 hours and 46 minutes Affected Components: Timing Data (Loop), Pit Road Data Jul 4, 16:43:41 GMT+0 - Investigating - As of 07/04 we are still investigating this and working on a solution/workaround Jul 3, 22:09:28 GMT+0 - Investigating - We are currently investigating this incident. Jul 3, 22:11:12 GMT+0 - Investigating - This is also likely to cause increased latency on ERDP and connected systems Jul 4, 19:34:21 GMT+0 - Identified - 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. Jul 4, 20:36:27 GMT+0 - Investigating - We are still investigating, we will post another update in around 45 minutes. Jul 4, 21:31:41 GMT+0 - Identified - Engineers are working on a potential fix. Jul 4, 22:30:08 GMT+0 - Investigating - 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. Jul 5, 00:42:04 GMT+0 - Investigating - Engineers are continuing to troubleshoot the issue to identify a potential fix. Jul 5, 01:19:58 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 5, 02:26:08 GMT+0 - Monitoring - No longer seeing duplicates. Will continue monitoring. Jul 5, 04:55:30 GMT+0 - Resolved - 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 Type: Incident

Duration: 1 day, 6 hours and 46 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>16:43:41</var> GMT+0</small><br><strong>Investigating</strong> - As of 07/04 we are still investigating this and working on a solution/workaround.</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>22:09:28</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>22:11:12</var> GMT+0</small><br><strong>Investigating</strong> - This is also likely to cause increased latency on ERDP and connected systems.</p> <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>19:34:21</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>20:36:27</var> GMT+0</small><br><strong>Investigating</strong> - We are still investigating, we will post another update in around 45 minutes..</p> <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>21:31:41</var> GMT+0</small><br><strong>Identified</strong> - Engineers are working on a potential fix. .</p> <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>22:30:08</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>00:42:04</var> GMT+0</small><br><strong>Investigating</strong> - Engineers are continuing to troubleshoot the issue to identify a potential fix..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>01:19:58</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>02:26:08</var> GMT+0</small><br><strong>Monitoring</strong> - No longer seeing duplicates. Will continue monitoring..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>04:55:30</var> GMT+0</small><br><strong>Resolved</strong> - 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.</p> ]]> Fri, 3 Jul 2026 22:09:28 +0000 https://status.nascarracedata.com/incident/cmr5hke5v0fm30rmj5fabhtyh https://status.nascarracedata.com/incident/cmr5hke5v0fm30rmj5fabhtyh Cup Car #45 Experiencing degraded GPS accuracy Type: Incident Duration: 2 hours and 38 minutes Affected Components: GPS Jun 28, 22:36:26 GMT+0 - Resolved - This incident has been resolved. Jun 28, 19:58:18 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 2 hours and 38 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>22:36:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>19:58:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Sun, 28 Jun 2026 19:58:18 +0000 https://status.nascarracedata.com/incident/cmqy7ofq90jqa2opejgkeib35 https://status.nascarracedata.com/incident/cmqy7ofq90jqa2opejgkeib35 Issue with connecting to NATS Cloud Endpoint Type: Incident Duration: 2 hours and 16 minutes Affected Components: GPS, Timing Data (Loop), Pit Road Data, Telemetry Jun 28, 19:31:23 GMT+0 - Investigating - We are currently investigating this incident. Jun 28, 20:17:24 GMT+0 - Investigating - We are still investigating this incident. Updates will be posted when we have them. Jun 28, 21:26:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 28, 21:47:17 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 16 minutes

Affected Components: , , ,

<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>19:31:23</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>20:17:24</var> GMT+0</small><br><strong>Investigating</strong> - We are still investigating this incident. Updates will be posted when we have them..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>21:26:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>21:47:17</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 28 Jun 2026 19:31:23 +0000 https://status.nascarracedata.com/incident/cmqy6ptq301r81atj7z4opldv https://status.nascarracedata.com/incident/cmqy6ptq301r81atj7z4opldv Reports of Missing Timing Data Type: Incident Duration: 3 hours and 8 minutes Affected Components: Timing Data (Loop) Jun 27, 18:43:52 GMT+0 - Monitoring - System has been switched back to main. Monitoring for the next few minutes then will resolve. Jun 27, 21:13:16 GMT+0 - Resolved - This incident has been resolved. Jun 27, 18:30:04 GMT+0 - Monitoring - Switched services to a backup system. Loop data is now being sent. Working on a more permanent fix for the main system. Jun 27, 18:04:56 GMT+0 - Investigating - We are currently investigating this incident. Jun 27, 18:13:22 GMT+0 - Identified - Streaming services are not receiving line crossing data. Currently investigating a fix. Type: Incident

Duration: 3 hours and 8 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>18:43:52</var> GMT+0</small><br><strong>Monitoring</strong> - System has been switched back to main. Monitoring for the next few minutes then will resolve..</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>21:13:16</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>18:30:04</var> GMT+0</small><br><strong>Monitoring</strong> - Switched services to a backup system. Loop data is now being sent. Working on a more permanent fix for the main system..</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>18:04:56</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>18:13:22</var> GMT+0</small><br><strong>Identified</strong> - Streaming services are not receiving line crossing data. Currently investigating a fix..</p> ]]> Sat, 27 Jun 2026 18:04:56 +0000 https://status.nascarracedata.com/incident/cmqwo6siw04qi2prxb835qqg2 https://status.nascarracedata.com/incident/cmqwo6siw04qi2prxb835qqg2 #2 and #28 NOAPS cars experiencing degraded GPS accuracy Type: Incident Duration: 4 hours and 11 minutes Affected Components: GPS Jun 20, 21:39:06 GMT+0 - Investigating - We are currently investigating this incident. Jun 20, 21:38:07 GMT+0 - Investigating - We are currently investigating this incident. Jun 20, 22:52:38 GMT+0 - Identified - Beginning to completely lose tracking of the #2 car. Cause is known and a fix is being worked on. Jun 21, 01:26:44 GMT+0 - Identified - Tracking fully lost on the #2, working on a fix now Jun 21, 01:49:26 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 hours and 11 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>21:39:06</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>21:38:07</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>22:52:38</var> GMT+0</small><br><strong>Identified</strong> - Beginning to completely lose tracking of the #2 car. Cause is known and a fix is being worked on..</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>01:26:44</var> GMT+0</small><br><strong>Identified</strong> - Tracking fully lost on the #2, working on a fix now.</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>01:49:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 20 Jun 2026 21:38:07 +0000 https://status.nascarracedata.com/incident/cmqmvq004042r2jq8j0ot8280 https://status.nascarracedata.com/incident/cmqmvq004042r2jq8j0ot8280 No PRO data available (PRO Data may be unavailable to start NCTS Race) Type: Incident Duration: 2 hours and 35 minutes Affected Components: Pit Road Data, Pro Penalty Jun 19, 23:43:21 GMT+0 - Resolved - This incident has been resolved. Jun 19, 21:08:42 GMT+0 - Investigating - PRO has been experiencing configuration issues which affect pit road data availability and may not be available to begin the NCTS Race. We are working with the vendor to resolve the issue as quickly as possible Jun 19, 21:48:27 GMT+0 - Monitoring - 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. Type: Incident

Duration: 2 hours and 35 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>23:43:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>21:08:42</var> GMT+0</small><br><strong>Investigating</strong> - PRO has been experiencing configuration issues which affect pit road data availability and may not be available to begin the NCTS Race. We are working with the vendor to resolve the issue as quickly as possible.</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>21:48:27</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> ]]> Fri, 19 Jun 2026 21:08:42 +0000 https://status.nascarracedata.com/incident/cmqlf8bmd00ls2oqq4r6rb4ah https://status.nascarracedata.com/incident/cmqlf8bmd00ls2oqq4r6rb4ah No GPS Vehicle Location Data is expected for all Friday events Type: Incident Duration: 1 day, 8 hours and 45 minutes Affected Components: GPS, Team Analytics - Live Jun 19, 16:49:25 GMT+0 - Monitoring - GPS data and TA are operating as expected across most of the course with localized degradation in turns 7-12\. SMT is working with onsite frequency coordination to isolate and resolve the issue. Jun 19, 23:46:08 GMT+0 - Monitoring - Turns 7-12 still occasionally seeing degraded values, but operating as expected for most of the course. Jun 20, 17:19:58 GMT+0 - Monitoring - Same status today so far, still experiencing some tracking issues in that same area of the track by turns 7-12\. We're working on a fix that we hope to implement before the race this afternoon. Jun 19, 12:45:16 GMT+0 - Investigating - SMT is working to resolve, but root cause is unknown at this time. Jun 19, 14:18:53 GMT+0 - Identified - SMT is working to resolve, but Team Analytics will not be operational Jun 20, 21:30:31 GMT+0 - Resolved - As far as we can tell visually, the changes made today pre-race have resolved the GPS tracking issues in turns 7-12\. We will look at the post-race analysis and send out another update tomorrow before the NCS race if needed. Jun 19, 15:59:30 GMT+0 - Identified - We are receiving GPS data pre-practice for Trucks. We may receive data once the cars are on track, but we expect it to be degraded and inconsistent. Type: Incident

Duration: 1 day, 8 hours and 45 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>16:49:25</var> GMT+0</small><br><strong>Monitoring</strong> - GPS data and TA are operating as expected across most of the course with localized degradation in turns 7-12\. SMT is working with onsite frequency coordination to isolate and resolve the issue..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>23:46:08</var> GMT+0</small><br><strong>Monitoring</strong> - Turns 7-12 still occasionally seeing degraded values, but operating as expected for most of the course..</p> <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>17:19:58</var> GMT+0</small><br><strong>Monitoring</strong> - Same status today so far, still experiencing some tracking issues in that same area of the track by turns 7-12\. We're working on a fix that we hope to implement before the race this afternoon..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>12:45:16</var> GMT+0</small><br><strong>Investigating</strong> - SMT is working to resolve, but root cause is unknown at this time..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>14:18:53</var> GMT+0</small><br><strong>Identified</strong> - SMT is working to resolve, but Team Analytics will not be operational.</p> <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>21:30:31</var> GMT+0</small><br><strong>Resolved</strong> - As far as we can tell visually, the changes made today pre-race have resolved the GPS tracking issues in turns 7-12\. We will look at the post-race analysis and send out another update tomorrow before the NCS race if needed..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>15:59:30</var> GMT+0</small><br><strong>Identified</strong> - We are receiving GPS data pre-practice for Trucks. We may receive data once the cars are on track, but we expect it to be degraded and inconsistent..</p> ]]> Fri, 19 Jun 2026 12:45:16 +0000 https://status.nascarracedata.com/incident/cmqkx8w94008n2inph7s2kypk https://status.nascarracedata.com/incident/cmqkx8w94008n2inph7s2kypk #7 CUP car in-car camera outage Type: Incident Duration: 1 hour and 26 minutes Affected Components: Live Stream Jun 14, 18:54:45 GMT+0 - Investigating - #7 has lost camera power. We are currently investigating this incident. Likely won't have the in-car camera feed on the livestream site. Jun 14, 20:20:44 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 26 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>18:54:45</var> GMT+0</small><br><strong>Investigating</strong> - #7 has lost camera power. We are currently investigating this incident. Likely won't have the in-car camera feed on the livestream site..</p> <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>20:20:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 14 Jun 2026 18:54:45 +0000 https://status.nascarracedata.com/incident/cmqe58swu02d22io56cr4l9ux https://status.nascarracedata.com/incident/cmqe58swu02d22io56cr4l9ux #77 CUP car experiencing periodic degraded GPS accuracy Type: Incident Duration: 1 hour and 39 minutes Affected Components: GPS Jun 14, 18:41:44 GMT+0 - Investigating - We are currently investigating this incident. Jun 14, 20:20:53 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 39 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>18:41:44</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>20:20:53</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 14 Jun 2026 18:41:44 +0000 https://status.nascarracedata.com/incident/cmqe4s1ox01zi2io57qv748xu https://status.nascarracedata.com/incident/cmqe4s1ox01zi2io57qv748xu #11 CUP car experiencing degraded GPS accuracy Type: Incident Duration: 1 hour and 48 minutes Affected Components: GPS Jun 14, 18:32:56 GMT+0 - Investigating - We are currently investigating this incident. Jun 14, 20:21:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 48 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>18:32:56</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>20:21:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 14 Jun 2026 18:32:56 +0000 https://status.nascarracedata.com/incident/cmqe4gqez017h2insiqtv7v61 https://status.nascarracedata.com/incident/cmqe4gqez017h2insiqtv7v61 Missing ERDP data Type: Incident Duration: 55 minutes Affected Components: GPS, Timing Data (Loop), Pit Road Data, Telemetry Jun 14, 17:37:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 14, 17:59:29 GMT+0 - Resolved - This incident has been resolved. Jun 14, 17:04:52 GMT+0 - Investigating - We are currently investigating this incident. Jun 14, 17:32:07 GMT+0 - Investigating - We are seeing some data recover on the cloud endpoint. Still investigating and working on this. Type: Incident

Duration: 55 minutes

Affected Components: , , ,

<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>17:37:51</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>17:59:29</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>17:04:52</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>17:32:07</var> GMT+0</small><br><strong>Investigating</strong> - We are seeing some data recover on the cloud endpoint. Still investigating and working on this..</p> ]]> Sun, 14 Jun 2026 17:04:52 +0000 https://status.nascarracedata.com/incident/cmqe1bhby000pqr9ygel110lm https://status.nascarracedata.com/incident/cmqe1bhby000pqr9ygel110lm GPS tracking issues along the frontstretch Type: Incident Duration: 1 hour and 2 minutes Affected Components: GPS Jun 13, 22:00:59 GMT+0 - Identified - We are continuing to work on a fix for this incident. May see periodic short pauses in data as we work to resolve this issue. Jun 13, 23:03:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>22:00:59</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. May see periodic short pauses in data as we work to resolve this issue..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>23:03:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 13 Jun 2026 22:00:59 +0000 https://status.nascarracedata.com/incident/cmqcwgfbi04gnnp5ga6jen7sv https://status.nascarracedata.com/incident/cmqcwgfbi04gnnp5ga6jen7sv #35 NOAPS car experiencing degraded GPS Type: Incident Duration: 2 hours and 24 minutes Affected Components: GPS Jun 13, 23:03:08 GMT+0 - Resolved - This incident has been resolved. Jun 13, 20:39:08 GMT+0 - Investigating - We are currently investigating this incident. Not a total loss of data, but degraded location accuracy. Type: Incident

Duration: 2 hours and 24 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>23:03:08</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>20:39:08</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Not a total loss of data, but degraded location accuracy..</p> ]]> Sat, 13 Jun 2026 20:39:08 +0000 https://status.nascarracedata.com/incident/cmqctj6d0021fpam49lzna0tj https://status.nascarracedata.com/incident/cmqctj6d0021fpam49lzna0tj Lost GPS NOAPS #26 Type: Incident Duration: 5 minutes Affected Components: GPS Jun 13, 14:44:16 GMT+0 - Investigating - We are currently investigating this incident. We have lost the connection to the NOAPS #26 car. Jun 13, 14:49:09 GMT+0 - Resolved - This incident has been resolved. Connection restored. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>14:44:16</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. We have lost the connection to the NOAPS #26 car..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>14:49:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Connection restored..</p> ]]> Sat, 13 Jun 2026 14:44:16 +0000 https://status.nascarracedata.com/incident/cmqcguthw03hmqnmiwb88210n https://status.nascarracedata.com/incident/cmqcguthw03hmqnmiwb88210n GPS Latency - #11 Car Type: Incident Duration: 23 minutes Affected Components: GPS Jun 7, 22:49:18 GMT+0 - Investigating - We are currently experiencing GPS location latency on the #11 car. Jun 7, 23:12:21 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 23 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>22:49:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently experiencing GPS location latency on the #11 car..</p> <p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>23:12:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 7 Jun 2026 22:49:18 +0000 https://status.nascarracedata.com/incident/cmq4djgr904ifp8qbzg3xibcd https://status.nascarracedata.com/incident/cmq4djgr904ifp8qbzg3xibcd Telemetry Data - #5 Car Type: Incident Duration: 1 hour and 2 minutes Affected Components: Live Stream, Telemetry Jun 7, 22:10:28 GMT+0 - Identified - The 5 car has lost telemetry data and in-car video for the remainder of the race due to the incident on lap 147. Jun 7, 23:12:02 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>22:10:28</var> GMT+0</small><br><strong>Identified</strong> - The 5 car has lost telemetry data and in-car video for the remainder of the race due to the incident on lap 147..</p> <p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>23:12:02</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 7 Jun 2026 22:10:28 +0000 https://status.nascarracedata.com/incident/cmq4c5iw10455p8r0dkv2flxz https://status.nascarracedata.com/incident/cmq4c5iw10455p8r0dkv2flxz Telemetry/ECU data change this week (Dover/All-Star) Type: Maintenance Duration: 3 days, 6 hours and 33 minutes Affected Components: Telemetry May 14, 15:00:01 GMT+0 - Identified - Maintenance is now in progress May 14, 15:00:00 GMT+0 - Identified - **Telemetry/ECU data change this week:** With the new ECU, changes were made to the throttle data in the CANBus message. We have tested to confirm consistency with data formatting from ERDP, but Throttle data may be inconsistent or degraded for NCS practice on Friday. May 17, 21:32:40 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 3 days, 6 hours and 33 minutes

Affected Components:

<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - **Telemetry/ECU data change this week:** With the new ECU, changes were made to the throttle data in the CANBus message. We have tested to confirm consistency with data formatting from ERDP, but Throttle data may be inconsistent or degraded for NCS practice on Friday..</p> <p><small>May <var data-var='date'> 17</var>, <var data-var='time'>21:32:40</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 14 May 2026 15:00:00 +0000 https://status.nascarracedata.com/maintenance/cmp5m83bi01rfpblwxcy19jc5 https://status.nascarracedata.com/maintenance/cmp5m83bi01rfpblwxcy19jc5 GPS Datapoint Expanding Decimal Places Type: Maintenance Duration: 7 days, 2 hours and 41 minutes Affected Components: GPS Apr 3, 15:41:04 GMT+0 - Completed - Maintenance has completed successfully. Mar 27, 13:00:00 GMT+0 - Identified - In the GPS Location message in ERDP, the lap\_frac field will increase to include 6 decimal places this weekend. Type: Maintenance

Duration: 7 days, 2 hours and 41 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>15:41:04</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - In the GPS Location message in ERDP, the lap\_frac field will increase to include 6 decimal places this weekend..</p> ]]> Fri, 27 Mar 2026 13:00:00 +0000 https://status.nascarracedata.com/maintenance/cmn9bnd7g01ay12reyhvh8zr6 https://status.nascarracedata.com/maintenance/cmn9bnd7g01ay12reyhvh8zr6 Telemetry message timestamp update Type: Maintenance Duration: 9 days, 8 hours and 24 minutes Affected Components: Telemetry Nov 3, 14:00:00 GMT+0 - Identified - Telemetry message timestamps will be updated to use microseconds (previously milliseconds) for the 2026 season. Feb 10, 22:23:44 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 9 days, 8 hours and 24 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - Telemetry message timestamps will be updated to use microseconds (previously milliseconds) for the 2026 season. .</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>22:23:44</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 3 Nov 2025 14:00:00 +0000 https://status.nascarracedata.com/maintenance/cmhjh9tdk00jmnnzpvg9f7t75 https://status.nascarracedata.com/maintenance/cmhjh9tdk00jmnnzpvg9f7t75 Vector GPS Documentation & Update Type: Maintenance Duration: 3 days Affected Components: , Telemetry, Pit Road Data, Timing Data (Loop), Event Racing Data Platform (ERDP) - Production → Sep 30, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 30, 18:00:00 GMT+0 - Identified - The vector GPS documentation page has been added to the doc website under the developer guide -> GPS tab. For any subscribers accessing this data during the 2024 season, there are no planned changes to the message schemas. This data is set to be added to the ERDP feed for the 2026 season at Bowman Gray. We will provide updates with opportunities to replay this data from the 2024 season soon. Sep 30, 17:49:29 GMT+0 - Identified - For anyone unfamiliar with the documentation website here is a link: <https://docs.nextgen.nascarracedata.com/DeveloperGuide/GPS/> Oct 3, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 days

Affected Components: , , ,

<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - The vector GPS documentation page has been added to the doc website under the developer guide -> GPS tab. For any subscribers accessing this data during the 2024 season, there are no planned changes to the message schemas. This data is set to be added to the ERDP feed for the 2026 season at Bowman Gray. We will provide updates with opportunities to replay this data from the 2024 season soon. .</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>17:49:29</var> GMT+0</small><br><strong>Identified</strong> - For anyone unfamiliar with the documentation website here is a link: <https://docs.nextgen.nascarracedata.com/DeveloperGuide/GPS/>.</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 30 Sep 2025 18:00:00 +0000 https://status.nascarracedata.com/maintenance/cmg6up3px014kfnyy0w2nlilo https://status.nascarracedata.com/maintenance/cmg6up3px014kfnyy0w2nlilo Pit stop details message update Type: Maintenance Duration: 8 hours Affected Components: Pit Road Data Jun 27, 13:00:00 GMT+0 - Identified - The following fields will be added to the pit stop details message on the staging environment for the the following 2 weekends and will be added to the production pit stop details message at Sonoma. isDeleted (bool) - indicates the infraction associated with the pitstop was deleted For more information please visit the documentation site: [https://docs.nextgen.nascarracedata.com/DeveloperGuide/Staging](https://docs.nextgen.nascarracedata.com/DeveloperGuide/Staging/#last-updated) Jun 27, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Jun 27, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 8 hours

Affected Components:

<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - The following fields will be added to the pit stop details message on the staging environment for the the following 2 weekends and will be added to the production pit stop details message at Sonoma. isDeleted (bool) - indicates the infraction associated with the pitstop was deleted For more information please visit the documentation site: [https://docs.nextgen.nascarracedata.com/DeveloperGuide/Staging](https://docs.nextgen.nascarracedata.com/DeveloperGuide/Staging/#last-updated).</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Fri, 27 Jun 2025 13:00:00 +0000 https://status.nascarracedata.com/maintenance/cmc9cgtfd001x7ij1g0mglz1m https://status.nascarracedata.com/maintenance/cmc9cgtfd001x7ij1g0mglz1m Pit stop details message update Type: Maintenance Duration: 8 hours Affected Components: Pit Road Data May 16, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully May 16, 12:00:01 GMT+0 - Identified - Maintenance is now in progress May 16, 12:00:00 GMT+0 - Identified - Pit stop details message updates: the following fields have been added to the pit stop details message at SRCc37a1284.DPef57a812 starting at the all star race 5/16 \- driverTime - in seconds \- leftTime - in seconds \- rightTime - in seconds \- jackTime - in seconds \- crewTime - in seconds \- carStopToJack - in seconds \- jackToCarGoes - in seconds \- tires - the number of tires changed \- stopComplete - the stop has been reviewed by an official \* fields in the message can still change after the stop has been marked as stopComplete Documentaion is available at: <https://docs.nextgen.nascarracedata.com/DeveloperGuide/Pit%20Stop%20Details/> Type: Maintenance

Duration: 8 hours

Affected Components:

<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> - Pit stop details message updates: the following fields have been added to the pit stop details message at SRCc37a1284.DPef57a812 starting at the all star race 5/16 \- driverTime - in seconds \- leftTime - in seconds \- rightTime - in seconds \- jackTime - in seconds \- crewTime - in seconds \- carStopToJack - in seconds \- jackToCarGoes - in seconds \- tires - the number of tires changed \- stopComplete - the stop has been reviewed by an official \* fields in the message can still change after the stop has been marked as stopComplete Documentaion is available at: <https://docs.nextgen.nascarracedata.com/DeveloperGuide/Pit%20Stop%20Details/>.</p> ]]> Fri, 16 May 2025 12:00:00 +0000 https://status.nascarracedata.com/maintenance/cmapfcnuu002cpsg84rjruqhq https://status.nascarracedata.com/maintenance/cmapfcnuu002cpsg84rjruqhq