Alright guys, excuse my lateness on talking about this stuff, but it's time to talk about the Pay-Review, which was Friday and Saturday, our first Pay-Review as our own company, and we had some challenges. Not that they should overshadow our successes because overall the event went great and 98% of people were able to watch the Pay-Review. There were a couple people who had issues. And listen, I already announced right after the event, I got no problem refunding anyone who wants a refund, okay? Information on the website for that, but if you want a refund, we'll give it to you because I want to keep everyone happy so we can keep doing these Pay-Reviews. A whole slew of circumstances came together and this is what happened. When we got the Pay-Review up and y'all, we tested it Wednesday, tested it Thursday, race day Friday, we're all ready to go. About two hours before the event starts and traffic starts to build on the website, I get a call from Johnny, our director, and he's like, hey man, Vimeo is down. Vimeo is a $10 billion company. Basically the way it works is once people get on their website, they get logged in, they pay, they start watching. All of the traffic load is on Vimeo at that point, right? So Vimeo goes down and we had no other real options at that point. We call him around, got onto another video streaming service, got it back up, right? Boom, our internet at the Freedom Factory flickers. Like, never has this happened before. We had fiber optic ran into the Freedom Factory, which is well worth it because we have insane internet speeds, but I don't know where our internet flickers. So now, right after we get back up and going, all of your guys screens at home go black. And everyone at home, you know, obviously starts hitting the refresh button. Now we have a refresh swarm, was 895,000 refreshes in under five minutes. So that then took down the server, which holds the whole website up. So now you can even access the website. So it went from now being able to see the video player, to then being able to see the video player again, to now the website is just completely down. So now the refresh swarm, starting to calm down, server comes back online, everybody comes back in, right? So now we have this like huge cycle of people coming back on the website, leaning, coming back. I don't know how many customers we lost in this time, you know, whatever. But eventually everything's smoothened out. And we ended up back on Vimeo. And this was during qualifying. So basically like 20 minutes before we actually got to race, we got this all ironed out. And we were right at the point where we were going to stream the free of 500 for free to YouTube and refund everybody, which would have been devastating to obviously the entire financial effort of this whole, you know, race. But we were going to do it because I didn't want to let you guys down. And that option was on the table up until all of a sudden we started getting the website to smooth it out. And I'm not going to say there was another issue. Like we had a couple of points during the race where, you know, we saw quite a few people refreshing. But it seemed like we were pretty smooth for a lot of you guys. And I hope it did. Doing this on our own was a huge, mungus risk. And it almost all failed. Literally almost all came crumbling down minutes before the race. It was so close to getting fully streamed for free. It's a really intense thing, like I'm telling you, between this free of 500 and the very first one, I mean, those two events are in the top five most stressful things have ever had happened in my career. So glad we got through that. I felt really good when the race was over and like I'm texting the director in my car like is the stream up, is the stream up. And magically it stayed up throughout the whole race. Just amazing. And then we moved to the next thing, which really wasn't the problem. Is we had some attacks on the website. A DDoS attack where people are basically loading up our server using bots. We have a defense mechanism in place for that. So that didn't affect us so much. But really just the flicker in the internet was bad. But it's crazy that people do still attack the website. Like why are you attacking our website? You know what I mean? I guess people just have to always target good things. Not going to worry about that. It was only like 50,000 refreshes. This is what it's equal to. So Pales in comparison to the internet flickering and causing all of you guys to actually refresh all good. Onto my next issue, the lap counter. We were supposed to have a thing on screen. The whole race says lap 22 out of 100, lap 40 out of 100. The people that do our lap counting, we have a company come in that manages positions and laps and all that. There was an ampersand in the coding that puts out the data to our live stream. And that ampersand corrupted all the data. So we had no real lap count. You'll see it comes on later. You know, about 70 laps in because we were doing it manually. But the guys are scrambling in the background, trying to figure this out. And then the position data also was corrupted because of that. So that's why there was no leaderboard, no lap counter. That stuff was all supposed to be there. We paid for it to be there. You know, we did everything we could to have it there, but it just didn't work out. So next time we'll be done. A couple things I want to touch on. The audio, one million times better. Audio, on point, sounded way better. The cameras were way too dark. Okay, we did not have our camera set up correctly. We're going to work on that. Some things I know that I need to do is get a mobile jumbo tron for the people at the Freedom Factory. So they can actually see the stream. Because they don't have any way to see in store. You play as they don't know what the announcers are talking about. So we got to get that figured out. Maybe even some TVs and hang them from the fence. We got to get an audio system for the south side of the track now. We have the VIP. And then the weather guys, the weather was crazy this weekend. I don't know if you guys really caught into that. I was trying not to show it on the channel. We had some crazy weather. On Thursday, 30 not winds, Friday, supposed to rain all day. Rain's in the morning, rain's still about 11. Boom, dries up. Somehow it didn't rain later in the day too. Because right when we were starting the race, the airfights comes up to me as I did. It looks like it's going to rain. And I'm like, I don't think it's going to rain. These humongous clouds come right over the track and just hold. Didn't drop a single drop rain. Miracle. Then moved to Saturday. It was for sure going to rain right like 530. So we moved the whole event up. So I know some of you guys missed the burnout contest because you didn't know that. But we announced it everywhere on our social media. It was one of those deals where like if we stuck with the time that we had already said, we wouldn't have gotten the event done. So I said screw it. We're going to move the whole thing up two hours, two and a half hours, show up early, get on the stream early. And we are going to get this event done. A lot of guys would just say, oh, we had a cancel the event. I just wanted to do it. I didn't want to miss out on doing burnouts. It was amazing. So we got the event done. The last car went and then it started raining. It was literally perfect timing. So we got really lucky on Saturday. But it cut the event short. So sorry to those of you who didn't feel like you got your full experience because we just rushed through it. We were freaking boom, boom, boom, trying to get those burnouts. There's everyone got a shot. Some people towed their car like a thousand miles. I wanted to make sure they got it blow off some tires. You know, overall, we had some issues. The internet stuff, definitely the most important of them because if you guys can't watch and you're spending money to watch, this is just not right. In person, there's no internet to blind these people. So they're going to need to show regardless. At home, there's a bigger audience. The freedom factory can only hold so many people. There's a way bigger audience watching from home. That's you guys. And I thank you guys so much for dealing with our technical difficulties. We really are going to get it worked out. We think we have a lot of good strategies that we're going to implement for Indy, which is May 14th and 15th. It's just a lot. So overall, guys, I'm not going to let the difficulties shadow such amazing things that we accomplished. I hope you guys liked it. And we're open to any recommendations in the comments below. Drop your comments. We will try and improve. We will improve. Come back for the next one, May 14th and 15th. The Indy 800. We're looking forward to it, but that's it for now. We'll find you later.