dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
688
SmokeScreen
join:2014-08-15
Kanata, ON

SmokeScreen

Member

Gaming Pings Questions

Can anyone with a low ping to their closes server.
Go to pingtest.net and use Ashburn VA?
If any of those fifth people with super low pings could do that it would be great.
Most of the gaming serversnI play on are in that area too

hlo207
join:2012-11-16
North York, ON

1 edit

hlo207

Member










Tested 3 times

BTW I am a hater of Java runtime, more so since that security issue last year. So my Java runtime at my home laptop is off. That is why the packet loss cannot be done and that may have lowered the letter rating.
morganjason
join:2013-01-08
Conception Bay South, NL

morganjason to SmokeScreen

Member

to SmokeScreen
»www.pingtest.net/result/ ··· 5157.png



Smoke screen
@99.224.116.x

Smoke screen to hlo207

Anon

to hlo207
Little bit surprising I get that type of ping on bell fibe25. Is it possible to ping this ip 108.61.30.82. It's an ip for call of duty ghosts server

hlo207
join:2012-11-16
North York, ON

hlo207

Member

From my laptop with a ethernet cable of 6 ft to gigaswitch then 3ft ethernet to HH1000

C:\>ping 108.61.30.82

Pinging 108.61.30.82 with 32 bytes of data:
Reply from 108.61.30.82: bytes=32 time=19ms TTL=55
Reply from 108.61.30.82: bytes=32 time=18ms TTL=55
Reply from 108.61.30.82: bytes=32 time=24ms TTL=55
Reply from 108.61.30.82: bytes=32 time=23ms TTL=55

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

C:\>

C:\>tracert 108.61.30.82

Tracing route to vl185-as7.pnj1.choopa.net [108.61.30.82]
over a maximum of 30 hops:

1 less than 1 ms less than 1 ms less than 1 ms mynetwork [192.168.2.1]
2 3 ms 2 ms 3 ms 10.11.0.17
3 * 1 ms 3 ms 10.178.206.4
4 3 ms 2 ms 3 ms 10.178.206.5
5 23 ms 20 ms 18 ms tcore4-toronto47_te0-10-00.net.bell.ca [64.230.1
07.102]
6 19 ms 18 ms 18 ms tcore4-montreal01_pos0-2-0-0.net.bell.ca [64.230
.79.215]
7 18 ms 17 ms 18 ms newcore1-newyork83_so6-0-0_0 [64.230.187.234]
8 17 ms 16 ms 17 ms bx6-newyork83_xe3-0-0.net.bell.ca [64.230.187.15
8]
9 22 ms 22 ms 24 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]
10 20 ms 18 ms 18 ms vl185-as7.pnj1.choopa.net [108.61.30.82]

Trace complete.

C:\>

Inside HH1000 Utilities:

Pinging 108.61.30.82 with 32 bytes of data:

Ping statistics for 108.61.30.82
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Round-trip times: Minimum = 17 ms, Maximum = 19 ms, Average = 18 ms

Tracing route to 108.61.30.82 over a maximum of 30 hops:

2 ms 1 ms 1 ms 10.11.0.17 (10.11.0.17)
2 ms 1 ms 2 ms 10.178.206.4 (10.178.206.4)
139 ms 38 ms 2 ms 10.178.206.5 (10.178.206.5)
18 ms 24 ms 20 ms tcore3-toronto47_te0-10-0-0.net.bell.ca (64.230.107.104)
72 ms 17 ms 19 ms tcore3-montreal01_hundredgige0-9-0-0.net.bell.ca (64.230.79.193)
17 ms 19 ms 20 ms newcore1-newyork83_so6-0-0_0 (64.230.187.234)
17 ms 16 ms 19 ms bx6-newyork83_xe3-0-0.net.bell.ca (64.230.187.158)
17 ms 19 ms 117 ms nyiix.gi3-6.cr1.nyc1.choopa.net (198.32.160.157)
18 ms 17 ms 18 ms vl185-as7.pnj1.choopa.net (108.61.30.82)
demonte21
join:2009-02-20
Mirabel, QC

demonte21 to SmokeScreen

Member

to SmokeScreen
Done in wifi :

badskater
join:2013-02-23
Quebec, QC

1 edit

badskater to SmokeScreen

Member

to SmokeScreen



175/175 here.

Also did the same test as hlo207 on the same ip:

c:\>ping 108.61.30.82

Pinging 108.61.30.82 with 32 bytes of data:
Reply from 108.61.30.82: bytes=32 time=20ms TTL=55
Reply from 108.61.30.82: bytes=32 time=13ms TTL=55
Reply from 108.61.30.82: bytes=32 time=15ms TTL=55
Reply from 108.61.30.82: bytes=32 time=15ms TTL=55

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

c:\>tracert 108.61.30.82

Tracing route to vl185-as7.pnj1.choopa.net [108.61.30.82]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 172.24.0.1
2 6 ms 1 ms 1 ms 10.11.16.33
3 * 1 ms 2 ms 10.178.206.148
4 2 ms 1 ms 1 ms 10.178.206.149
5 12 ms 15 ms 15 ms dis17-quebec14_Gig6-0-0.net.bell.ca [64.230.87.2
46]
6 18 ms 18 ms 19 ms tcore3-montreal02_pos0-3-0-0.net.bell.ca [64.230
.32.186]
7 14 ms 12 ms 32 ms newcore1-newyork83_so1-0-0.net.bell.ca [64.230.1
87.129]
8 12 ms 12 ms 12 ms bx6-newyork83_xe3-0-0.net.bell.ca [64.230.187.15
8]
9 13 ms 18 ms 23 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

10 13 ms 13 ms 13 ms vl185-as7.pnj1.choopa.net [108.61.30.82]

Trace complete.
morganjason
join:2013-01-08
Conception Bay South, NL

morganjason

Member

Ping Test results:
Reply From Bytes Time TTL
108.61.30.82
(108.61.30.82): 32 46.4 49
108.61.30.82
(108.61.30.82): 32 39.4 49
108.61.30.82
(108.61.30.82): 32 38.4 49
108.61.30.82
(108.61.30.82): 32 39.6 49

Ping statistics:
Packets Sent Packets Received Packet Loss Round Trip Minimum Round Trip Maximum Round Trip Average
4 4 0 38.4 46.4 40.9

Hop Time 1 Time 2 Time 3 Host / IP Address
1 3.374ms 8.903ms 11.426ms 10.255.252.1
2 1.799ms 1.62ms 1.599ms 142.166.181.226
3 19.711ms 18.904ms 19.511ms 142.166.185.94
4 20.691ms 23.123ms 20.857ms 142.166.149.93
5 34.899ms 34.167ms 35.736ms 207.231.227.110
6 32.877ms 35.461ms 34.232ms 77.67.79.25
7 34.563ms 39.89ms 33.551ms 141.136.110.138 89.149.180.162
8 34.635ms 36.779ms 38.072ms 199.229.230.94
9 40.972ms 44.339ms 69.31.34.210 41.529ms 69.31.95.6 69.31.95.6
10 39.162ms 38.917ms 108.61.65.41 40.262ms 108.61.30.82
xappie
join:2002-06-26
Toronto, ON

xappie to SmokeScreen

Member

to SmokeScreen


DKS
Damn Kidney Stones

join:2001-03-22
Owen Sound, ON

DKS to SmokeScreen

to SmokeScreen

Crzyrio
join:2007-02-01
Mississauga, ON

Crzyrio to SmokeScreen

Member

to SmokeScreen
25/10 + FTTN.

battleop
join:2005-09-28
00000

battleop to SmokeScreen

Member

to SmokeScreen
"Most of the gaming serversnI play on are in that area too"

In the same area or same network? The ping servers and game servers could be in the same building in racks next to each other and your path to both could be thousands of miles from each other.

hlo207
join:2012-11-16
North York, ON

hlo207

Member

When you are dealing with the hosting/cloud services these servers are using, they are replicate everywhere so they will stay "up" all the time. The main server is in that location and if its goes down, it will probably affect the availability somewhat for a short time. They are usually virtual machines hosted inside physical machines. Those co-locates don't go down even with major power outage, their backup generators have enough output to power a city block for days.

battleop
join:2005-09-28
00000

battleop

Member

And this has what to do with routing?

hlo207
join:2012-11-16
North York, ON

hlo207

Member

Quite possible.

From my understanding based on what I have seen at my work and how our web applications were hosted, you have 2 ways to do it with these data centers.
1) You can buy your own hardware and put them there. You go in to set them up physically and you have to go in (remote or in person) to fix them when something goes wrong. The data center provides the electricity and internet access (speed depends on what you pay for). Unless your servers go down, your applications will be up 24/7.
2) You rent virtual machines from them. You can have whatever OS you like and whatever simulated hardware config you like as well depending on what you want to pay. Your virtual machines are replicated across the cloud and will stay up 24/7 unless something very catastrophic happens.

Big vendor like Microsoft runs their own data center that includes the Xbox Live. I am not too sure about these gaming servers. In general it will be cheaper to let someone else host the servers for you than setting up the infrastructure necessary to host your own 24/7 commercial servers.

battleop
join:2005-09-28
00000

battleop

Member

"the data center provides the electricity and internet access (speed depends on what you pay for)."

Most of your real data centers will have multiple carriers in their dc for their customers to make direct connections to in addition to an offering of their own blend of upstream providers.

Take 56 Marietta in Atlanta for example. It's a big carrier hotel with hundreds of providers in the same place. You could have one company with a cabinet and bandwidth from at&t and the cabinet next to them could have bandwidth from Verizon. An end user out on the internet would take two different paths to the same physical location.

That's why you can't say pings to the same physical location will be similar. In the real world they are neighbors but on the internet they are not.