Lag is relative. /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />
From my aunts cottage in St Beatrix in rural Quebec I get pings of 40ish, then again, cowtown can't connect from south Calgary, yet my friend from Edmonton can, it's all relative. The current service isn't a t1 connection, though it's the best residentially available... and I'm obviously refering in that post to me, as was the whole point, because I can't $#@!ing have a clue how well a penguin in the deep antarcttic can connect to any of the servers.
Possible New (FAST!) Server?
-
Grim_Reaper_4u
- Posts: 356
- Joined: Wed Jul 30, 2003 7:00 am
- Location: Netherlands
I'm not talking about my lag here Bax. I don't even think about lag unless its the packloss sort. Its the lag that everyone complains about when playing large games on FTX. Then again, I seem to have misunderstood your post. Please disregard.jgbaxter wrote:QUOTE (jgbaxter @ Jan 23 2007, 01:34 PM) Lag is relative. /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />
From my aunts cottage in St Beatrix in rural Quebec I get pings of 40ish, then again, cowtown can't connect from south Calgary, yet my friend from Edmonton can, it's all relative. The current service isn't a t1 connection, though it's the best residentially available... and I'm obviously refering in that post to me, as was the whole point, because I can't $#@!ing have a clue how well a penguin in the deep antarcttic can connect to any of the servers.
Last edited by ImmortalZ on Tue Jan 23, 2007 9:24 am, edited 1 time in total.
I live in Michigan
Do I win the pathic connection game???
Do I win the pathic connection game???
Code: Select all
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
17 260 ms 316 ms 460 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Reply from 204.14.17.162: bytes=32 time=198ms TTL=49
Reply from 204.14.17.162: bytes=32 time=234ms TTL=49
Reply from 204.14.17.162: bytes=32 time=205ms TTL=49
Reply from 204.14.17.162: bytes=32 time=355ms TTL=49
Minimum = 198ms, Maximum = 355ms, Average = 248ms
Reply from 204.14.17.162: bytes=32 time=225ms TTL=49
Reply from 204.14.17.162: bytes=32 time=414ms TTL=49
Reply from 204.14.17.162: bytes=32 time=340ms TTL=49
Reply from 204.14.17.162: bytes=32 time=210ms TTL=49
Minimum = 210ms, Maximum = 414ms, Average = 297ms
Reply from 204.14.17.162: bytes=32 time=767ms TTL=49
Reply from 204.14.17.162: bytes=32 time=304ms TTL=49
Reply from 204.14.17.162: bytes=32 time=256ms TTL=49
Reply from 204.14.17.162: bytes=32 time=183ms TTL=49
Minimum = 183ms, Maximum = 767ms, Average = 377ms
Reply from 204.14.17.162: bytes=32 time=1166ms TTL=49
Reply from 204.14.17.162: bytes=32 time=206ms TTL=49
Reply from 204.14.17.162: bytes=32 time=201ms TTL=49
Reply from 204.14.17.162: bytes=32 time=201ms TTL=49
Minimum = 201ms, Maximum = 1166ms, Average = 443ms
Reply from 204.14.17.162: bytes=32 time=322ms TTL=49
Reply from 204.14.17.162: bytes=32 time=206ms TTL=49
Reply from 204.14.17.162: bytes=32 time=220ms TTL=49
Reply from 204.14.17.162: bytes=32 time=212ms TTL=49
Minimum = 206ms, Maximum = 322ms, Average = 240msSsssh
No i think i do. I can't ever run a trace/ping on the poor server, as my college decided that anyone sing the CMd for web use MUST be a hacker... Or at least thats how the tech guy explained it.
FIZ wrote:QUOTE (FIZ @ Feb 28 2011, 04:56 PM) After Slap I use Voltaire for light reading.
QUOTE [20:13] <DasSmiter> I like to think that one day he logged on and accidentally clicked his way to the EoR forumCronoDroid wrote:QUOTE (CronoDroid @ Jan 23 2009, 07:46 PM) If you're going to go GT, go Exp, unless you're Gooey. But Gooey is nuts.
[20:13] <DasSmiter> And his heart exploded in a cloud of fury[/quote]
16 hops for me.
Average ping time: 132ms.
Average ping time: 132ms.
[img]http://www.freeallegiance.org/forums/st ... erator.gif" alt="IPB Image">
[url=http://pk.dras.us]
-
badpazzword
- Posts: 3627
- Joined: Thu Jan 12, 2006 8:00 am
- Contact:
Statistiche Ping per 204.14.17.162:
Pacchetti: Trasmessi = 100, Ricevuti = 91, Persi = 9 (9% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 136ms, Massimo = 409ms, Medio = 206ms
As for contributing, I am currently unable to do any paypal. When I'll be able, I'll buy Supporter (Plus?). I guess I will occasionally hand you those 15€.
Pacchetti: Trasmessi = 100, Ricevuti = 91, Persi = 9 (9% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 136ms, Massimo = 409ms, Medio = 206ms
As for contributing, I am currently unable to do any paypal. When I'll be able, I'll buy Supporter (Plus?). I guess I will occasionally hand you those 15€.
Have gaming questions? Get expert answers!


-
FingerBang
- Posts: 526
- Joined: Wed Jan 05, 2005 8:00 am
- Location: Winnipeg
heres me through a router then a VPN tunnel to calgary the over to ON.
Will post results from home later
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=68ms TTL=53
Reply from 204.14.17.162: bytes=32 time=78ms TTL=53
Reply from 204.14.17.162: bytes=32 time=95ms TTL=53
Reply from 204.14.17.162: bytes=32 time=75ms TTL=53
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 95ms, Average = 79ms
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.90.135.225
2 46 ms 28 ms 42 ms 10.90.7.4
3 26 ms 64 ms 27 ms 10.90.7.1
4 159 ms 81 ms 44 ms clgrabcoi01.enmaxenvision.net [72.29.232.206]
5 29 ms 27 ms 33 ms ra1so-ge3-2-4.cg.bigpipeinc.com [66.244.207.157]
6 43 ms 26 ms * rc1so-ge9-8.cg.shawcable.net [66.163.71.49]
7 61 ms 45 ms 59 ms rc2nr-pos13-0.wp.shawcable.net [66.163.76.86]
8 81 ms 47 ms 47 ms rc1sc-ge12-0-0.wp.shawcable.net [66.163.73.170]
9 82 ms 73 ms 77 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
10 112 ms 110 ms 85 ms rc2sh-pos15-0.mt.shawcable.net [66.163.66.14]
11 70 ms 92 ms 98 ms gw-ndcc.torontointernetxchange.net [198.32.245.6
9]
12 70 ms 71 ms 100 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Will post results from home later
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=68ms TTL=53
Reply from 204.14.17.162: bytes=32 time=78ms TTL=53
Reply from 204.14.17.162: bytes=32 time=95ms TTL=53
Reply from 204.14.17.162: bytes=32 time=75ms TTL=53
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 95ms, Average = 79ms
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.90.135.225
2 46 ms 28 ms 42 ms 10.90.7.4
3 26 ms 64 ms 27 ms 10.90.7.1
4 159 ms 81 ms 44 ms clgrabcoi01.enmaxenvision.net [72.29.232.206]
5 29 ms 27 ms 33 ms ra1so-ge3-2-4.cg.bigpipeinc.com [66.244.207.157]
6 43 ms 26 ms * rc1so-ge9-8.cg.shawcable.net [66.163.71.49]
7 61 ms 45 ms 59 ms rc2nr-pos13-0.wp.shawcable.net [66.163.76.86]
8 81 ms 47 ms 47 ms rc1sc-ge12-0-0.wp.shawcable.net [66.163.73.170]
9 82 ms 73 ms 77 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
10 112 ms 110 ms 85 ms rc2sh-pos15-0.mt.shawcable.net [66.163.66.14]
11 70 ms 92 ms 98 ms gw-ndcc.torontointernetxchange.net [198.32.245.6
9]
12 70 ms 71 ms 100 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Last edited by FingerBang on Tue Jan 23, 2007 5:41 pm, edited 1 time in total.
ASGS logs wrote:Harold3(7): FINGERBANG GET OUT FROM BEHIND THAT WORMHOLE AND FIGHT LIKE A MAN YOU @&%#! CHICKEN
CODEping -n 20 tigereye.ca
Pingen naar tigereye.ca [204.14.17.162] met 32 byte gegevens:
Antwoord van 204.14.17.162: bytes=32 tijd=111 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=106 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=103 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=110 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=106 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=105 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=113 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=108 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=107 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=109 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=108 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=103 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=103 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=106 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=108 ms TTL=52
Ping-statistieken voor 204.14.17.162:
Pakketten: verzonden = 20, ontvangen = 20, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
Minimum = 103ms, Maximum = 113ms, Gemiddelde = 106ms
from the Netherlands. I get on average a ping of 80 to the planet servers, this one seems worse for me.
Pingen naar tigereye.ca [204.14.17.162] met 32 byte gegevens:
Antwoord van 204.14.17.162: bytes=32 tijd=111 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=106 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=103 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=110 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=106 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=105 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=113 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=108 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=107 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=109 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=108 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=103 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=103 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=104 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=106 ms TTL=52
Antwoord van 204.14.17.162: bytes=32 tijd=108 ms TTL=52
Ping-statistieken voor 204.14.17.162:
Pakketten: verzonden = 20, ontvangen = 20, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
Minimum = 103ms, Maximum = 113ms, Gemiddelde = 106ms
from the Netherlands. I get on average a ping of 80 to the planet servers, this one seems worse for me.

Snack, something's definitely wrong with the route between hungary and germany there. Look at the drastic leap between hops 6 and 7!Snack wrote:QUOTE (Snack @ Jan 23 2007, 02:52 AM) Hmm, probably the worst server I have been to. :/
Craps out on that 6th 7th hop...
CODE
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 268 ms 1 ms 1 ms SE515.home [192.168.222.1]
2 18 ms 17 ms 14 ms bdr03.ip.t-com.hr [172.29.252.36]
3 1032 ms 15 ms 15 ms 172.29.1.177
4 27 ms 15 ms 15 ms gdr01-gdr02-ge.ip.t-com.hr [195.29.252.198]
5 21 ms 13 ms 15 ms gtr01-gdr01.ip.t-com.hr [195.29.240.30]
6 20 ms 23 ms 20 ms 212.184.27.29
7 709 ms 925 ms 610 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
8 250 ms 910 ms 854 ms 217.6.24.194
9 425 ms 330 ms 330 ms tigereye.ca [204.14.17.162]
Hopefully whatever company is managing that router fixes that because that's nasty!
MrChaos likely has something similar going on in Michigan. MrC- can you post the full traceroute? 1116ms is damned long and it looks like something's screwing up along the way. I hope it's something inbetween and not the server itself.
Full traceroutes help identify what route everyone is taking to that server so I can assess if it's well-connected or not. Posting the last line doesn't tell me any more than a ping.
As far as payments - don't even worry about it for now. I just wanted to see *IF* there was a small handful of people who would pass a few bucks every now and then to help lighten the load. I can bear the full load for a bit, but not forever. If there are people to help skim the top then it's definitely a lot more doable.
Thanks for the feedback so far, guys. It's helping me make an informed decision.
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.

