UJ's Hamster Died. We're All That's Left...
https://ujrefugees.net/
damn, its plunging after hours. down over $17 per share.stonedmegman wrote: ↑Tue Jul 23, 2024 10:36 pm Tesla’s Profit Falls for Second Straight Quarter
https://www.wsj.com/business/autos/tesl ... r-3e849b36
I have some as well. I'm still in the black but definitely took a hit. The greedy part of me says this might be a buying opportunity but the negative side thinks this might have already sullied the brand to the point it cant be redeemed.
I sold it today. I just don't know how long it will take to get past this mess.
are they going to be financially liable for the costs of any of the damage? I didn't read the article, but I saw one today that was talking about the costs of that outage.B-Tender wrote: ↑Wed Jul 24, 2024 6:49 pmI sold it today. I just don't know how long it will take to get past this mess.
Yes, they very well could be. Our own company was brought down Friday morning due to this business. About 80% of our total world-wide workstations were brought down. At this point, we have almost 90% of those back up and running normally. The others were not harmed by the CrowdStrike update since they were either off or isolated from the network. CS hit early Friday morning, and it didn't actually take them long to realize there was a big problem and correct it, so a lot of workstations were spared. But those workstations hit, it created many blue recovery screens all around, since so many of our systems have 24/7 uptime. And due to the nature of our business, we need CS, as does our largest competitors who also got hit with similar results. To be on our company's network in whatever fashion, the CS client specific to our company needs to be installed. Simple and no bullshit.
I would compare this to hitting a fiber optic line during a construction job. Hitting the line has the expense of fixing the problem, obviously, but what revenue was lost during the time it was down? Well, that's the million dollar question (literally). And it seems like the game is to see how many zeros can be added. It gets ridiculous. I have never had to pay one, but I have had a few wagged in front of me that were just mind blowing. Until they found out that all of the correct people were called in advance and the line wasn't where it was supposed to be, etc (not my fault).QillerDaemon wrote: ↑Wed Jul 24, 2024 9:22 pmYes, they very well could be. Our own company was brought down Friday morning due to this business. About 80% of our total world-wide workstations were brought down. At this point, we have almost 90% of those back up and running normally. The others were not harmed by the CrowdStrike update since they were either off or isolated from the network. CS hit early Friday morning, and it didn't actually take them long to realize there was a big problem and correct it, so a lot of workstations were spared. But those workstations hit, it created many blue recovery screens all around, since so many of our systems have 24/7 uptime. And due to the nature of our business, we need CS, as does our largest competitors who also got hit with similar results. To be on our company's network in whatever fashion, the CS client specific to our company needs to be installed. Simple and no bullshit.
If your company does not have a CS account, you did not get hit, and you wouldn't have. This only affected huge companies with security needs that CS offers. I won't go into what I know about the update, but if you know anything about deep programming, especially system programming, you've probably heard of a "null pointer" and the effects it can have in "Ring 0". This blue recovery screen was actually a good thing, it kept a lot of systems from being in a bad state that might have allowed malware and network attacks. That's a large part of what CS protects against. And it was a single file that caused it. But getting to that file has been the major headache, the other network security options we use like Microsoft's BitLocker got in the way. It should be noted this only affected Windows computers, which is why Microsoft got blamed at first. It did not affect CS programs for non-Windows operating systems like the Mac and Unix/Linux, which account for a good number of those systems unaffected.
As for liability, most companies our size have IT insurance to tide against lost of income and the costs of getting a company's IT back up. But only to a relative degree. If it goes beyond such coverage, then CS certainly can be brought to pay. I wouldn't envy being an employee of CS right now. But CS is going nowhere, and I doubt seriously this will hamper their overall business much. In a month of so, it will be mostly forgotten other than by the legal and finance teams. The rest of us will remember in a faint haze about that week back in July of 2024, the way we recall similar other nasty situations where we had long sleepless days and nights manually restoring our company computers. We did our jobs and moved on.
Based on QD's clear and concise recommendation here to buy more stock, I'm going to treat this as a buying opportunity. Dont let me down QD!QillerDaemon wrote: ↑Wed Jul 24, 2024 9:22 pmYes, they very well could be. Our own company was brought down Friday morning due to this business. About 80% of our total world-wide workstations were brought down. At this point, we have almost 90% of those back up and running normally. The others were not harmed by the CrowdStrike update since they were either off or isolated from the network. CS hit early Friday morning, and it didn't actually take them long to realize there was a big problem and correct it, so a lot of workstations were spared. But those workstations hit, it created many blue recovery screens all around, since so many of our systems have 24/7 uptime. And due to the nature of our business, we need CS, as does our largest competitors who also got hit with similar results. To be on our company's network in whatever fashion, the CS client specific to our company needs to be installed. Simple and no bullshit.
If your company does not have a CS account, you did not get hit, and you wouldn't have. This only affected huge companies with security needs that CS offers. I won't go into what I know about the update, but if you know anything about deep programming, especially system programming, you've probably heard of a "null pointer" and the effects it can have in "Ring 0". This blue recovery screen was actually a good thing, it kept a lot of systems from being in a bad state that might have allowed malware and network attacks. That's a large part of what CS protects against. And it was a single file that caused it. But getting to that file has been the major headache, the other network security options we use like Microsoft's BitLocker got in the way. It should be noted this only affected Windows computers, which is why Microsoft got blamed at first. It did not affect CS programs for non-Windows operating systems like the Mac and Unix/Linux, which account for a good number of those systems unaffected.
As for liability, most companies our size have IT insurance to tide against lost of income and the costs of getting a company's IT back up. But only to a relative degree. If it goes beyond such coverage, then CS certainly can be brought to pay. I wouldn't envy being an employee of CS right now. But CS is going nowhere, and I doubt seriously this will hamper their overall business much. In a month of so, it will be mostly forgotten other than by the legal and finance teams. The rest of us will remember in a faint haze about that week back in July of 2024, the way we recall similar other nasty situations where we had long sleepless days and nights manually restoring our company computers. We did our jobs and moved on.
I took the Crowdstrike proceeds and bought an ETF for the Russell 2000.CHEEZY17 wrote: ↑Wed Jul 24, 2024 10:14 pmBased on QD's clear and concise recommendation here to buy more stock, I'm going to treat this as a buying opportunity. Dont let me down QD!QillerDaemon wrote: ↑Wed Jul 24, 2024 9:22 pmYes, they very well could be. Our own company was brought down Friday morning due to this business. About 80% of our total world-wide workstations were brought down. At this point, we have almost 90% of those back up and running normally. The others were not harmed by the CrowdStrike update since they were either off or isolated from the network. CS hit early Friday morning, and it didn't actually take them long to realize there was a big problem and correct it, so a lot of workstations were spared. But those workstations hit, it created many blue recovery screens all around, since so many of our systems have 24/7 uptime. And due to the nature of our business, we need CS, as does our largest competitors who also got hit with similar results. To be on our company's network in whatever fashion, the CS client specific to our company needs to be installed. Simple and no bullshit.
If your company does not have a CS account, you did not get hit, and you wouldn't have. This only affected huge companies with security needs that CS offers. I won't go into what I know about the update, but if you know anything about deep programming, especially system programming, you've probably heard of a "null pointer" and the effects it can have in "Ring 0". This blue recovery screen was actually a good thing, it kept a lot of systems from being in a bad state that might have allowed malware and network attacks. That's a large part of what CS protects against. And it was a single file that caused it. But getting to that file has been the major headache, the other network security options we use like Microsoft's BitLocker got in the way. It should be noted this only affected Windows computers, which is why Microsoft got blamed at first. It did not affect CS programs for non-Windows operating systems like the Mac and Unix/Linux, which account for a good number of those systems unaffected.
As for liability, most companies our size have IT insurance to tide against lost of income and the costs of getting a company's IT back up. But only to a relative degree. If it goes beyond such coverage, then CS certainly can be brought to pay. I wouldn't envy being an employee of CS right now. But CS is going nowhere, and I doubt seriously this will hamper their overall business much. In a month of so, it will be mostly forgotten other than by the legal and finance teams. The rest of us will remember in a faint haze about that week back in July of 2024, the way we recall similar other nasty situations where we had long sleepless days and nights manually restoring our company computers. We did our jobs and moved on.
I do love me a good ETF!B-Tender wrote: ↑Thu Jul 25, 2024 7:06 pmI took the Crowdstrike proceeds and bought an ETF for the Russell 2000.CHEEZY17 wrote: ↑Wed Jul 24, 2024 10:14 pmBased on QD's clear and concise recommendation here to buy more stock, I'm going to treat this as a buying opportunity. Dont let me down QD!QillerDaemon wrote: ↑Wed Jul 24, 2024 9:22 pmYes, they very well could be. Our own company was brought down Friday morning due to this business. About 80% of our total world-wide workstations were brought down. At this point, we have almost 90% of those back up and running normally. The others were not harmed by the CrowdStrike update since they were either off or isolated from the network. CS hit early Friday morning, and it didn't actually take them long to realize there was a big problem and correct it, so a lot of workstations were spared. But those workstations hit, it created many blue recovery screens all around, since so many of our systems have 24/7 uptime. And due to the nature of our business, we need CS, as does our largest competitors who also got hit with similar results. To be on our company's network in whatever fashion, the CS client specific to our company needs to be installed. Simple and no bullshit.
If your company does not have a CS account, you did not get hit, and you wouldn't have. This only affected huge companies with security needs that CS offers. I won't go into what I know about the update, but if you know anything about deep programming, especially system programming, you've probably heard of a "null pointer" and the effects it can have in "Ring 0". This blue recovery screen was actually a good thing, it kept a lot of systems from being in a bad state that might have allowed malware and network attacks. That's a large part of what CS protects against. And it was a single file that caused it. But getting to that file has been the major headache, the other network security options we use like Microsoft's BitLocker got in the way. It should be noted this only affected Windows computers, which is why Microsoft got blamed at first. It did not affect CS programs for non-Windows operating systems like the Mac and Unix/Linux, which account for a good number of those systems unaffected.
As for liability, most companies our size have IT insurance to tide against lost of income and the costs of getting a company's IT back up. But only to a relative degree. If it goes beyond such coverage, then CS certainly can be brought to pay. I wouldn't envy being an employee of CS right now. But CS is going nowhere, and I doubt seriously this will hamper their overall business much. In a month of so, it will be mostly forgotten other than by the legal and finance teams. The rest of us will remember in a faint haze about that week back in July of 2024, the way we recall similar other nasty situations where we had long sleepless days and nights manually restoring our company computers. We did our jobs and moved on.
I had that happen many years ago. I had put a Good Til Cancelled order in on some Chuckie Cheese. But it never dipped and just went up. then about 3 years later the market tanked one day and my broker called and said my order filled. It was one of the best purchases I ever had. In hindsight, that might not be a bad strategy. To just put a GTC order for some great stock at some ridiculous price and see what happens. Its impossible to buy on these dips. No one would have bought yesterday at the end of the day. And by morning, before the market opened, they were already projecting half the losses covered so any good stocks would have been way up.Just for the record I'm up about 8 bucks per share as of today. Not breaking any records for sure but not bad for taking a flyer on a stock that just caused billions of damage.
I have never seen a worse stock than the one I took the flyer on for this contest. My sister heard about it from "a guy at a party".CHEEZY17 wrote: ↑Mon Aug 19, 2024 7:19 pmJust for the record I'm up about 8 bucks per share as of today. Not breaking any records for sure but not bad for taking a flyer on a stock that just caused billions of damage.
the story of how it was supposed to sky rocket is too long to tell, but she has never, ever, had a good stock tip.