EASTCOAST: issue suggestion

deant
deant Posts: 1 Arc User
edited May 2011 in Support Desk
here is what i posted on another thread:
my ip is: 77.78.31.7
pls chack it if possible:

the problem is somewhere in the midddle, between our ISP and the pwi servers. i DC alot on all east coast servers, but have no problems at west coast ones. so here is the traceroute:

root@named:~# traceroute -n 74.201.183.68
traceroute to 74.201.183.68 (74.201.183.68), 30 hops max, 60 byte packets
1 212.25.32.1 0.414 ms 0.369 ms 0.340 ms
2 212.25.58.1 0.553 ms 0.563 ms 0.629 ms
3 94.156.251.137 0.817 ms 0.808 ms 0.737 ms
4 67.17.157.61 9.319 ms 9.393 ms 9.460 ms
5 67.17.108.246 161.157 ms 161.042 ms 161.094 ms
6 67.17.192.54 160.832 ms 160.872 ms 160.852 ms
7 216.52.95.9 159.650 ms 216.52.95.73 159.503 ms 216.52.95.9 159.590 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 *^C

after that here is the ping report:

PING 216.52.95.9 (216.52.95.9) 56(84) bytes of data.


--- 216.52.95.9 ping statistics ---
58 packets transmitted, 28 received, 51% packet loss, time 57275ms
rtt min/avg/max/mdev = 161.458/168.403/348.455/34.655 ms

whois info:

root@named:~# whois 216.52.95.9

Internap Network Services Corporation PNAP-8-98 (NET-216-52-0-0-1) 216.52.0.0 - 216.52.255.255
InterNAP Network Services, PNAP-NYM PNAP-NYM-INAP-BB-1 (NET-216-52-94-0-1) 216.52.94.0 - 216.52.95.255


all connection going trough this ip are bad. i hope someone else notices that
Post edited by deant on

Comments

  • HeaIy - Raging Tide
    HeaIy - Raging Tide Posts: 9 Arc User
    edited May 2011
    I'm having the same problem at the same node when tracert (I think I talked to you yesterday on an alt when you WC'ed about this problem in Raging Tide). I submited a ticket, no reply, I asked on another topic, they told me to restart my computer (geeez...thanks). Also I don't have any problems logging on West Coast servers, sad part is i don't have any chars on West coast servers..

    My tracert:

    Tracing route to pwieast3.perfectworld.com [74.201.183.67]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 86.104.41.1
    2 <1 ms 1 ms 1 ms bbRhv-ge129-v250-ilink-pronet3.b.ipv4ilink.net [
    86.55.20.85]
    3 1 ms 1 ms 1 ms bbUnr-ten84-v25-bbRhv.b.ipv4ilink.net [193.19.19
    4.53]
    4 1 ms 1 ms 1 ms bbNx-ten15-v19-bbUnr.b.ipv4ilink.net [193.19.194
    .86]
    5 1 ms 1 ms 1 ms iNx-ten150-v20-bbNx.b.ipv4ilink.net [193.19.194.
    209]
    6 25 ms 2 ms 2 ms wNx-Po3-v701-iNx.b.ipv4ilink.net [193.19.194.89]

    7 8 ms 14 ms 1 ms 209.130.173.109
    8 33 ms 36 ms 33 ms xe1-3-2-10G.scr4.FRA4.gblx.net [67.16.143.14]
    9 303 ms 197 ms 191 ms po3-40G.ar4.NYC1.gblx.net [67.17.108.246]
    10 126 ms 118 ms 117 ms 67.17.192.54
    11 191 ms 118 ms 117 ms border1.pc1-bbnet1.nyj001.pnap.net [216.52.95.9]

    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 *
  • deant
    deant Posts: 1 Arc User
    edited May 2011
    yes we talked about it. and i think the problem is on previous node: 67.17.192.54

    my frend form another ISP traced 216.52.95.9 and he had different route to it. he doesnt have DC issues. i dont know which ISP holds 67.17.192.54 but the problem is definetly there. and i`m not sure what pwi can do about it since they dont own it. b:sadb:sad
  • SylenThunder - Twilight Temple
    SylenThunder - Twilight Temple Posts: 7,908
    edited May 2011
    Unfortunately, there's not a lot that you, or PWI can do about it. you just have to wait till the routers correct the load-balancing issue or adjust to a different route.
    [SIGPIC][/SIGPIC]
  • Deant - Raging Tide
    Deant - Raging Tide Posts: 143 Arc User
    edited May 2011
    yp lets hope its sooner than later
  • sunshine4u
    sunshine4u Posts: 8 Arc User
    edited May 2011
    bump..fix this please

Categories