Catalysthost OpenVZ 128MB (TX)

wlanboy · Jul 18, 2014

Time for an update:

15 minutes of network downtime since the last update.

Uptime of the vps itself is 121 days.

CPU and I/O are great.

Network too.

Code:

 wget cachefly.cachefly.net/100mb.test -O /dev/null
--2014-07-18 19:35:21--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[===========================================================================================>] 104,857,600 33.6M/s   in 3.0s

2014-07-18 19:35:24 (33.6 MB/s) - `/dev/null' saved [104857600/104857600]

wlanboy · Sep 28, 2014

Time for an update:

0 minutes of network downtime since the last update.

Uptime of the vps itself is 121 days.

CPU and I/O are great.

Network too.

Code:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2014-09-28 08:49:50--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[===========================================================================================>] 104,857,600 35.9M/s   in 2.8s

2014-09-28 08:49:53 (35.9 MB/s) - `/dev/null' saved [104857600/104857600]

HalfEatenPie · Sep 28, 2014

Aww yisss

AutoSnipe · Oct 21, 2014

Everytime i see Catalysthost mentioned anywhere i feel like doing the leap to them.

I suppose if i think really hard i could find an use for another vps

Great Review Btw

wlanboy · Dec 7, 2014

Time for an update:

0 minutes of network downtime since the last update.

Uptime of the vps itself is 264 days.

CPU and I/O are great.

Network too.

Code:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2014-12-07 21:16:35--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[===================================================================================>] 104,857,600 41.5M/s   in 2.4s

2014-12-07 21:16:38 (41.5 MB/s) - `/dev/null' saved [104857600/104857600]

HalfEatenPie · Dec 7, 2014

wlanboy · Jan 19, 2015

Time for an update:

5 minutes of network downtime since the last update.

Uptime of the vps itself is 306 days.

CPU and I/O are great.

Network too:

Code:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-01-19 16:32:18--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================>] 104,857,600 42.0M/s   in 2.4s

2015-01-19 16:32:21 (42.0 MB/s) - `/dev/null' saved [104857600/104857600]

clownjugglar · Jan 19, 2015

I had a 96MB special with these guys, and it was a blast. I moved on because I needed more RAM and something closer to home.

The year I was with them the only major disruption was when they swapped IPs out. I believe they bought their own. Plenty of heads up time was given.

I can't provide stats like wlanboy, but I can say I never noticed lag or downtime. I ran murmur, irssi, an xmpp server, and had plenty of RAM to spare. All services worked when I needed them. I'd use them at least once a day if not more. I also heavily used it (and shared with a friend) as a SSH tunnel to use at 'work'.

I've recommended them to others in person so I know they've made at least one or two sales based on that.

HalfEatenPie · Jan 19, 2015

Thanks @wlanboy and @clownjugglar. We try pretty hard to make sure everything's in tip top shape!

wlanboy · Feb 20, 2015

Time for an update:

7 hours and 19 minutes of downtime since the last update.

Uptime of the vps is 17 days.

CPU and I/O are good.

Network is - as always - beyond any compare:

Code:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-02-20 15:18:19--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[========================================================>] 104,857,600 96.0M/s   in 1.0s

2015-02-20 15:18:20 (96.0 MB/s) - `/dev/null' saved [104857600/104857600]

drmike · Feb 22, 2015

wlanboy said:
wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-02-20 15:18:19-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[========================================================>] 104,857,600 96.0M/s in 1.0s

2015-02-20 15:18:20 (96.0 MB/s) - `/dev/null' saved [104857600/104857600]

Only one point to pick and that's the speed test. Cachefly like a lot of others is minimally accurate. They are shipping a big empty file and end to end hell there might be compression or other gaming on. Seems to be. Reason why they don't want serve a random right sort of file.

Kudos @wlanboy for the updates on your VPS providers. These are great.

That said, I remain impressed with throughput on Incero's network. They show good numbers for me more than other networks. Pretty consistent, day or night, weekday or weekend.

Those Catalyst guys, can't leave them out. Friendly bunch. Always down to earth and helpful. Am I an active customer? No, but I have been in past where I needed resources for folks where they are (Dallas). I am a recovering redneck VPS collector

HalfEatenPie · Feb 22, 2015

Thanks for keeping up with this @wlanboy! Appreciate it! I have a question though...

wlanboy said:
7 hours and 19 minutes of downtime since the last update.

From what I can tell, that should be 1 hour and 32 minutes of downtime since the last update. The 1 hour and 17 minutes are from one of the core routers acting up and being replaced immediately (once the problem was found that is) with a spare backup unit. I'm not quite sure where the other 6 or so hours came from, since your last update was from January 19th

drmike said:
Only one point to pick and that's the speed test. Cachefly like a lot of others is minimally accurate. They are shipping a big empty file and end to end hell there might be compression or other gaming on. Seems to be. Reason why they don't want serve a random right sort of file.

Kudos @wlanboy for the updates on your VPS providers. These are great.

That said, I remain impressed with throughput on Incero's network. They show good numbers for me more than other networks. Pretty consistent, day or night, weekday or weekend.

Those Catalyst guys, can't leave them out. Friendly bunch. Always down to earth and helpful. Am I an active customer? No, but I have been in past where I needed resources for folks where they are (Dallas). I am a recovering redneck VPS collector

Thanks @drmike! That's the goal here! I hate tooting our own horn since I'm an admin here and conflict of interest and all that, but it's definitely something we're happy about! Ryan's a beast with everything and it's a great pleasure working with him.

ryanarp · Feb 22, 2015

The other 6 or so hours was from forgetting to change IP address when we had cut off for IP migration.

Interesting your monitoring was down for 1 hour and 15 minutes. Network had a 30 minute blip and a 5 minutes follow up blip during the routing engine switch over . Guessing your IP didn't ARP into the switch as the node itself reported 35 minutes total. Make sure to open a ticket so we can check. We did some detailed reporting on twitter about that issue.

wlanboy · Feb 23, 2015

drmike said:
Only one point to pick and that's the speed test. Cachefly like a lot of others is minimally accurate. They are shipping a big empty file and end to end hell there might be compression or other gaming on. Seems to be. Reason why they don't want serve a random right sort of file.

But it is compareable if I am using it for all tests.

I cron the wgets through a whole week and take the result closest to the arithmetic mean value.

Believe me or not if I compare the MongoDB throughput and the wget results the values are compareable. Cachefly is something like the optimum throughput and all other transfers are below that line. But the bare numbers are in relation.

HalfEatenPie said:
From what I can tell, that should be 1 hour and 32 minutes of downtime since the last update. The 1 hour and 17 minutes are from one of the core routers acting up and being replaced immediately (once the problem was found that is) with a spare backup unit. I'm not quite sure where the other 6 or so hours came from, since your last update was from January 19th.

Thanks for the update.

I appreciate the feedback of providers explaining what happend - don't have the time to get through all announcements to catch the right date/time combinations.

HalfEatenPie · Feb 23, 2015

wlanboy said:
Thanks for the update.

I appreciate the feedback of providers explaining what happend - don't have the time to get through all announcements to catch the right date/time combinations.

Not a problem and I totally understand. You'll setup your monitoring and your service, we'll make sure the server is online, stable, and connected to the internet. Our own calculated network outage during this period was roughly around 35 minutes, so yours going on even longer is something we hope we can investigate later.

Again, thanks a ton for maintaining these rolling updates, we appreciate it.

wlanboy · Mar 26, 2015

Time for an update:

43 seconds of network downtime since the last update.

Uptime of the vps is 52 days.

CPU and I/O are good.

Network is - as always - great:

Code:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-03-26 21:00:35--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[========================================================>] 104,857,600 97.3M/s   in 1.0s

2015-03-26 21:00:37 (97.3 MB/s) - `/dev/null' saved [104857600/104857600]

wlanboy · Jul 2, 2015

Time for an update:

16 minutes of network downtime since the last update.

Uptime of the vps is 48 days.

CPU and I/O are good.

Network is - as always - great:

Code:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-07-02 07:22:12--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[=================================================================================================================================================>] 104,857,600 88.2M/s   in 1.1s

2015-07-02 07:22:13 (88.2 MB/s) - `/dev/null' saved [104857600/104857600]

wlanboy · Nov 18, 2015

Time for an update:

52 minutes of network downtime since the last update.

CPU and I/O are good.

HalfEatenPie · Nov 18, 2015

holla holla at yo boy!

wlanboy · Jan 2, 2016

Time for an update:

0 minutes of network downtime since the last update.
CPU and I/O are good.

Will update after the migration to the new data center in Dallas on January 4th/5th too.

Catalysthost OpenVZ 128MB (TX)

Content Contributer

Content Contributer

The Irrational One

New Member

Content Contributer

The Irrational One

Content Contributer

New Member

The Irrational One

Content Contributer

100% Tier-1 Gogent

The Irrational One

Catalyst Host

Content Contributer

The Irrational One

Content Contributer

Content Contributer

Content Contributer

The Irrational One

Content Contributer