Latency monitoring of common DCs and hosts

[kaniini]

Hi guys,

As a side effect of monitoring the performance of my own network, using Smokeping, I realized that I actually have a lot of useful data on the latencies of other providers.

You can find the Smokeping instance here: http://monitor.tortois.es/smokeping/smokeping.cgi

If you want me to add any other providers to it, give me working non-router test IPs and their locations.  Also, whether or not they have multiple locations!

Please submit the data in the following format if you have one site:
 

+ ISPName

title = ISP (Location)

menu = ISP (Location)

host = 127.0.0.1

Or if you have multiple locations:

+ ISPName

title = ISP (Multiple)

menu = ISP (Multiple)

++ LocationOne

title = ISP Location One

menu = Location One

host = 127.0.0.1

++ LocationTwo

title = ISP Location Two

menu = Location Two

host = 127.0.1.1

(and so on, I am sure you get it by now)

 

[shovenose]

If you want to add us Both have only one location right now.

ShoveHost - ip: 204.68.96.67 hostname: speedtest.shovehost.com

BetterVPS - ip: 162.212.56.113 hostname: dallas.speedtest.bettervps.com

 

[Tux]

You forgot RamNode

199.241.28.6 (Atlanta) and 192.249.60.11 (Seattle)

 

[kaniini]

If you want to add us Both have only one location right now.


ShoveHost - ip: 204.68.96.67 hostname: speedtest.shovehost.com


BetterVPS - ip: 162.212.56.113 hostname: dallas.speedtest.bettervps.com

Added.

• Smokeping statistics for ShoveHost
  
• Smokeping statistics for BetterVPS

You forgot RamNode

199.241.28.6 (Atlanta) and 192.249.60.11 (Seattle)

Are these official test IPs?  I don't want to monitor a customer VPS and then have it go poof later.

 

[Tux]

Those are official RamNode test IPs.

 

[shovenose]

Thank you, that's actually quite useful for me

 

[RyanD]

Please contact me about the IP(s) you are using for COLO@ you appear to be using router IP(s) which de-prioritize ICMP and are going to have massively erratic results (as see in the smoke's)

 

[kaniini]

Please contact me about the IP(s) you are using for COLO@ you appear to be using router IP(s) which de-prioritize ICMP and are going to have massively erratic results (as see in the smoke's)

I sent you a PM asking for better test IPs.  The main concern here is that the ones published on Colo@'s WHT offers are either routers or whatever.

 

[RyanD]

I sent you a PM asking for better test IPs.  The main concern here is that the ones published on Colo@'s WHT offers are either routers or whatever.

Yeah, sales team didn't know any better, that should have been corrected and replaced long ago with our speedtest boxes

 

[kaniini]

The list of sites being monitored has been updated.

Synopsis of changes:

• BetterVPS removed from monitoring for now
• RamNode official test IPs added
• COLO@ test IPs changed to official for all locations but Clifton, which does not have an official test IP yet

I noticed that our probe for BuyVM in Buffalo has gone dark.  Is there an official test IP for BuyVM in Buffalo?  Francisco?

 

[RyanD]

It's amazing how much better our smoke(s)look when a router isn't being used

http://monitor.tortois.es/smokeping/smokeping.cgi?target=ColoAt.Atlanta

 

[kaniini]

Dallas and Chicago monitors should be coming up by the end of the week as compute infrastructure is deployed at those sites.

 

[KuJoe]

I hope I did this right:

+ Secure Dragon
title = Secure Dragon (Multiple)
menu = Secure Dragon (Multiple)

++ LocationOne
title = Secure Dragon Tampa, FL
menu = Tampa, FL
host = 199.167.29.3

++ LocationTwo
title = Secure Dragon Denver, CO
menu = Denver, CO
host = 198.57.46.3

++ LocationThree
title = Secure Dragon Portland, OR
menu = Portland, OR
host = 198.57.47.3

 

[RyanD]

Dallas and Chicago monitors should be coming up by the end of the week as compute infrastructure is deployed at those sites.

Why not a monitoring point in Atlanta?

 

[kaniini]

Secure Dragon has been added, and the Dallas monitor is now online.

 

[Steven F]

This is really cool! It's a very useful tool, I can't wait until it has a few monitors in the UK/NL/over seas.

Get Internap in there, nfoServers has a list of test IPs on their site to a bunch of their facilities.

 

[kaniini]

The Chicago monitor has been online for a while.

We will have infrastructure online at Serverius DC by mid-August (some planning is still being done), so there will be a monitor there too.

nfoServers will be added in the next config update.

 

[egihosting]

Very curious about our latency from different location.

And William, thank you for providing this service!

+ EdgeVM

title = EdgeVM (Multiple)

menu = EdgeVM (Multiple)

 

++ LocationOne

title = EdgeVM San Jose

menu = San Jose, CA

host = 136.0.16.3

 

++ LocationTwo

title = EdgeVM New York

menu = New York, NY

host = 205.164.41.66

 

[Damian]

This is a great service!

Please to add IPXcore:

+ IPXcore
title = IPXcore (Multiple)
menu = IPXcore (Multiple)

++ LocationOne
title = IPXcore Buffalo, NY
menu = Buffalo, NY
host = 198.144.190.2

++ LocationTwo
title = IPXcore San Diego, CA
menu = San Diego, CA
host = 209.112.254.18

++ LocationThree
title = IPXcore Kansas City, MO
menu = Kansas City, MO
host = 204.12.220.202

 

[mitgib]

Here is Hostigation for you

+ Hostigation

title = Hostigation (Multiple)

menu = Hostigation (Multiple)

++ LocationOne

title = Hostigation Los Angeles, CA

menu = Los Angeles, CA

host = 206.253.164.3

++ LocationTwo

title = Hostigation Charlotte, NC

menu = Charlotte, NC

host = 69.85.88.3