- Joined
- Dec 1, 2016
- Messages
- 6,582
- Points
- 728

and so do i but that is not the issue here it is about the people not the organizationBelieve you me Sir! I have a lot of written documentation of this.
![]() |
As a way to introduce our brass coins to the community, we will raffle off a free coin during the month of August. Follow link ABOVE for instructions for entering. |
![]() |
![]() |
The beloved Ships in Scale Magazine is back and charting a new course for 2026! Discover new skills, new techniques, and new inspirations in every issue. NOTE THAT OUR NEXT ISSUE WILL BE MARCH/APRIL 2026 |
![]() |

and so do i but that is not the issue here it is about the people not the organizationBelieve you me Sir! I have a lot of written documentation of this.

Well said, CLB. In fact, I was one of those who got banned from MSW, so I understand how easy it is for old frustrations to resurface... but I fully agree that this isn’t the moment for that. What we’ve lost as a community is far bigger than any individual grievance.I really hope this thread becomes about mourning all the loss of that wealth of information we just lost as a community and moving forward rather than airing past grudges and reopening old wounds.



Yes we are safeA lot of English text for a simple Dutchy….
And for me as a newbie, are we safe on SOS?
Do we have a regular backup?

But we are going to take extra measures soonGreat! What a relief
THe same thing could happen on SOS, so yes, always backup your data.A lot of English text for a simple Dutchy….
And for me as a newbie, are we safe on SOS?
Do we have a regular backup?
ran an AI search asking whether the below statement published by MSW and The Nautical Research Guild was true:
In the last three days, there has been a global issue regarding the software that operates computer servers. This has impacted websites and servers around the world. An unscrupulous group of hackers had found a way around server security and had broken into many servers, destroying data.
Outages are tracked by a number of outage tracking services worldwide because information about "global issues" regarding server hacking is critical information for platform administrators everywhere. When any significant security breaches occur, they are immediately reported and likely become big news. This would certainly have triggered an AI response confirming some sort of "global" hacking event. Instead, I received the following response:
Recent Global Server Software Issue — What’s Happening
There is no confirmed report of a global server software security breach in the last three days that has been widely documented by major outage tracking sources. While there have been widespread internet outages in recent weeks, these have been attributed to network infrastructure failures, transit provider issues, and internal service problems, not to a coordinated hack that bypassed server security Network World+1.
Bottom line: The recent global server-related issues have been network and service outages, not a confirmed hack. If you are seeing widespread website failures, it’s more likely due to infrastructure or configuration problems than a coordinated security breach. For the most accurate, real-time updates, check live outage maps from ThousandEyes or Cloudflare Radar.
- Cloudflare Outage (Nov 18, 2025): A major outage affected many websites and platforms, including X, ChatGPT, Amazon, Spotify, Zoom, Uber, and Azure. Cloudflare blamed it on a spike in unusual traffic that caused a configuration file to grow beyond expected size, triggering a crash in its traffic management system. They stressed there was no evidence of malicious activity Ars Technica.
- Hurricane Electric & Cogent Outages (Jan 2–31, 2026): These were network transit provider outages affecting multiple regions. For example, Hurricane Electric’s Los Angeles nodes went down for about an hour, impacting downstream partners in the U.S., Asia, and Europe Network World.
- Ongoing Outage Tracking: Platforms like ThousandEyes and Entireweb Status show real-time maps of global internet health, but no recent “server security breach” event has been flagged as the cause of these disruptions ThousandEyes+1.
- Outages ≠ Security Breach: Many large-scale outages are due to technical failures, configuration errors, or transit provider issues, not hacker exploits.
- No Evidence of Hack: In the Cloudflare case, the company explicitly stated there was no evidence of malicious activity Ars Technica.
- Security Breaches Are Different: If a server security breach had occurred, it would typically be reported by security firms, ISPs, or cloud providers, and would involve specific indicators like unauthorized access or data exfiltration.
What’s happened now affects the members, the builders, and the people who shared their work and knowledge over the years. In fact, many of those members are no longer with us, and their work was a way to remember their contributions.
When support was asked for, I don’t see it as something directed at an administration. It’s about the community of modelers, the same kind of people we have here and many other forums, perhaps. At the end of the day, this is our hobby, and it’s built on people helping each other and sharing what they know.
I really hope this thread becomes about mourning all the loss of that wealth of information we just lost as a community and moving forward rather than airing past grudges and reopening old wounds.
Bob, I can’t say I’m surprised by your post, but I don’t have any desire to get into a back-and-forth argument about it.Well said, Jimsky! It is all about the MSW members. But I strongly believe, whether I have a dog in the fight or not, that it is decidedly not in SoS's best interests to "provide aid and comfort to the enemy" by giving any assistance or support to the MSW administration or its tax-exempt 501.c.3. corporate sponsor, the NRG. They have behaved badly time and time again. Not the many great modelers who participate as members. I'm talking about the corporate management that controls that platform. Our assistance should be provided to the MSW member modelers, not to the MSW "corporate oligarchs." These people are not SoS's friends.
Industry security watchdog reports do not confirm NRG and MSW management's explanation of their being the victim of a hacking cyberattack. Industry security monitoring resources report to the contrary that nothing of the "global attack" nature MSW and NRG claim has been reported in the applicable timeframe. There may be some explanation, but as far as I am concerned, it does not appear that they are being honest about the matter for reasons unknown. Neither is there any question of the MSW management's long-standing animus against SoS and SoS members on account of their simply being SoS members. The management of NRG and MSW, after a previous "fatal crash" again failed to securely back up their database. I fail to see in their official announcements the slightest acceptance of responsibility for the loss of the huge amount of highly valuable data that has been wiped out by their grossly negligent failure to follow what is indisputably standard operating procedure for any serious platform. Neither have they acknowledged their responsibility to their members who, at the management's initiation, contributed a tremendous amount of time and energy to contribute the data they did. These people aren't even the friends of their own forum's members.
SoS owes nothing to MSW. There is nothing of any value to the scale ship modeling hobby that MSW ever offered the hobby that SoS didn't do more of and do better. Wake up and smell the bacon! There are dozens of active SoS members who were misled to believe SoS was garbage and then were thrown out of MSW because they did not follow the "party line" and kiss the hands of those who now control it. If SoS were to suffer a fatal loss of its database, do you really think MSW would be riding to its rescue? Get real!
This may be MSW's misfortune, if not its own misadventure, and it's certainly the regrettable loss of a lot of valuable ship modeling data, albeit nothing that is lost to posterity, but the bulk of it in one way or another is duplicated and presently available on SoS. This is an opportunity for SoS to take the lead and leave MSW in its dust. This is the favor SoS should be doing for the scale ship modeling community right now, rather than enabling "bad actors" to continue their misbehavior on a renewed and revitalized MSW.
Now is the time for SoS to reach out to every MSW member and welcome them to join the rest of us at SoS for as long as they wish. I'm betting those "50,000" members will turn out to be less than 500 members who have posted in the last month, but I think if they get to know us, they won't be leaving very soon. The way we help the MSW modelers is to invite them to "stay at our house" for the duration and thereafter, but we don't encourage the MSW management to return expecting to be welcomed back to the ship modeling community. Now that MSW is down, it behooves the ship modeling community and SoS in particular, to see that it stays down and out. Talk about being nice and all that as much as you want but never forget that nice guys finish last.
![]()
Hackers are actively exploiting a bug in cPanel, used by millions of websites | TechCrunch
Web hosts are scrambling to fix the bug under active attack by hackers. One company said hackers have been abusing the bug for months.techcrunch.com
The current year is 2026, not 2027.... unless I've taken a lot longer to lay the Muscongus bay garboard strake than I thought. (BTW, that's the exact date that the MSW site went down)April 30, 2026, a year ago
Bob, realistically, none of us is in any position, nor do we want to be, to pick apart what happened on their end. We don't have access to their systems, we don't know how their backups were set up, and we certainly can't say with any confidence what vulnerability was or wasn't in play. That's just the reality, and BTW, not our business. Speculating about it here won't change what happened, and it's unlikely to help anyone move forward either. The thread is rather informational.Interesting information. The article was published on April 30, 2026, a year ago. This vulnerability was identified as early as February 2026, fourteen months ago, and a repair patch was circulated to address the vulnerability. As the article reports, most vulnerable servers were patched by the end of April of last year. The question remains: If this is the vulnerability that was exploited to destroy the MSW database, why don't they admit that the hackers' success was due to their failure to install a patch on their vulnerable servers, and to explain why their two additional back-up files "failed" as well.
Neither here no there to me. Just sayin'.

Is it 2027 already? Time really does fly....The article was published on April 30, 2026, a year ago

