Recently over in the LowEndTalk-sphere, fears have been growing over a DediPath deadpool…
There’s been a thread with over 4,000 views up for days about a curious case of DediPath downtime, with no response from the DediPath team.
The normal public-facing employee and CTO, Ernie Quick, also removed DediPath as his source of employment as of last month according to his LinkedIn:
Ernie was also the founder of lowend VPS host, Hudson Valley Host.
He was last active over on LowEndTalk right now as I write you this post at 2:35 PM 8/1/23:
But, no public comment from Ernie or anyone else from DediPath so far.
DediPath Speculations
As noted on the DediPath LowEndTalk thread, issues weren’t limited to just one location.
It was 3 three locations:
- LA
- NYC
- San Jose
All of the Evocative/INAP locations.
Other providers at those locations with Evocative/INAP were up, too. It was just DediPath down.
The longer the downtime went on, the more concerns increased:
Speculations revolved around financial issues or unpaid invoices to Evocative, due to the fact it was isolated downtime to DediPath.
Strangely enough, WebHostingTalk now seems to actively censor any discussion involving DediPath, too:
A very mysterious situation with no clarification from DediPath themselves…
Outside of a RFO (reason for outage), later shared by a DediPath customer received directly via email:
Reason for Outage
Date: July 31, 2023Summary:
This document serves as the Reason for Outage (RFO) to provide a comprehensive explanation of the network interruption that occurred on July 28th, 2023. The purpose of this RFO is to outline the root cause, impact, actions taken for resolution, and preventative measures to avoid similar incidents in the future.Incident Overview:
On July 28th, 2023, at approx. 6PM EST a network interruption was experienced in San Jose, Redondo Beach, and Secaucus. This interruption resulted in a partial or complete loss of network connectivity and services for affected services. The incident was resolved at on July 28th, 2023 approx. 8:25PM with the exception of customers that were affected by a switch failure in Secaucus.Root Cause Analysis:
After a thorough investigation, the root cause of the network interruption has been identified as follows:Issue with common upstream provider we have in all three locations.
An unrelated switch failure that occurred in Secaucus, which affected a small portion of customer in New Jersey.
Impact:
The network interruption had the following significant impact:Downtime: Affected systems experienced a loss of connectivity, leading to disruptions in services.
Actions Taken:
Upon identifying the root cause, the following actions were taken to resolve the network interruption:Immediate Notification to Upstream Provider: The network team promptly contacted upstream providers to resolve the upstream issue.
Testing and Verification: After the upstream provider implemented the fix, DediPath performed thorough testing and verification were performed to ensure the stability and functionality of the network.
Since the incident was resolved we have opened discussions with other providers to prevent this situation from occurring again.
Conclusion:
The network interruption experienced on July 28th was a significant incident that impacted the organization and its users. Through a comprehensive root cause analysis and implementation of preventative measures, we aim to strengthen the network’s resilience and provide a more robust and reliable service to our customers. We apologize for any inconvenience caused and remain committed to continually improving our network infrastructure.If you have any further questions or concerns, please do not hesitate to reach out to our support team at support@dedipath.com
Sincerely,
DediPath
You’d think with all of the controversy, someone from DediPath might want to address things publicly.
EthernetServers Abruptly Move Upstreams
EthernetServers definitely felt the heat when DediPath, their (previously) primary upstream went down.
Customers started understandably blaming them for downtime even though there was nothing they could do about it.
It led to an executive decision by EthernetServers to leave ASAP with them announcing the following:
You are receiving this email because you have one or more active VPS’ with Ethernet Servers.
As many of you will have noticed, there have been server stability issues in recent weeks following a data center facility fire.
To protect the integrity of our company, and our customers, we are conducting emergency server migrations.
This is not the way we would like to be handling the matter, as in an ideal world, we would provide considerable notice upfront, however, we believe it is in everyone’s best interest to act sooner rather than later.
With regret, this does mean that IP space is changing.
Unfortunately, it is not feasible to provide individual status updates upon start and finish of the migrations, so we will be updating https://www.ethernetservers.com/clients/serverstatus.php with our progress.
To prioritize this task, we ask that all non-urgent support requests are deferred until this is complete.
Our sincere apologies for the trouble caused here.
Kind Regards,
Ethernet Servers
EthernetServers continued on in the thread stating that they manually migrated all customers to “a mix of Equinix and Digital Realty facilities.”
Unsurprisingly, a Few People Complained
For example…
Of course, downtime sucks… especially when you’re losing billions of dollars for every minute that you’re down.
(As per half of the downtime threads over at LowEndTalk.)
But really, though, among the mystery and skepticism involving DediPath, I think EthernetServers realized they didn’t want to risk having issues in the future and immediately reacted, then moving their servers.
If you ask me? I think that’s a perfect reaction from EthernetServers.
However, on the other hand…
Hopefully, DediPath Can Figure Things Out
Having spoken to Ernie in the past personally, he has always been a pretty knowledgeable and kind person… but if he’s truly left DediPath, that’s a big transition for DediPath.
He played a huge role for them. DediPath previously always provided a solid service at a solid price.
Regardless, downtime is never a good look for a business that relies on its uptime percentage as its primary selling point.
Maybe it’s just a one-off event, DediPath is totally fine, and EthernetServers moved for nothing, though…
Who knows?
Only time will tell.
But one thing is for certain:
EthernetServers and DediPath have officially signed the divorce papers.
Update 8/31/23:
This article was only posted on 8/1/23, but DediPath has already announced its closure.
The details are available here.
Related Posts:
- Path.net Seeks Discord Subpoena for Ex-Employee and Competitor’s Data - December 12, 2023
- Interviewing Christopher Cantwell - December 6, 2023
- Uptime Kuma: Your New Favorite Self-Hosted Uptime Monitoring Tool - December 1, 2023
Leave a Reply