Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Even More Stock Liquidation!! Colos, Dedis and Storage at Microtronix DC (Ohio)

2»

Comments

  • Seems to be back up now.

  • Email from Microtronix:

    Dear Customer,

    We wanted to update everyone on what happened Sunday morning 12-15-2024 around 7:20 a.m. EST. We don't have a full clear picture as of yet, we are still investigating with our upline to see what we uncover, this is why we have not fully updated everyone as of yet.

    Currently what we know. Ever since two weeks ago when we had the splice in our Worthington route that line has been sporadically unstable in its operating. We would lose connection to our peer in Worthington for seconds at random times. This has caused our failover setup to falsely report that line going down here and there over the past two weeks. Its become more sporadic the end of this last week. We attribute that to attenuation in the line since the splice was put in. Our upline cannot track it down, since they are receiving full power output when they check the line across its POPs, so far however, we are 99% positive this is the reason for the false positives we have experienced. As such we have not put much precendance on Worthington route errors until they find the problem.

    The Worthington line went down at 2:30 a.m. this morning, EST, it was another false positive but our failover setup kicked in. Normally this would not of caused an issue, so we left it until morning to deal with.

    The issue arose when at 7:20 a.m. our Lima route also failed tests against our peer for connectivity. Though the failover setup should not of been active anymore at that point, and a failed line should of just failed, it did not. The failover setup we have in place malfunctioned, a blip in the Lima route (which we can't seem to track down currently) happened at the same time when we had a port failure. We tried to bring things back up remotely as we usually do, but were unable to. This required a technician to be on-site which took a bit more time than usual. Usually a port failure would not cause issues, since we have fail-over in place, but being as Worthington was down because of the false positive it caused total failure.

    At this point we have replaced the malfunctioning port, and temporarily disabled our fail-over procedure. We are re-implementing it to better suit this scenario and potential future scenarios like it.

    In the mean time we are further investigating with level 3 engineers at our upline tomorrow throughout the day when they are at full strength also, see if we can track down where the attenuation is at in the Worthington line. At this point we think it was a perfect storm, two things seemingly unrelated happening at the same time, murphy's law.

    We do apologize for any issues caused and the downtime, we are working to mitigate this possibility in the future. Thank you all!

    Microtronix Administration

    Thanked by 1jfreak53
  • jfreak53jfreak53 Member, Patron Provider

    Line issues. Thanks to @eezcloud for posting our update.

  • @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Thanked by 1iKeyZ
  • But I came to this thread expecting hardware sale for a hosting company going out of business.

    Why use "liquidate" when you're not closing business? It doesn't mean what you think it means.

  • @eezcloud said:
    Email from Microtronix:

    Dear Customer,

    We wanted to update everyone on what happened Sunday morning 12-15-2024 around 7:20 a.m. EST. We don't have a full clear picture as of yet, we are still investigating with our upline to see what we uncover, this is why we have not fully updated everyone as of yet.

    Currently what we know. Ever since two weeks ago when we had the splice in our Worthington route that line has been sporadically unstable in its operating. We would lose connection to our peer in Worthington for seconds at random times. This has caused our failover setup to falsely report that line going down here and there over the past two weeks. Its become more sporadic the end of this last week. We attribute that to attenuation in the line since the splice was put in. Our upline cannot track it down, since they are receiving full power output when they check the line across its POPs, so far however, we are 99% positive this is the reason for the false positives we have experienced. As such we have not put much precendance on Worthington route errors until they find the problem.

    The Worthington line went down at 2:30 a.m. this morning, EST, it was another false positive but our failover setup kicked in. Normally this would not of caused an issue, so we left it until morning to deal with.

    The issue arose when at 7:20 a.m. our Lima route also failed tests against our peer for connectivity. Though the failover setup should not of been active anymore at that point, and a failed line should of just failed, it did not. The failover setup we have in place malfunctioned, a blip in the Lima route (which we can't seem to track down currently) happened at the same time when we had a port failure. We tried to bring things back up remotely as we usually do, but were unable to. This required a technician to be on-site which took a bit more time than usual. Usually a port failure would not cause issues, since we have fail-over in place, but being as Worthington was down because of the false positive it caused total failure.

    At this point we have replaced the malfunctioning port, and temporarily disabled our fail-over procedure. We are re-implementing it to better suit this scenario and potential future scenarios like it.

    In the mean time we are further investigating with level 3 engineers at our upline tomorrow throughout the day when they are at full strength also, see if we can track down where the attenuation is at in the Worthington line. At this point we think it was a perfect storm, two things seemingly unrelated happening at the same time, murphy's law.

    We do apologize for any issues caused and the downtime, we are working to mitigate this possibility in the future. Thank you all!

    Microtronix Administration

    Constructive feedback: run your messages through an AI to polish things up. I like using the professional option on ahrefs website to make what I'm saying read better, but recently been using Gemini with similar improvements.

    Ahrefs output:

    Dear Customer,

    We would like to provide an update regarding the events that occurred on Sunday morning, December 15, 2024, at approximately 7:20 a.m. EST. While we are still in the process of gathering all the details, we are actively investigating the situation with our upstream team, which is why a comprehensive update has not yet been issued.

    Here is what we currently know: Two weeks ago, we experienced a splice issue on our Worthington route, which has since resulted in intermittent instability. We have been losing connection to our peer in Worthington for brief periods, leading our failover system to incorrectly report outages over the past fortnight. This instability has intensified in the last week, and we suspect it is due to attenuation in the line following the splice. Our upstream team has been unable to pinpoint the issue, as they are receiving full power output during their checks across the Points of Presence (POPs). However, we are nearly certain that this is the cause of the false positives we have been encountering. Consequently, we have not prioritized the Worthington route errors until the underlying problem is identified.

    This morning at 2:30 a.m. EST, the Worthington line experienced another outage, which turned out to be another false positive, prompting our failover system to activate. Typically, this would not have posed a significant issue, so we opted to address it in the morning.

    The situation escalated at 7:20 a.m. when our Lima route also failed connectivity tests with our peer. Although the failover system should have been inactive at that time, a simultaneous failure occurred, leading to a malfunction in our failover setup. A transient issue on the Lima route coincided with a port failure, which we are currently unable to trace. Our usual remote recovery efforts were unsuccessful, necessitating an on-site technician, which took longer than anticipated. Normally, a port failure would not disrupt service due to our failover measures, but the ongoing issues with the Worthington line resulted in a complete service failure.

  • @TimboJones said:

    @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Yeah, the guy doing "due dilligence" didn't bother going to the providers' HOME PAGE and scroll down to see his answer

    It was obviously a question in bad faith.

    Go be a white knight somewhere else, canuck.

  • @Petey_Long said: in bad faith

    Clearly a loaded comment.

    Thanked by 1TimboJones
  • @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Yeah, the guy doing "due dilligence" didn't bother going to the providers' HOME PAGE and scroll down to see his answer

    It was obviously a question in bad faith.

    Go be a white knight somewhere else, canuck.

    It was quick question. No fucking investigation or "due diligence" needed before hand. It could have just been a curious question, given the Jesus freak handle and signature.

    You're aware you're the annoying "white knight" in this case, right? You inserted yourself over fake insult and making requirements of due diligence. Most people would just tell you to fuck off for being butthurt over nothing.

  • Petey_LongPetey_Long Barred
    edited December 2024

    @TimboJones said:

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Yeah, the guy doing "due dilligence" didn't bother going to the providers' HOME PAGE and scroll down to see his answer

    It was obviously a question in bad faith.

    Go be a white knight somewhere else, canuck.

    It was quick question. No fucking investigation or "due diligence" needed before hand. It could have just been a curious question, given the Jesus freak handle and signature.

    You're aware you're the annoying "white knight" in this case, right? You inserted yourself over fake insult and making requirements of due diligence. Most people would just tell you to fuck off for being butthurt over nothing.

    He literally said it was him doing due dilligence ya dumb canuck

    Just trying to do my due diligence before inquiring about colocation options.

    If you're going to argue on someone's behalf, know who/what you're arguing for.

  • TimboJonesTimboJones Member
    edited December 2024

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Yeah, the guy doing "due dilligence" didn't bother going to the providers' HOME PAGE and scroll down to see his answer

    It was obviously a question in bad faith.

    Go be a white knight somewhere else, canuck.

    It was quick question. No fucking investigation or "due diligence" needed before hand. It could have just been a curious question, given the Jesus freak handle and signature.

    You're aware you're the annoying "white knight" in this case, right? You inserted yourself over fake insult and making requirements of due diligence. Most people would just tell you to fuck off for being butthurt over nothing.

    He literally said it was him doing due dilligence ya dumb canuck

    So? It was after you shat on him for asking a valid question. And that's exactly what due diligence is, he confirmed details, SMH. Just accept you were being a tool and apologize, or carry on like you prevented some form of hate from single fucking question.

  • @TimboJones said:

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Yeah, the guy doing "due dilligence" didn't bother going to the providers' HOME PAGE and scroll down to see his answer

    It was obviously a question in bad faith.

    Go be a white knight somewhere else, canuck.

    It was quick question. No fucking investigation or "due diligence" needed before hand. It could have just been a curious question, given the Jesus freak handle and signature.

    You're aware you're the annoying "white knight" in this case, right? You inserted yourself over fake insult and making requirements of due diligence. Most people would just tell you to fuck off for being butthurt over nothing.

    He literally said it was him doing due dilligence ya dumb canuck

    So? It was after you shat on him for asking a valid question.

    When you ask stupid questions, you get stupid answers.

  • @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @TimboJones said:

    @Petey_Long said:

    @wewehello said:
    @Petey_Long I get it you like to act like a dick. Glad your not a host or it would prob be a quick Deadpool :smile:

    For someone to say they're doing "due dilligence" with a straight face and not even visit the providers website just makes this all the more laughable.

    Just admit you got caught with your pants down, rushed to find some sort of alternate explanation as to why you said what you said and just take the L already

    Are you sniffing glue? The guy asked the OP a valid question without insult and you lost your shit due to your religious bias. You're clearly the douche in this situation.

    Yeah, the guy doing "due dilligence" didn't bother going to the providers' HOME PAGE and scroll down to see his answer

    It was obviously a question in bad faith.

    Go be a white knight somewhere else, canuck.

    It was quick question. No fucking investigation or "due diligence" needed before hand. It could have just been a curious question, given the Jesus freak handle and signature.

    You're aware you're the annoying "white knight" in this case, right? You inserted yourself over fake insult and making requirements of due diligence. Most people would just tell you to fuck off for being butthurt over nothing.

    He literally said it was him doing due dilligence ya dumb canuck

    So? It was after you shat on him for asking a valid question.

    When you ask stupid questions, you get stupid answers.

    Sigh. I asked the question, so you're admitting to giving a stupid answer. Got it.

    You can't rewrite history on a public forum.

Sign In or Register to comment.