Duration: 18 hours and 12 minutes

Affected Components:

Oct 12, 20:56:00 GMT+0
Resolved - This issue has been resolved. .

Oct 12, 18:15:14 GMT+0
Investigating - We are actively working to resolve the 401 Unauthorized Error for external clients trying to access feed.nascar.com. .

Duration: 1 hour and 29 minutes

Affected Components:

Oct 11, 22:53:36 GMT+0
Resolved - This incident has been resolved..

Oct 11, 21:24:46 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 45 minutes

Affected Components:

Oct 11, 22:53:43 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Oct 11, 21:08:49 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours and 14 minutes

Affected Components:

Oct 11, 22:53:50 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Oct 11, 20:39:57 GMT+0
Investigating - We are currently investigating this incident..

Duration: 3 hours and 15 minutes

Affected Components:

Oct 11, 22:53:55 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Oct 11, 19:39:07 GMT+0
Investigating - We are currently investigating this incident..

Duration: 38 minutes

Affected Components:

Oct 9, 23:25:48 GMT+0
Resolved - This incident has been resolved..

Oct 9, 22:48:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 8 minutes

Oct 5, 19:46:51 GMT+0
Resolved - .

Oct 5, 19:39:09 GMT+0
Investigating - We are planning a camera test at Charlotte this Friday morning which will initiate and impact our live Production data and systems during that time. **Approx Test Time:** 10:30am - 10:45am (after CW FAX) **What to Expect:** Similar to a Practice Session, notifications for an active session, flag alerts, and Timing and Scoring data will populate our distribution feeds and endpoints including ERDP, OnTrack, [feed.nascar.com](http://feed.nascar.com), [data.nascar.com](http://data.nascar.com), RMON, MLP, and Scoring Monitors. This should be considered test data and in no way impacts any live standings for the weekend. A red flag will be thrown to indicate the end of the test session. Please notify any others on your team of this upcoming test and expected impacts from our use of live event data for this test session. We appreciate your patience and cooperation..

Duration: 1 hour and 40 minutes

Affected Components:

Oct 5, 00:26:24 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Oct 4, 22:46:14 GMT+0
Investigating - We are currently investigating this incident..

Duration: 5 days, 5 hours and 38 minutes

Affected Components:

Oct 5, 19:47:12 GMT+0
Resolved - We implemented a fix and are currently monitoring the result..

Sep 30, 14:08:51 GMT+0
Identified - Livestream accounts now only permit one device per login at a time..

Duration: 33 minutes

Affected Components:

Sep 27, 22:04:47 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Sep 27, 21:32:01 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 15 minutes

Affected Components:

Sep 27, 22:04:53 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Sep 27, 20:49:25 GMT+0
Investigating - We are currently investigating this incident. Video may return during the race but is not confirmed..

Duration: 2 hours and 47 minutes

Affected Components:

Sep 27, 22:05:04 GMT+0
Resolved - We are continuing to work on a fix for this incident..

Sep 27, 19:18:08 GMT+0
Investigating - We are currently investigating this incident. We do not expect the video feed to return during the race..

Duration: 1 day, 17 hours and 32 minutes

Sep 21, 20:58:14 GMT+0
Resolved - The new recording of the NCS Race at Bristol has been uploaded to files.nascar.com..

Sep 20, 03:26:38 GMT+0
Investigating - We experienced a problem with recording the ERDP files during Saturday's Cup race at Bristol. We will work to re-create these files and distribute them as soon as we are able to..

Duration: 2 hours and 43 minutes

Affected Components:

Sep 20, 03:01:15 GMT+0
Resolved - This incident has been resolved..

Sep 20, 00:18:32 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 37 minutes

Affected Components:

Sep 19, 01:44:50 GMT+0
Resolved - This incident has been resolved..

Sep 19, 00:08:15 GMT+0
Investigating - We are currently investigating this incident..

Duration: 3 hours and 17 minutes

Affected Components:

Sep 13, 23:13:21 GMT+0
Resolved - This incident has been resolved..

Sep 13, 19:56:44 GMT+0
Investigating - We are currently investigating this incident..

Duration: 34 minutes

Affected Components:

Sep 7, 01:14:55 GMT+0
Resolved - This incident has been resolved..

Sep 7, 00:40:41 GMT+0
Investigating - We are currently investigating this incident..

Duration: 4 hours and 4 minutes

Affected Components:

Sep 7, 01:15:03 GMT+0
Resolved - This incident has been resolved..

Sep 6, 21:10:53 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour

Affected Components:

Aug 30, 02:38:05 GMT+0
Resolved - This incident has been resolved..

Aug 30, 01:38:22 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 12 minutes

Affected Components:

Aug 30, 02:38:36 GMT+0
Resolved - This incident has been resolved..

Aug 30, 01:32:08 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 30, 01:26:55 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 54 minutes

Affected Components:

Aug 30, 02:38:14 GMT+0
Resolved - This incident has been resolved..

Aug 30, 00:44:25 GMT+0
Investigating - We are currently investigating this incident..

Duration: 3 hours and 24 minutes

Affected Components:

Aug 30, 02:38:23 GMT+0
Resolved - This incident has been resolved..

Aug 29, 23:14:07 GMT+0
Investigating - We are currently investigating this incident..

Duration: 53 minutes

Affected Components:

Aug 29, 01:55:25 GMT+0
Resolved - This incident has been resolved..

Aug 29, 01:01:56 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours and 11 minutes

Affected Components:

Aug 29, 01:55:35 GMT+0
Resolved - This incident has been resolved..

Aug 28, 23:44:09 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours and 5 minutes

Affected Components: ,

Aug 28, 21:11:09 GMT+0
Resolved - This incident has been resolved..

Aug 28, 19:06:28 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 day, 20 hours and 31 minutes

Affected Components: , , , , , , , , , , , , ,

Aug 23, 22:31:14 GMT+0
Completed - Maintenance has completed successfully..

Aug 22, 02:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 22, 01:35:45 GMT+0
Identified - For this weekend, the #40 will be reflected in all live event data and applications for all sessions, including timing and scoring, scoring monitors, Livestream, Team Analytics, location, telemetry, and other ERDP data..

Duration: 3 days, 6 hours and 33 minutes

Affected Components:

May 17, 21:32:40 GMT+0
Completed - Maintenance has completed successfully..

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..

Duration: 7 days, 2 hours and 41 minutes

Affected Components:

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..

Duration: 9 days, 8 hours and 24 minutes

Affected Components:

Feb 10, 22:23:44 GMT+0
Completed - Maintenance has completed successfully..

Nov 3, 14:00:00 GMT+0
Identified - Telemetry message timestamps will be updated to use microseconds (previously milliseconds) for the 2026 season. .

Duration: 3 days

Affected Components: , , ,

Oct 3, 18:00:00 GMT+0
Completed - Maintenance has completed successfully.

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/>.

Duration: 8 hours

Affected Components:

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.

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).

Duration: 8 hours

Affected Components:

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/>.