Session timed out

It's been doing this all day for me, those of you on Samsung Galaxy S II, what ROM are you on. I'm on latest CyanogenMOD Nightly.

On server 83, I reinstalled the app, same issue.

Same here. I am using galaxy s2. I am facing session timeout error and network connection issue. I this happen to me right before I stated the fort attack. I couldn't login and it said session timeout after I login. Finally I lost all of the inf, cav and arc. The only troop I left is cats. But now I am having problem maintaining it. As I dont have inf and cav to carry res from the fort. I may starve my cats too. It sucks!!! Anyone can help?

It's not just the phone. It's definitely a traffic problem as iPhones are doing the same thing. The servers are slow intermittently and problems with logins are very sporadic. Keep trying over and over and finally you can make it in, if you catch it during a good time. This is the second time today this has been happening.

It is starting to affect the S1 as well.

it is affecting all people on all servers on all devices
sorry I can't elaborate more

Thus is happening on my Galaxy S on Rogers and my girlfriends LG Optimism One on Choosing, I tested on her phone with a new user.

After two days of this glitch ive watched a ton of people have troops starve including myself:( no pres lost but its getting difficult to enjoy the game

The server crashes and timeouts are causing players to lose faith in haypi altogether. I'm a paying customer, and cannot get any repayment of lost troops! It's absurd to treat customers this way!! There's nothing wrong with my device or my internet connection. HAYPI secure your servers!!!

It's best to keep screenshots of your army... just in case. Support would need a copy of this in case it happens again.

This seems like the attacks are happening due to an anniversary of a certain organization.

Just push through the lag, and you'll be able to get back on.

The samething is happening to me try to do any thing I get timedout. All mine lvels haven been set back to 0. This is on server 79