Well it is time to look for a new NOC! I am not going to have all my eggs in one basket!

:angry: Lesson Learned! :angry:

From where I am Deru Internet (deru.net) has one good PING!


Using Netlab 1.4 30 pings - 100 packet size and 5 time out.
----------------------------------------------------------------------------
From Pensacola Fl.

deru.net - Avg 59 ms
nac.net - Avg 71 ms

BurstNet.com - Avg 93 ms
Oppps :blush: Wrong URL... It is Burst.net... I will repost as the times will change as it is much later. SORRY

Please post your Ping report for ALL THREE NOCs and where you are from.

Also tell what you know about the NOCs Network listed above.

Pinging deru.net [140.99.0.9] with 32 bytes of data:

Reply from 140.99.0.9: bytes=32 time=671ms TTL=239
Reply from 140.99.0.9: bytes=32 time=658ms TTL=239
Reply from 140.99.0.9: bytes=32 time=657ms TTL=239
Reply from 140.99.0.9: bytes=32 time=653ms TTL=239

Ping statistics for 140.99.0.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 653ms, Maximum = 671ms, Average = 659ms

Not bad....

Pinging 140.99.0.9 with 32 bytes of data:

Reply from 140.99.0.9: bytes=32 time=70ms TTL=243
Reply from 140.99.0.9: bytes=32 time=70ms TTL=243
Reply from 140.99.0.9: bytes=32 time=71ms TTL=243
Reply from 140.99.0.9: bytes=32 time=70ms TTL=243

Ping statistics for 140.99.0.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 71ms, Average = 70ms

CALIFORNIA

[admin@plesk admin]$ ping deru.net
PING deru.net (140.99.0.9) from 216.40.250.24 : 56(84) bytes of data.
64 bytes from deru.net (140.99.0.9): icmp_seq=0 ttl=239 time=37.077 msec
64 bytes from deru.net (140.99.0.9): icmp_seq=1 ttl=239 time=39.953 msec
64 bytes from deru.net (140.99.0.9): icmp_seq=2 ttl=239 time=29.962 msec
64 bytes from deru.net (140.99.0.9): icmp_seq=3 ttl=239 time=29.958 msec
64 bytes from deru.net (140.99.0.9): icmp_seq=4 ttl=239 time=29.958 msec
64 bytes from deru.net (140.99.0.9): icmp_seq=5 ttl=239 time=39.956 msec
64 bytes from deru.net (140.99.0.9): icmp_seq=6 ttl=239 time=29.903 msec

--- deru.net ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max/mdev = 29.903/33.823/39.956/4.572 ms
[admin@plesk admin]$

What about nac.net and BurstNet.com ?

What are your pings to them and where are you all from?

Regards,
Dale

I'm from Michigan...


C:\>ping deru.net

Pinging deru.net [140.99.0.9] with 32 bytes of data:

Reply from 140.99.0.9: bytes=32 time=61ms TTL=234
Reply from 140.99.0.9: bytes=32 time=59ms TTL=234
Reply from 140.99.0.9: bytes=32 time=57ms TTL=234
Reply from 140.99.0.9: bytes=32 time=58ms TTL=234

Ping statistics for 140.99.0.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 61ms, Average = 58ms


C:\>ping nac.net

Pinging nac.net [207.99.0.69] with 32 bytes of data:

Reply from 207.99.0.69: bytes=32 time=43ms TTL=233
Reply from 207.99.0.69: bytes=32 time=40ms TTL=233
Reply from 207.99.0.69: bytes=32 time=58ms TTL=233
Reply from 207.99.0.69: bytes=32 time=41ms TTL=233

Ping statistics for 207.99.0.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 58ms, Average = 45ms


C:\>ping burstnet.com

Pinging burstnet.com [128.11.42.61] with 32 bytes of data:

Reply from 128.11.42.61: bytes=32 time=48ms TTL=231
Reply from 128.11.42.61: bytes=32 time=47ms TTL=231
Reply from 128.11.42.61: bytes=32 time=47ms TTL=231
Reply from 128.11.42.61: bytes=32 time=46ms TTL=231

Ping statistics for 128.11.42.61:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 48ms, Average = 47ms

Deru: 34ms
NAC: 96ms
BurstNet: 89ms

This is from a 1.5MBit DSL in northern California.

Our URL is:
http://www.burst.net
NOT
http://www.burstnet.com :-)

Also, we have additional carriers/routes/capacity being installed within the next 5-10 days (fiber and equipment just came in today...), so you may want to wait until then to judge our speed :-)


Warm Regards,
Sean R.
BurstNET

To be fair, here's what I received when issuing a ping to burst.net:


C:\>ping burst.net

Pinging burst.net [66.96.192.201] with 32 bytes of data:

Reply from 66.96.192.201: bytes=32 time=50ms TTL=240
Reply from 66.96.192.201: bytes=32 time=50ms TTL=240
Reply from 66.96.192.201: bytes=32 time=53ms TTL=240
Reply from 66.96.192.201: bytes=32 time=57ms TTL=240

Ping statistics for 66.96.192.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 57ms, Average = 52ms

Here is the updated ping tests....

deru.net - Avg 53 ms
nac.net - Avg 66 ms
Burst.Net - Avg 79 ms

Sorry Sean... IT was a over site! :blush:

I am not sure who deru.net is but their network has been solid! Their web page tells me that are a local ISP but I do know that they do dedicated servers and Co-Location.

We all know who nac.net and Burst.Net are even if I get Burst's url wrong.

Originally posted by CrowMan
From where I am Deru Internet (deru.net) has one good PING!


And I believe that's because you live closer to deru (AZ) than to either NAC/Burst (east cost).

Ping to some great extend is just a measure of distance between the origin and destination of the ping packets. The farther away the distance, the longer it takes for the packet to reach the destination (actually, it needs to travel back to you again).

Now, NAC and Burst are located in east coast, NJ and PA respectively whereas Deru is located (I believe) in AZ, close enough to west coast. Somebody from California will of course (under normal condition) have a better ping result to deru than to NAC/Burst since it's just less distance for the ping packet to travel.

It may not be the cleverest idea to choose an NOC solely based on ping results. For one, ping does not tell you much about the quality of a network. Even if it does so, your result has to be statistically valid; a ping can go really bad at small period of time and then back again to normal. I would suggest you to use pingplotter (www.pingplotter.com) to monitor these network for much longer time (say, days or weeks). Using pingplotter, you not only able to monitor these network continuosly for days/weeks but also in the event of a problem you can see where the problem starts to happen (your ISP? somehwere between your ISP and the data center?). I usually run this program to monitor several data center at the same time to learn just a little bit more about them and make a good comparison among them.

Good luck ...

cheers,
:beer:

dektong,

Ping Plotter Rocks! Thanks this will help things! It will also be a good test and marker of the new stuff Burst.net is going to be adding as well.

I am in Fl. so nac.net and Burst.Net are closer than deru.net. That is why I am so surprised at their ping.

Thanks again for the link to Ping Plotter. It will help me in finding a 2nd NOC. We will be spaning our servers over 2 or 3 NOCs from this point on.

It is just good Business!

From Powell, Ohio

To deru.net

PING deru.net (140.99.0.9): 56 data bytes
64 bytes from 140.99.0.9: icmp_seq=0 ttl=239 time=83.887 ms
64 bytes from 140.99.0.9: icmp_seq=1 ttl=239 time=93.182 ms
64 bytes from 140.99.0.9: icmp_seq=2 ttl=239 time=90.420 ms
64 bytes from 140.99.0.9: icmp_seq=3 ttl=239 time=83.184 ms
64 bytes from 140.99.0.9: icmp_seq=4 ttl=239 time=81.019 ms
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 81.019/86.338/93.182/4.642 ms


To nac.net

PING nac.net (207.99.0.69): 56 data bytes
64 bytes from 207.99.0.69: icmp_seq=0 ttl=242 time=58.060 ms
64 bytes from 207.99.0.69: icmp_seq=1 ttl=242 time=56.650 ms
64 bytes from 207.99.0.69: icmp_seq=2 ttl=242 time=57.818 ms
64 bytes from 207.99.0.69: icmp_seq=3 ttl=242 time=56.849 ms
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 56.650/57.344/58.060/0.605 ms

To Burst.NET

PING burst.net (66.96.192.201): 56 data bytes
64 bytes from 66.96.192.201: icmp_seq=0 ttl=240 time=60.756 ms
64 bytes from 66.96.192.201: icmp_seq=1 ttl=240 time=60.857 ms
64 bytes from 66.96.192.201: icmp_seq=2 ttl=240 time=59.704 ms
64 bytes from 66.96.192.201: icmp_seq=3 ttl=240 time=57.899 ms
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 57.899/59.804/60.857/1.189 ms

Thanks for the post......

It is cool seeing how others see the three NOC's.

Their are so many things that factor in to connect times.

As a host it is good to see how others around the country are hitting the NOC.

GOOD STUFF!;)

Originally posted by dektong


It may not be the cleverest idea to choose an NOC solely based on ping results. For one, ping does not tell you much about the quality of a network.

Good luck ...

cheers,
:beer:

I agree with that. There are so many other things that come into play besides ping times...

Mind you, this is from more of a dedicated server / colocation standpoint, but it still applies to shared hosting to some extent.

1) Connectivity Redundancy - Do they have multiple pipes to the Internet? Is there enough capacity in each of those pipes to carry their network traffic in the event that one goes down? If they claim to have redundant pipes, do they actually have them BGP4 routed?

2) Network Redundancy - Do they have dual or more fiber feeds into their NOC and are each of their providers on a distinct physical path coming into the building? It does no good if some whacko with a backhoe digs up their OC12 loop that both of their OC3 ports are running on. Do they have hot stand by core routers? Redundant distribution switches, redundant feeds to your cab, etc etc.

3) Environment concerns - is the NOC adequetely cooled? Do they a N+1 cooling system in place, so that even if one of their A/C unit fails, their NOC will stay nice and cool. What about fire supression?

4) Staffing - Is the NOC staffed 24/7? What happens when their core router goes down at 3AM? Do they have to call someone in or do they have engineers on site?

5) Security - How is the facility secured? I've heard stories of people walking into NOCs, giving some BS story about working for such and such company, and then getting access to the NOC and walking out of the building with a lot of stolen equipment.

6) Price. One NOC might be redundant to the max, but they might be super expensive. The next guy might lacking in a few areas, but might be much cheaper

7) Financial stability - As everyone here should know, the entire telcom industry is suffering, and several major players have gone belly up or closed down several data centers, etc. Exodus, Verio, and Inflow come to mind ...

I could elaborate further, but there's a lot more to picking a NOC then just comparing ping times.

One good resource that I use to look at ping / traceroute times of a particular NOC from a variety of geographical locations is www.traceroute.org. The web site is just one big list of traceroute servers all over the world. The benifit to using these traceroute servers as opposed asking people in WHT for ping times is that you'll be able to go back do additional tests. Plus you get the added benifit of having the entire traceroute in front of you, which can be helpful in determining what providers a NOC is using, and if they are using BGP4 correctly, etc.

Happy hunting

From Tucson, Arizona :

C:\>ping deru.net

Pinging deru.net [140.99.0.9] with 32 bytes of data:

Reply from 140.99.0.9: bytes=32 time=85ms TTL=233
Reply from 140.99.0.9: bytes=32 time=85ms TTL=233
Reply from 140.99.0.9: bytes=32 time=84ms TTL=233
Reply from 140.99.0.9: bytes=32 time=85ms TTL=233

Ping statistics for 140.99.0.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 85ms, Average = 84ms

C:\>ping nac.net

Pinging nac.net [207.99.0.69] with 32 bytes of data:

Reply from 207.99.0.69: bytes=32 time=95ms TTL=241
Reply from 207.99.0.69: bytes=32 time=95ms TTL=241
Reply from 207.99.0.69: bytes=32 time=97ms TTL=241
Reply from 207.99.0.69: bytes=32 time=99ms TTL=241

Ping statistics for 207.99.0.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 99ms, Average = 96ms

C:\>ping burst.net

Pinging burst.net [66.96.192.201] with 32 bytes of data:

Reply from 66.96.192.201: bytes=32 time=114ms TTL=240
Reply from 66.96.192.201: bytes=32 time=122ms TTL=240
Reply from 66.96.192.201: bytes=32 time=116ms TTL=240
Reply from 66.96.192.201: bytes=32 time=118ms TTL=240

Ping statistics for 66.96.192.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 122ms, Average = 117ms