network issues

[starLivitation]

so i live in middle east ( jordan ). today i had some wierd lag and some disconects. although i suspected somethign with my ISP since teamspeak also droped, later on i felt it was a routing issue , while the lag continued the teamspeak and other internet functions continued normally.

if someone can tell me what is going on. i given up for today , lets see if tomorerow this is fixed

trace route to the new server Odin

Tracing route to 195.82.50.54 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    39 ms    15 ms    14 ms  bng-hq.go.com.jo [194.165.130.202]
  3    15 ms    15 ms   193 ms  10.50.6.9
  4    15 ms    15 ms    15 ms  213.139.50.9
  5    15 ms    28 ms    15 ms  213.139.51.5
  6    75 ms    79 ms    79 ms  81.52.188.223
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    90 ms    96 ms     *     KDDI-DEUTSC.edge5.Frankfurt1.Level3.net [212.16
.4.98]
 10    90 ms    90 ms    89 ms  195.82.60.29
 11    89 ms    90 ms    90 ms  195.82.61.14
 12     *       90 ms    90 ms  195.82.50.234
 13   124 ms    92 ms    89 ms  195.82.50.54

i see 2 IPs, being chozen then, it times out to them...

if i do a normal ping test, it also times out 1 out of 10 or so this example :

Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=89ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=89ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=92ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=110ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=105ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Request timed out.
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=114ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=98ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Reply from 195.82.50.54: bytes=32 time=90ms TTL=52
Reply from 195.82.50.54: bytes=32 time=91ms TTL=52
Request timed out.
Request timed out.

[JedahJohnny]

Orange ISP problem and Square Enix must do something!

http://forum.square-enix.com/ffxiv/t...63#post3382063
http://forum.square-enix.com/ffxiv/t...57#post3382057
http://forum.square-enix.com/ffxiv/t...03#post3381603
http://forum.square-enix.com/ffxiv/t...92#post3381492

[starLivitation]

i did a pathping to 195.82.50.54 just now and, i got this result

  1  192.168.1.1
  2  bng-hq.go.com.jo [194.165.130.202]
  3  10.50.6.9
  4  213.139.50.9
  5  213.139.51.5
  6  81.52.188.223
  7     *        *        *
Computing statistics for 150 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           akram [192.168.1.132]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2   30ms     0/ 100 =  0%     0/ 100 =  0%  bng-hq.go.com.jo [194.165.130.202]

                                0/ 100 =  0%   |
  3   17ms    93/ 100 = 93%    93/ 100 = 93%  10.50.6.9
                                0/ 100 =  0%   |
  4   18ms     0/ 100 =  0%     0/ 100 =  0%  213.139.50.9
                                0/ 100 =  0%   |
  5   18ms     0/ 100 =  0%     0/ 100 =  0%  213.139.51.5
                                0/ 100 =  0%   |
  6   76ms     0/ 100 =  0%     0/ 100 =  0%  81.52.188.223

i see packet loss on 10.50.6.9, so i looked it up. it says this "is a bogon or private IP address that should not appear on the Internet."

so i dont know what that means i checked google and found this https://en.wikipedia.org/wiki/Bogon_filtering

does this make sense to anyone? could this be my problem?

[worldofneil]

10.* is an internal IP yes.

Never seen one like that in the middle of a route (where it's already going over the Internet), but 194.165.130.202 (the hop before) is owned by your ISP (Jordan Telecom) and the hop after (213.139.50.9) is also owned by them so it would figure that internal 10 address is owned by them too. it's a problem in their network and you'd need to talk to your ISP about it and give them this information.

[Raist]

It is reporting a reserved IP on your ISP's network. I get that sometimes within TWC as well, usually at the CMTS in the cable plant.

Looks like you've got some weirdness within Orange's own network trying to get out of Jordan that they need to investigate. May want to generate some reports to the lobby server (neoloby06.ffxiv.com) and submit a formal ticket with Orange about your packet loss and lag spikes, requesting their Tier3/Engineering team looks into it.

The peering carrying people into KDDI (SE's ISP) doesn't appear to be prepared for the increased data flow yet either, and some tweaking needs to be done there as well. Your ISP established the agreements on your side of the equation (like the France Telecom and level3 segments--your ISP's policies sent you there, not SE). Things appear to be going haywire at the exchanges prior to where SE's influence could take hold, so your ISP should be the first people to look into the matter, and then KDDI from their end if it persists closer to their exchange points.

[starLivitation]

just called my ISP with information above, unfourtinatly, they refused to send this information to tier3 support.... the generic reply i got, ur connection is working, maybe we need to replace the modem or router u got with the newer version. perks of living in a 3rd world country...


do u guys possibly think wtfast can fix this? the last 2 days, i got heavy lag unplayable in savage.....it was fine just 1 day before this incident... thats only durring 6 to 10 PM. Server time this is happening...