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.

VPS at ColoCrossing Buffalo is down/unreachable

2»

Comments

  • angstromangstrom Moderator

    Just as an update:

    • I decided to wait and see if my VPS would come back up. (I didn't want to allow them to immediately recreate the VPS!)
    • A short time later (I had already gone to bed), my VPS came back up
    • My monitor shows 7 hours and 28 minutes of continuous downtime
    • Today, I asked via a ticket whether one could rely on the node for the longer (or even shorter) term. The answer was:
      "There was some issue with the host node which is why you were unable to access your VPS, Now we have resolved the issue."
      It's not clear what the issue was

    At this time, the node (NY-Cloud-40) seems responsive

    A fresh Geekbench-6.3.0 test (less than 10 minutes ago!) gives:

    • Single-Core Score: 809
    • Multi-Core Score: 1448

    My VPS has the following specs:

    • 2GB RAM | 2 vCores (Intel Xeon E5-2683 v4) | 40GB SSD | Debian 12 amd64
    Thanked by 1maverick
  • angstromangstrom Moderator
    edited May 2024

    @brandonk said:
    Registered just to say I'm on the same node, and it went down around 11:30AM EDT on the 16th. I received the exact same support response. Fortunately, the node came back up around 9:30PM EDT that evening and I used the opportunity to back up my configs. We'll see what happens going forward. The downtime is what it is, but insisting that the VPS has to be recreated when the node is just temporarily offline is bad.

    Thanks for sharing your experience

    I guess that the charitable interpretation of what happened is that there was a serious incident of some kind (as opposed to merely a connectivity issue), but -- yes -- the proposal to recreate the VPS was drastic as long as there was a realistic hope of saving the node

  • rogerwilcorogerwilco Member
    edited May 2024

    @angstrom bummer! On the flipside, if the instance was PaaS, offering to re-provision vs. waiting for whatever is impacting the host to be resolved is appreciated.

    Signed,
    Docker user

    Thanked by 1angstrom
  • neohneoh Member

    @BruhGamer12 said:
    My $7 a-year colocrossing VPS pushes 80-100TB a month of bandwidth and it rarely has issues I dunno why my cheap ass service rarely has issues compared to people who pay a lo more at colocrossing lol.

    Inclusive monthly traffic for BF vps is 330TB. Your bandwidth usage just reaches 30%.

  • @neoh said:

    @BruhGamer12 said:
    My $7 a-year colocrossing VPS pushes 80-100TB a month of bandwidth and it rarely has issues I dunno why my cheap ass service rarely has issues compared to people who pay a lo more at colocrossing lol.

    Inclusive monthly traffic for BF vps is 330TB. Your bandwidth usage just reaches 30%.

    That's crazy they allow so much lol

Sign In or Register to comment.