Average latency to Slashdot.org?
Displaying poll results.21756 total votes.
Most Votes
- What's the highest dollar price will Bitcoin reach in 2024? Posted on February 28th, 2024 | 8470 votes
- Will ByteDance be forced to divest TikTok Posted on March 20th, 2024 | 6303 votes
Most Comments
- What's the highest dollar price will Bitcoin reach in 2024? Posted on March 20th, 2024 | 68 comments
- Will ByteDance be forced to divest TikTok Posted on March 20th, 2024 | 20 comments
Odd (Score:5, Funny)
Re:Odd (Score:5, Funny)
Once they manage, you'll see their first post magically appears!
Re:Odd (Score:3)
Haha. Or the 1ms crowd self destructed hacking /. and removing each others posts.
= 40ms to 80ms (same continent) (Score:5, Insightful)
Or using a typical US ISP.
You can't see it, but my middle finger is raised in the general direction of Comcast Headquarters.
Re:= 40ms to 80ms (same continent) (Score:3)
Comcasted out to 60 ms here. my route took me down to CA then back up to Seattle and finally over to Chicago (Elk Grove)
Tracing route to slashdot.org [216.34.181.45]
over a maximum of 30 hops:
1 22 ms 7 ms 12 ms 73.104.252.1
2 7 ms 7 ms 8 ms te-0-0-0-1-ur07.seattle.wa.seattle.comcast.net [68.87.205.65]
3 10 ms 15 ms 9 ms ae-20-0-ar03.burien.wa.seattle.comcast.net [69.139.164.125]
4 12 ms 11 ms 8 ms ae-1-0-ar03.seattle.wa.seattle.comcast.net [68.85.240.94]
5 14 ms 21 ms 26 ms te-1-3-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.93.165]
6 10 ms 10 ms 10 ms pos-0-1-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.85.38]
7 8 ms 8 ms 16 ms 208.172.91.5
8 20 ms 10 ms 15 ms cr1-te-0-5-1-0.sel.savvis.net [204.70.224.45]
9 61 ms 60 ms 61 ms cr1-ten-0-4-0-1.chd.savvis.net [204.70.192.134]
10 65 ms 60 ms 59 ms hr1-te-12-0-1.elkgrovech3.savvis.net [204.70.198.73]
11 69 ms 65 ms 64 ms das5-v3030.ch3.savvis.net [64.37.207.150]
12 62 ms 71 ms 72 ms 64.27.160.194
13 59 ms 62 ms 63 ms slashdot.org [216.34.181.45]
Trace complete.
Re:= 40ms to 80ms (same continent) (Score:2)
13 hops, 60ms, straight from comcast seattle to savvis. Second time also 13 hops, but via CA just like yours
Re:= 40ms to 80ms (same continent) (Score:2)
What's that anomalous hop #5 (Seattle -> San Jose -> Seattle)? Looks like a routing bug.
Re:= 40ms to 80ms (same continent) (Score:2)
The clue is in the second router name: "pos-0-1-0-0-pe01.seattle.wa.ibone.comcast.net". It's a backbone ("ibone") router. Most likely as part of their aggregation scheme, the San Jose router is allowed to feed into it but the lower-level Seattle routers are not. I actually see something similar in my routing pattern: I live in Ashburn Viriginia, but the packets route out to Charlotte NC and then back to Ashburn ibone routers.
Re:= 40ms to 80ms (same continent) (Score:3)
Or using a typical US ISP.
You can't see it, but my middle finger is raised in the general direction of Comcast Headquarters.
Pretty sad, I'm in Canada on a fairly average connection and I get 35ms.
Average = 74ms (Score:2)
Pinging from Buffalo on Time Warner.
Same continent is 87ms? (Score:2)
Despite the ranges specified in the survey, I'm getting 87ms ping in North America. I'm thinking this one is on Telus, though... or savvis, who I don't much trust anyway. Why the heck are they routing my packets to /.?
Re:Same continent is 87ms? (Score:2)
VPN +Firewall delays, and Savvis (Score:2)
I'm connected through my $DAYJOB VPN, so traceroute takes about 30ms to get out the door and over to ***.sfo.savvis.net. Traceroutes and pings from /. itself are running 80ms or so. Neither traceroute nor ping are necessarily accurate, because systems, especially routers, don't always prioritize them, and routers especially tend to use the underpowered CPU to respond to pings, but simple routed packets get handled by ASICs or at least line cards, so ping/traceroute times should be interpreted as an upper bound on the best route times.
In the States, 95ms (Score:4, Informative)
Time Warner. That pretty much says it all.
Re:In the States, 95ms (Score:2)
Here's mine:
$ /usr/sbin/traceroute slashdot.org ...res.rr.com (....1) 26.049 ms 26.186 ms 26.451 ms ...socal.rr.com (...) 18.361 ms 18.883 ms 19.020 ms ...socal.rr.com (...) 24.877 ms 25.501 ms 25.670 ms ...socal.rr.com (...) 25.757 ms 26.236 ms 26.493 ms ... (...) 28.782 ms 14.848 ms 17.855 ms
traceroute to slashdot.org (216.34.181.45), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.984 ms 1.263 ms 1.525 ms
2
3
4
5
6
7 107.14.19.138 (107.14.19.138) 14.614 ms ae-0-0.pr0.lax00.tbone.rr.com (66.109.6.135) 15.218 ms 21.140 ms
8 107.14.16.38 (107.14.16.38) 21.783 ms 22.325 ms 22.477 ms
9 cr1-tengig-0-5-0-0.lay.savvis.net (204.70.198.5) 41.288 ms 41.441 ms 41.576 ms
10 cr2-te-0-3-0-0.chd.savvis.net (204.70.192.97) 103.365 ms 103.879 ms 104.022 ms
11 hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (204.70.195.122) 105.279 ms 105.768 ms 109.344 ms
12 das5-v3032.ch3.savvis.net (64.37.207.158) 101.606 ms 101.512 ms 97.105 ms
13 64.27.160.194 (64.27.160.194) 109.545 ms 110.045 ms 110.187 ms
14 slashdot.org (216.34.181.45) 100.104 ms 100.851 ms 100.976 ms
Re:In the States, 95ms (Score:2)
My ping time with Time Warner is great,its my speed that sucks. Have to keep calling them up saying "I am paying for the 20 meg service, not the 1.5 meg service", and they will be like "sorry, let us reset something on our end". The whole issue could probably be resolved if they just added an additional node to my neighborhood. I shouldn't be getting buffering issues on a 3.5 Mbps Hulu stream when I have nothing else going on in my network.
Worst part about Time Warner is that their tech support seems to be centralized out of New York, and I have waited up to 3 hours on hold before (depending on which department you are trying to get in contact with - the cable card support is seriously understaffed, just to find out in the end that Time Warner puts broadcast flags on EVERYTHING, so I couldn't use the piece of equipment I wanted). i didn't have these kind of issues with Charter before I moved to a Time Warner area - Charter's tech support was in my city, never waited more than 5 minutes on hold, I was on a dedicated node so my speeds and pings were better than friends on Fios, I was paying half as much as I was with Time Warner and getting better speeds.... I'll tell you, I love the shorter commute I have to work now, but if I had it to do over again, there is no way I would move into another Time Warner service area!
Re:In the States, 95ms (hear, hear) (Score:3)
TWC is pathetic, but my other "choice" is AT&T.
Re:In the States, 95ms (Score:2)
Time Warner. That pretty much says it all.
It says you got through, which isn't always guaranteed on TW. After a few months on TW, I switched to using Google's DNS, since the only thing worse than 80+ ms is "timed out". And that was happening way too frequently.
Funny thing, though: Chrome always found the URLs it was looking for. Made me wonder if it was just using its own DNS anyway. Not curious enough to investigate further, though.
Re:In the States, 95ms (Score:2)
20 ms from Toronto.
How do I answer, oh Insensitive Clod? (Score:2)
I guess I'll have to choose the "= 40ms to 80ms (same continent)" option, because I am technically less than 80ms and the poll option syntactically doesn't specify a range.
Re:In the States (MO), 92ms (Score:2)
Savvis.net (Score:2)
Tracing route to slashdot.org [216.34.181.45]
over a maximum of 30 hops:
1 25 ms 18 ms 28 ms 76.40.96.1
2 10 ms 9 ms 12 ms 65.28.16.254
3 13 ms 15 ms 16 ms tge0-10-0-7.ksczksmp-ccr1.kc.rr.com [98.156.43.82]
4 82 ms 107 ms 102 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 58 ms 55 ms 55 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
6 42 ms 54 ms 54 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
7 44 ms 40 ms 38 ms 107.14.17.234
8 34 ms 34 ms 34 ms 107.14.16.30
9 34 ms 34 ms 35 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.204.146]
10 38 ms 36 ms 34 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
11 90 ms 92 ms 92 ms cr2-te-0-6-0-1.chd.savvis.net [206.28.97.89]
12 92 ms 95 ms 136 ms hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net [204.70.195.122]
13 92 ms 92 ms 98 ms das5-v3032.ch3.savvis.net [64.37.207.158]
14 100 ms 93 ms 103 ms 64.27.160.194
15 92 ms 92 ms 92 ms slashdot.org [216.34.181.45]
Trace complete.
Space? (Score:3)
Not sure the estimates in brackets are quite right. I get 280ms from Australia. And I'm on the ground.
Re:Space? (Score:2)
And I thought I was slow with my 261 ms.
On a 20/20 Mbit fibre connection in Hong Kong.
It's obviously the distance: pinging google.hk gives me 4.5 ms round trip time.
Re:Space? (Score:2)
93ms, from the same continent (Score:2)
261ms average from Beijing, China (Score:2)
Here on business.
Some web sites work reasonably fast, some terribly slowly, others not at all. In particular, local city newspaper web sites appear to be blocked by the Great Firewall, while national news sites appear to work.
133ms from NZ (Score:2)
ping latency does not matter (Score:3)
dialup != high latency (Score:4, Informative)
Although
High latency = slow
and
Dialup = slow
I wouldn't have thought of "dialup" to describe a high-latency connection. (Gee, by eliminating your local router, it drops a hop, and should be faster, right?)
Years ago, the latency from my DSL provider to some locations was so bad (>500ms ping times) that I actually dialed another ISP on when I was using an especially "chatty" protocol, and enjoyed better overall performance, even though the max theoretical throughput was only 1/20th what the DSL connection offered..
Re:dialup != high latency (Score:4, Interesting)
I live in the server room (Score:2)
Re: .sig (Score:2)
>CDE open sourced
uh, great? I guess. Excuse me if I don't jump for joy at the open sourcing of a Corba-based DE (also, I actually use CDE (at work), so we can just add another strike against it)
On fibre in Brisbane Australia (Score:2)
64 bytes from slashdot.org (216.34.181.45): icmp_req=1 ttl=237 time=244 ms
64 bytes from slashdot.org (216.34.181.45): icmp_req=2 ttl=237 time=244 ms
64 bytes from slashdot.org (216.34.181.45): icmp_req=3 ttl=237 time=244 ms
64 bytes from slashdot.org (216.34.181.45): icmp_req=4 ttl=237 time=245 ms
traceroute to slashdot.org (216.34.181.45), 30 hops max, 60 byte packets
1 10.1.1.254 (10.1.1.254) 4.813 ms 4.948 ms 5.093 ms
2 ge0-0-1.1626.br2.24lit.bne.core.overthewire.net.au (180.214.67.213) 5.210 ms 5.554 ms 5.847 ms
3 ge0-1.960.fw14.24lit.bne.core.overthewire.net.au (180.214.69.150) 3.311 ms 3.418 ms 3.537 ms
4 ge0-0-1.954.br2.24lit.bne.core.overthewire.net.au (180.214.69.137) 5.909 ms 6.102 ms 6.197 ms
5 ge0-0-0.2001.br3.148bru.bne.core.overthewire.net.au (180.214.88.72) 6.348 ms 6.485 ms 6.620 ms
6 ge0-0.3035.br1.639gar.syd.core.overthewire.net.au (180.214.88.133) 21.582 ms 19.712 ms 19.839 ms
7 202.68.65.81 (202.68.65.81) 19.867 ms 19.471 ms 19.798 ms
8 xe-3-1-0.r00.sydnau02.au.bb.gin.ntt.net (202.68.64.214) 19.990 ms 20.374 ms 20.748 ms
9 as-1.r02.lsanca03.us.bb.gin.ntt.net (129.250.6.106) 186.378 ms xe-1-0-0.r05.sydnau01.au.bb.gin.ntt.net (129.250.5.97) 20.945 ms 21.426 ms
10 xe-3-0-3.r20.lsanca03.us.bb.gin.ntt.net (129.250.2.141) 202.438 ms 202.682 ms 202.797 ms
11 xe-0-1-3.r21.lsanca03.us.bb.gin.ntt.net (129.250.2.189) 186.315 ms ae-1.r04.lsanca03.us.bb.gin.ntt.net (129.250.5.2) 202.866 ms xe-0-1-3.r21.lsanca03.us.bb.gin.ntt.net (129.250.2.189) 186.423 ms
12 208.175.201.13 (208.175.201.13) 203.294 ms ae-2.r04.lsanca03.us.bb.gin.ntt.net (129.250.5.70) 161.971 ms 162.044 ms
13 cr2-tengig-0-7-4-0.lay.savvis.net (204.70.198.9) 201.082 ms 201.196 ms 208.175.201.13 (208.175.201.13) 179.511 ms
14 cr2-tengig-0-7-4-0.lay.savvis.net (204.70.198.9) 181.143 ms 180.959 ms cr2-te-0-3-0-0.chd.savvis.net (204.70.192.97) 262.831 ms
15 hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (204.70.195.122) 269.972 ms 270.046 ms 269.110 ms
16 hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (204.70.195.122) 248.461 ms das5-v3032.ch3.savvis.net (64.37.207.158) 266.921 ms hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (204.70.195.122) 248.522 ms
17 das5-v3032.ch3.savvis.net (64.37.207.158) 246.155 ms 246.334 ms 64.27.160.194 (64.27.160.194) 278.941 ms
18 slashdot.org (216.34.181.45) 270.879 ms 64.27.160.194 (64.27.160.194) 247.043 ms slashdot.org (216.34.181.45) 270.570 ms
From Brazil... (Score:2)
Porto Alegre/GVT ~= 174ms
New Orleans over Cox Cable (Score:2)
69ms latency and 13 hops from N.O. through Dallas to slashdot.org.
From Minnetonka, MN, USA (Score:2)
dual.rkkda.org (0.0.0.0) Tue Apr 23 21:53:21 2013
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. router 0.0% 16 0.3 0.3 0.3 0.6 0.1
2. comcast 0.0% 16 9.4 9.8 7.3 25.9 4.4
3. te-0-2-0-5-sur01.minnetonka.mn.m 0.0% 15 17.8 10.6 7.7 22.1 4.0
4. te-0-6-0-12-ar01.roseville.mn.mi 0.0% 15 12.1 24.9 9.4 57.1 18.9
5. pos-0-11-0-0-cr01.350ecermak.il. 0.0% 15 19.5 21.4 17.9 36.6 4.4
6. pos-1-4-0-0-pe01.350ecermak.il.i 0.0% 15 19.5 20.0 18.0 31.0 3.3
7. ber1-tengig3-3.chicagoequinix.sa 0.0% 15 18.1 20.0 17.7 32.7 3.9
8. hr2-te-12-0-1.elkgrovech3.savvis 0.0% 15 28.3 32.3 19.1 100.0 24.8
9. das6-v3033.ch3.savvis.net 0.0% 15 20.5 21.3 19.1 33.2 3.7
10. 64.27.160.198 0.0% 15 26.7 25.5 18.8 35.7 5.3
11. slashdot.org 0.0% 15 20.0 23.0 18.5 49.4 8.3
45ms and I am a citizen (Score:2)
I didn't notice any speed increase in 2009 when I became a citizen - maybe I should move to Canada
(I am in MN so I am used to the cold by now)
Back in the Exodus Waltham data center days... (Score:2)
From Ohio via ATT (Score:2)
9 hops, 50 ms ping
Behind a firewall... (Score:2)
doesn't allow ping!
Re:Behind a firewall... (Score:2)
Yep. Same here. And it's not even some intrusion control measure, as I can ping anything inside the firewall.
650ms in Guantanamo Bay, Cuba (Score:2, Interesting)
DSL over 1950's copper wire on base.
300+ (Score:4, Informative)
6 packets transmitted, 6 received, 0% packet loss, time 5005ms
rtt min/avg/max/mdev = 313.723/320.220/329.918/4.815 ms
Thailand to US. Sometimes it can be even 400 ms to some US/EU server, but to slashdot is 300. Working over ssh on that kind of latency ... is painful, but one gets used to it.
Internet is good here, it's just that US/EU is so far away.. not as far as moon, but still..
Re:300+ (Score:3, Informative)
Working over ssh on that kind of latency ... is painful, but one gets used to it.
You shouldn't have to get used to it. If you have any say in what software is installed on the far end, and you don't need X forwarding, then I suggest you try mosh [mit.edu].
Re:300+ (Score:2)
Sounds like you or your ISP is connected to the US through satelite if you are getting those kind of ping times. Its similar to the response times I see with friends who have satelite.
Re:300+ (Score:2)
No it isn't. It's normal latency from this part of the world. Here in Australia, which is a bit further away again, I get average ping time of 310ms. There's a lot of fibre and numerous repeaters along the way. That all drives up propagation time.
Re:300+ (Score:2)
Oh, I actually misread. I saw time 5005ms and was thinking that was his results. Looking at it again, I see that its 320.220ms. My bad!
Hurray for ignorance! (Score:2)
Cape Town: 254ms (Score:3)
Ping statistics for 216.34.181.45:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 253ms, Maximum = 259ms, Average = 254ms
Traceroute (route goes from Cape Town to London and thence across the "pond"):
1 <1 ms <1 ms <1 ms 172.27.0.1
2 9 ms 9 ms 9 ms 196-210-170-129.dynamic.isadsl.co.za [196.210.170.129]
3 11 ms 11 ms 10 ms cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
4 10 ms 11 ms 11 ms 196.35.115.128
5 11 ms 11 ms 10 ms core2b-ctn-gi0-1.ip.isnet.net [168.209.2.3]
6 163 ms 163 ms 162 ms 168.209.246.66
7 161 ms 162 ms 207 ms 195.50.124.33
8 161 ms 161 ms 161 ms vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
9 192 ms 221 ms 203 ms ae-22-52.car2.London1.Level3.net [4.69.139.99]
10 161 ms 162 ms 161 ms bcr1-ge-6-1-0.londonlnx.savvis.net [206.24.169.29]
11 167 ms 162 ms 162 ms cr1-te-0-0-5-0.uk1.savvis.net [204.70.206.61]
12 254 ms 254 ms 253 ms cr1-te-0-6-0-0.chd.savvis.net [204.70.198.118]
13 254 ms 254 ms 253 ms hr1-te-12-0-1.elkgrovech3.savvis.net [204.70.198.73]
14 254 ms 254 ms 254 ms das5-v3030.ch3.savvis.net [64.37.207.150]
15 257 ms 254 ms 266 ms 64.27.160.194
16 254 ms 254 ms 254 ms slashdot.org [216.34.181.45]
missing answer: (Score:2)
In Soviet Russia (Score:2)
Moscow. 169 ms.
pretty quick (Score:2)
On a train in the UK going to work... (Score:2)
64 bytes from 216.34.181.45: icmp_seq=0 ttl=237 time=186.522 ms
64 bytes from 216.34.181.45: icmp_seq=1 ttl=237 time=382.941 ms
64 bytes from 216.34.181.45: icmp_seq=2 ttl=237 time=218.723 ms
Request timeout for icmp_seq 3
64 bytes from 216.34.181.45: icmp_seq=4 ttl=237 time=357.108 ms
64 bytes from 216.34.181.45: icmp_seq=3 ttl=237 time=1866.197 ms
Request timeout for icmp_seq 6
64 bytes from 216.34.181.45: icmp_seq=7 ttl=237 time=189.342 ms
64 bytes from 216.34.181.45: icmp_seq=5 ttl=237 time=3010.007 ms
64 bytes from 216.34.181.45: icmp_seq=8 ttl=237 time=186.937 ms
64 bytes from 216.34.181.45: icmp_seq=6 ttl=237 time=3081.013 ms
64 bytes from 216.34.181.45: icmp_seq=9 ttl=237 time=196.033 ms
Given I'm doing 100+ mph and still have Internet access I guess I'm not going to moan too much.
Variable, but over 200... (Score:3)
My 'net connection is quite variable. Sometimes it's good, and I get around 200ms to hit google.com, but sometimes it is so slow, and it takes ~1 second to hit google.com. At the moment, here's the results of my latest ping to /. (taken just moments ago).
As you can see, it's quite high.
And yet, I'm not in space, nor am I on dial-up. I'm just in yet another developing country. Me thinks the poll author (and the poll "editor") have first world problems.
2hrs from Chicago and 60ms ping wha? (Score:2)
My tracert sends me down to Dallas and back for some reason, despite being 2hrs or so from Elk Grove if that is indeed in Chicago area.
133 ms from Sweden (Score:2)
A steady 133 ms from Stockholm, Sweden.
Ethernet from home to ISP. I wonder how faster it would have been if I had bypassed my slow router...
304ms average on ADSL? (Score:2)
Is my connection really that slow, it certainly doesn't seem like it.
Does this include ... (Score:3)
Don't need to be in space for 200ms pings. (Score:2)
Re:Don't need to be in space for 200ms pings. (Score:3)
Last I checked, satelites were in space. :-)
Canada faster than some US? (Score:2)
I'm getting 31ms average ping from my wired computer. I'm on Videotron cable, in Canada. Wireless system is a bit slower.
Just for fun, I tried with cell phone connection (Bell 3G), and got 121ms average.
Brazil here... (Score:2)
I'm in a quantum network.. (Score:2)
..you insensitive clod!
6 packets transmitted, 6 received, 100% packet loss, time %$^£$^
killed
fellow US citizen? (Score:2)
not quite. More like 'friendly northern neighbour'
(i.e: Canada for the geographically impaired)
Ping times (Score:2)
I'm getting ping times as low as 17ms, and as high as 137ms. My average was 39.71, and my median was 24.
Consistent 11ms (Score:2)
Pinging just under 20ms but (Score:2)
I'm not inside US borders.
Request timed out... (Score:2)
But site loads. *shrugs*
Negative ping times (Score:5, Funny)
Since I'm in KC (home to Google Fiber), my ping times are in the negatives. Google knows what I want to ping before I do!
Descriptions wrong (Score:2)
The average of 5 pings is 93 msec, which you characterize as "a pond divides us". But your IP address is hosted in Iowa while I am in California, only half a continent away. I can download from Hayes, Iowa, at 15 Mbps.
Fellow American citizen, my shiny metal ass! (Score:2)
Despite our efforts to secede, Vermont is still part of the U.S., but I'm only getting 50ms.
On Verizon LTE 98ms (Score:2)
I'm on IPv6 (Score:2)
right around 40 (Score:2)
20ms (Score:2)
Ping time != distance. It's infrastructure. (Score:3)
My ping time is 162ms with a maximum of 1431.
But I'm in rural America. I'm lucky I can even ping anything, despite paying $70 a month for 0.5Mbps. (Yes, the decimal point and units are correct. We pay for 0.5, but get 0.35. Almost fast enough to stream music!)
Re:203ms - With Fibre connection and not in space (Score:3)
At least you get a return. Where I work, ping is dead. Perhaps Carrier Pigeons do not pass ICMP.
Re:203ms - With Fibre connection and not in space (Score:2)
Re:203ms - With Fibre connection and not in space (Score:2)
Yeah, both tracert and ping blocked on corporate level. I get about 40ms at home, when I am not using VPN to Sweeden. When using my VPN, latency skyrockets to around 200ms.
Re:203ms - With Fibre connection and not in space (Score:2)
239ms consistent for me - Tauranga, New Zealand.
Re:203ms - With Fibre connection and not in space (Score:2)
I'm in Australia and my average is 237ms, and they say that we don't need the NBN...
I'm sure that is a provider problem, as well as a shitty infrastructure problem. Once a year my Internet/phone line drops out for a day or two and then I have to call out a tech to look at the exchange, and each time they find a problem with it...
Re:203ms - With Fibre connection and not in space (Score:3, Interesting)
Re:203ms - With Fibre connection and not in space (Score:2)
Hmm 193-195ms here, I wouldn't say 4 hops is many.
Re:203ms - With Fibre connection and not in space (Score:2)
Re:203ms - With Fibre connection and not in space (Score:4, Informative)
Re:203ms - With Fibre connection and not in space (Score:2)
My goodness - something NZ does better than OZ!
Re:203ms - With Fibre connection and not in space (Score:2)
Re:203ms - With Fibre connection and not in space (Score:2)
~280ms, Johannesburg, South Africa. Yay! I'm not last!
Re:203ms - With Fibre connection and not in space (Score:2)
I get to blame mweb for my troubles....
Re: 200ms (Score:2)
Re: 200ms (Score:2)
Re: 200ms (Score:2)
Re:Same continent, faster than a citizen (Score:2)
Also 35ms from Shawinigan, Québec, Canada.
Re:Request timed out. (Score:2)
ping Slashdot.org
Pinging slashdot.org [216.34.181.45] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 216.34.181.45:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Re:Request timed out. (Score:2)
You insensitive clod.
The missing option I pictured was "still waiting for a reply... why are you ignoring me???"
Re:Finland (Score:2)
This one from a VDSL2 connection in TeliaSonera network in southern Finland.
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
> tracert slashdot.org
Tracing route to slashdot.org [216.34.181.45]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 172.20.0.1
2 21 ms 21 ms 21 ms dsl-espbrasgw1-54f9c0-1.dhcp.inet.fi [84.249.192.1]
3 21 ms 21 ms 21 ms 141.208.206.193
4 60 ms 24 ms 22 ms hkiasbr1-s0-0-0.datanet.tele.fi [141.208.8.10]
5 22 ms 47 ms 22 ms hls-b2-link.telia.net [213.248.75.17]
6 29 ms 30 ms 29 ms s-bb3-link.telia.net [213.155.133.70]
7 76 ms 58 ms 59 ms ffm-bb1-link.telia.net [213.155.135.50]
8 52 ms 55 ms 53 ms ffm-b12-link.telia.net [213.155.135.11]
9 50 ms 53 ms 53 ms 208.174.57.249
10 64 ms 58 ms 58 ms cr1-TE-0-8-1-0.frankfurtft3.savvis.net [204.70.206.153]
11 163 ms 161 ms 162 ms 206.28.96.218
12 161 ms 160 ms 161 ms hr1-te-12-0-1.elkgrovech3.savvis.net [204.70.198.73]
13 163 ms 162 ms 162 ms das6-v3033.ch3.savvis.net [64.37.207.162]
14 168 ms 164 ms 158 ms 64.27.160.198
15 161 ms 160 ms 160 ms slashdot.org [216.34.181.45]
Trace complete.
Re:=98ms (Score:2)
Exactly same country, but comcast.
Cable friggin sucks
Re:60ms-70ms in 13 hops from Southern California (Score:2)
That looks to me like it's the savvis Dallas to Chicago hop that's introducing the major latency, I see a similar jump, 10-12ms through the AT&T network to Chicago and then it jumps to 30+ms once it's handed off to savvis.
Re:Someone needs to mash up a Google Map tool here (Score:3)
Ha! 12 hops from Australia, and I am still in Aus on the third hop.
traceroute to slashdot.org (216.34.181.45), 64 hops max, 40 byte packets
1 lback9.comcen.com.au (203.23.236.9) 42.557 ms 41.783 ms 41.875 ms
2 core-syd-lns2.comcen.com.au (203.23.236.45) 42.703 ms 42.163 ms 42.824 ms
3 vlan551.22rrc76f000.optus.net.au (59.154.10.17) 208.661 ms 44.400 ms 43.367 ms
4 203.208.190.53 (203.208.190.53) 207.727 ms 251.916 ms 202.476 ms
5 67.17.192.141 (67.17.192.141) 201.065 ms 200.753 ms 201.199 ms
6 savvis-1.ar4.SJC2.gblx.net (64.208.27.50) 202.814 ms 203.397 ms 203.382 ms
7 cr2-te-0-5-0-1.sfo.savvis.net (206.28.98.117) 205.074 ms cr2-tengig0-7-3-0.sanfrancisco.savvis.net (204.70.206.57) 204.809 ms cr2-te-0-5-0-1.sfo.savvis.net (206.28.98.117) 205.253 ms
8 cr1-ten-0-4-0-1.chd.savvis.net (204.70.192.134) 256.832 ms 377.895 ms 421.459 ms
9 hr1-te-12-0-1.elkgrovech3.savvis.net (204.70.198.73) 284.913 ms 256.715 ms 255.786 ms
10 das6-v3033.ch3.savvis.net (64.37.207.162) 255.428 ms 338.727 ms 413.156 ms
11 64.27.160.198 (64.27.160.198) 259.926 ms 257.551 ms 255.290 ms
12 slashdot.org (216.34.181.45) 256.096 ms 254.693 ms 257.132 ms