Page 3 of 5

Posted: Thu Jan 07, 2010 3:41 pm
by kramari
Mryddlin wrote:QUOTE (Mryddlin @ Jan 7 2010, 02:33 PM) note to self: Turn off bittorrent before playing!

Last night was good on planet2 for me (once I released I have the torrents running and shut it down).

I did this once and cursed my ISP then I remembered that torrent was running.

Posted: Fri Jan 08, 2010 3:51 pm
by Jeruwafi
FYI my pings to GPZ went back to normal... for now...
so between Dec 20th and today something was wrong with routing and it's a recurring problem ;]

Posted: Sun Jan 10, 2010 6:28 pm
by MrChaos
Jeruwafi wrote:QUOTE (Jeruwafi @ Jan 8 2010, 09:51 AM) FYI my pings to GPZ went back to normal... for now...
so between Dec 20th and today something was wrong with routing and it's a recurring problem ;]
I think this is an issue across all the severs Jeru

There were days around the christmas holidays when Planet was pretty much unplayable for me but the pings appeared to be fine... :unsure: why. It has been back to normal last few times Ive hopped on.

Ive already mentioned that Solap's performance was horrible lately too, so I am not bashing Planet2. Rather Im wondering if the intertubes needed a flushing or there is something else going on... what I have not a clue.

Posted: Sun Jan 10, 2010 6:33 pm
by sgt_baker
Where does the excrement go when you flush teh intertubes?

Food (euch) for thought.

Posted: Sun Jan 10, 2010 6:37 pm
by Jeruwafi
QUOTE I think this is an issue across all the severs[/quote]
Internet is failing? :-)

I've noticed unstable behaviour on other servers as well but GPZ's problems are the only that are easy to pinpoint.. not to mention my "workaround" which indicates specific problem in specific place :-)

Posted: Sun Jan 10, 2010 6:43 pm
by pkk
Jeruwafi wrote:QUOTE (Jeruwafi @ Jan 10 2010, 07:37 PM) Internet is failing? :-)
Someone dropped the internet...
Jeruwafi wrote:QUOTE (Jeruwafi @ Jan 10 2010, 07:37 PM) I've noticed unstable behaviour on other servers as well but GPZ's problems are the only that are easy to pinpoint.. not to mention my "workaround" which indicates specific problem in specific place :-)
It's like I said before, I can't fix routings off your ISPs.

Posted: Sun Jan 10, 2010 6:49 pm
by theTroy
pkk wrote:QUOTE (pkk @ Jan 10 2010, 10:43 AM) Someone dropped the internet...


It's like I said before, I can't fix routings off your ISPs.

This isnt routing off my ISP, this is routing near the GPZ server (last few tracert lines, where the trace is already not even in my country, but rather on the server's routing).

As I already mentioned above, I own a server in Amsterdam, and it works perfectly fine for me.

Thank you kindly for looking into the problem ;)

Edit : btw, the issue in the last few days was a bit better, not sure whether its just me, but I will test it regularly for a few days.

Posted: Tue Jan 12, 2010 8:39 am
by Jeruwafi
QUOTE It's like I said before, I can't fix routings off your ISPs.[/quote]
Saying it's our ISP is wrong ;p
3 people from 3 different countries, 2 different continents are routed via "217.118.121.134" where problem most likely occurs. It would be safe to assume it's part of GPZ's hoster ISP. True, you can't fix it, but whoever you pay for gpz can yell at whoever they pay and it might get fixed. right? :)

Posted: Tue Jan 12, 2010 8:25 pm
by parcival

Code: Select all

C:\>ping server.german-borg.de

Pinging server.german-borg.de [84.243.253.92] with 32 bytes of data:

Reply from 84.243.253.92: bytes=32 time=155ms TTL=114
Reply from 84.243.253.92: bytes=32 time=151ms TTL=114
Reply from 84.243.253.92: bytes=32 time=155ms TTL=114
Reply from 84.243.253.92: bytes=32 time=154ms TTL=114

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

C:\>tracert server.german-borg.de

Tracing route to server.german-borg.de [84.243.253.92]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    30 ms    30 ms    30 ms  bbras-llu-kln-08L0.forthnet.gr [194.219.231.70]
  3    31 ms    31 ms    31 ms  core-kln-01-Gi6-0-0.forthnet.gr [62.1.37.129]
  4   134 ms   135 ms   137 ms  212.162.9.141
  5   146 ms   141 ms   140 ms  vlan89.csw3.Frankfurt1.Level3.net [4.68.23.190]
  6   135 ms   138 ms   139 ms  ae-72-72.ebr2.Frankfurt1.Level3.net [4.69.140.21]
  7   143 ms   133 ms   132 ms  ae-2-2.ebr1.Dusseldorf1.Level3.net [4.69.132.137]
  8   134 ms   137 ms   145 ms  ae-1-100.ebr2.Dusseldorf1.Level3.net [4.69.141.150]
  9   143 ms   143 ms   141 ms  ae-2-2.ebr1.Amsterdam1.Level3.net [4.69.133.89]
 10    93 ms    93 ms    94 ms  ae-12-51.car2.Amsterdam1.Level3.net [4.69.139.131]
 11   149 ms   151 ms   150 ms  212.72.48.162
 12   152 ms   152 ms   150 ms  Gi6-0-0.ams-koo-access-1.interoute.net [212.23.41.134]
 13   141 ms   141 ms   142 ms  PO10-0.rtm-vla-access-1.interoute.net [212.23.41.205]
 14   152 ms   152 ms   149 ms  217.118.121.134
 15   152 ms   151 ms   150 ms  rtr-1.ams-tc2.grafix.nl [217.67.247.1]
 16   147 ms   153 ms   142 ms  server.german-borg.de [84.243.253.92]

Trace complete.

Posted: Thu Jan 14, 2010 8:18 am
by Zapper
If you have a hvy lag, restart windows and reconnect and the lag is gone.