Loading issue of Kixeye games on Facebook

[#1]

I am wondering if anyone else is having problems loading games from Kixeye via facebook using there broadband connection. If we try via either wired or wireless home connection the games will not load. I have checked all settings on the 3 computers in our house and there is no issue with any other sites and other games via facebook seem to load ok. The really strange thing is if I tether either my windows or apple laptops to my mobile phone connection the games will launch. Does anyone have any ideas as to the reason behind this as have tried flash updates/ removal etc to no avail. I cant see its a problem with setings on computers as the games will load as mentioned via 3G tethered connection.

[#2]

I am having same problem someone mentioned it may be fault lies with your isp blocking return path of info packets,can anyone help?

[#3]

Further update after looking at forums again and plusnet is cropping up a lot now so looks like its them causing the problem with something they may have changed recently,come on guys lots of knowledge on here someone must be able to help.

[#4]

Good afternoon Guys n Gals,
I'm very sorry to hear that you are experiencing this problem, rest assured, it appears to be a common accurence with a few other customers who have reported a similar issue with the Kixeye games.
Whilst it is a bank holiday today, I can't say that this will be looked into as a priority, but we are collating as much information and as many examples of this as possible. The more we get, the better case we have for calling the big guns out to have a look into it.
Worst case scenario is that it doesn't get looked into till tomorrow morning (by which time it could no doubt rectify it's self).
From what I can fathom so far there does appear to be a routing issue within the network and it's preventing the connections from being made.
Please accept my apologies for any inconvenience this is causing you.

[#5]

Thx for answer matt we wait your response.

[#6]

Good evening,
For awareness, this has been raised as problem number 72561
Our networks team will most likely pick this up in the morning.
Here's to hoping it fixes it's self before then
Cheers,
Matt

[#7]

I haven't been able to access www.pclinuxos.com (199.231.58.82) today.

$ tracepath www.pclinuxos.com
 1:  master.local                                          0.271ms pmtu 1500
 1:  dsldevice.lan                                        13.464ms 
 1:  dsldevice.lan                                        96.584ms 
 2:  lo0-central10.ptw-ag01.plus.net                      63.880ms asymm  3 
 3:  link4-central10.ptw-gw02.plus.net                    62.065ms asymm  6 
 4:  xe-0-2-0.ptw-cr02.plus.net                          114.281ms asymm  5
 5:  te9-4.ptn-gw02.plus.net                              62.244ms asymm  7 
 6:  po4.ptn-gw01.plus.net                                62.632ms asymm  5 
 7:  195.99.126.144                                       62.965ms asymm  9 
 8:  core2-te0-15-0-14.ilford.ukcore.bt.net               64.768ms asymm  7 
 9:  core2-pos9-1.telehouse.ukcore.bt.net                 66.971ms asymm 10 
10:  t2as2-tge1-4.uk-lon1.eu.bt.net                       63.863ms asymm 11 
11:  no reply
...
31:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500 

I presume this is part of the same problem and I hope this information helps.

[#8]

Hey,
Yep, This appears to be part of the same issue.
I've done a traceroute from home - on Ask4 and got the below:

traceroute to www.pclinuxos.com (199.231.58.82), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1)  0.088 ms  0.082 ms  0.091 ms
 2  ac4-ppp.dr.ask4.net (81.23.59.244)  18.701 ms  18.714 ms  18.712 ms
 3  br1-ac.dr.ask4.net (81.23.57.1)  18.932 ms  18.945 ms  18.943 ms
 4  dc1-xmr.dr.ask4.net (81.23.57.17)  19.326 ms  19.408 ms  19.553 ms
 5  10ge-3-2.thn-xmr.thn-w1.core.ask4.net (81.23.51.241)  32.626 ms  32.638 ms  32.856 ms
 6  83.231.235.197 (83.231.235.197)  23.877 ms  22.435 ms  22.833 ms
 7  ae-4.r22.londen03.uk.bb.gin.ntt.net (129.250.5.24)  22.729 ms  22.723 ms  22.712 ms
 8  as-0.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.254)  93.884 ms  93.897 ms  90.379 ms
 9  ae-4.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.51)  193.838 ms  163.075 ms  193.846 ms
10  ae-0.r20.sttlwa01.us.bb.gin.ntt.net (129.250.2.53)  176.505 ms  176.513 ms  176.303 ms
11  ae-5.r21.snjsca04.us.bb.gin.ntt.net (129.250.3.39)  186.045 ms  180.044 ms  198.704 ms
12  ae-2.r06.snjsca04.us.bb.gin.ntt.net (129.250.5.55)  178.906 ms  186.970 ms  188.184 ms
13  xe-0-0-0-4.r06.snjsca04.us.ce.gin.ntt.net (128.241.219.130)  189.405 ms  196.248 ms  190.469 ms
14  border1.t7-1-bbnet1.sje.pnap.net (66.151.144.4)  186.448 ms border1.t8-1-bbnet2.sje.pnap.net (66.151.144.68)  196.782 ms border1.t7-1-bbnet1.sje.pnap.net (66.151.144.4)  184.759 ms
15  enkillc-1.border1.sje.pnap.net (74.201.124.202)  191.351 ms  189.103 ms  186.701 ms^C

Seems there is an issue between the BT network and pnap.net
All affected sites so far have been on pnap.net
Thanks for the further information.
Cheers,

[#9]

So is that your end or kixeye's end?

[#10]

It's hard to say at this stage,
It's more likely to be somewhere with BT's network.
It's as if USA has dropped off the map for them, to this particular location... But it's not affecting all USA traffic, it's very bizarre.
Our Operations team have been left a message for when they arrive tomorrow morning and hopefully the issue can then be resolved, or at least on the way to be resolved.
Regards,

[#11]

Thx again matt.

[#12]

Im having the same Kixeye issue, it started yesterday morning right in the middle of a War Commander event which I was doing rather well at 
tracert wc-fb4.cdn.kixeye.com
Crapped out after this hop:
10    77 ms  204 ms  209 ms  166-49-214-149.eu.bt.net [166.49.214.149]
11    *        *        *    Request timed out.
Raised a support ticket with Kixeye who suggested it was my ISP, raised a support ticket with Plusnet but still awaiting reply.
I hope this is fixed soon or I will lose all my event points

[#13]

All 'broken' sites seem to be back up again! 
Nice job!

[#14]

Yes, it's working again. Thanks to whoever dug up the cable and tied it back together!

[#15]

Hey Guys,
Glad to hear that all is working again!
Not sure what happened over night, but whatever did happen seemed to fix the problem
Enjoy the rest of your day,
Matt