Bug? Immediate time-out

This just happened to me as well.
What's going on?

Same thing here:
http://de.lichess.org/n9duOTrOYLAA
http://de.lichess.org/1FWaxWgC1Ue1
http://de.lichess.org/2D4vkVfWBscr
Black won on time after first move.

In this game, I had a win on time with white although my opponent should've had time left:
http://de.lichess.org/BAi553ngSIlv

Glad to notice it's happening to everyone, I assumed it was one user who was cheating by exploiting the code or something.

I had it happen in my last game as well.

Same thing here:
http://de.lichess.org/n9duOTrOYLAA
http://de.lichess.org/1FWaxWgC1Ue1
http://de.lichess.org/2D4vkVfWBscr
Black won on time after first move.

In this game, I had a win on time with white although my opponent should've had time left:
http://de.lichess.org/BAi553ngSIlv

Same here: http://en.lichess.org/10P9m2jw

A fix is in the way.

WebSocket log from a timed out game:

{"t":"b","d":[{"v":1,"t":"crowd","d":{"white":false,"black":true,"watchers":[]}}]}
{"t":"following_onlines","d":{}}
{"t":"following_onlines","d":[]}
{"t":"b","d":[{"v":2,"t":"crowd","d":{"white":true,"black":true,"watchers":[]}}]}
{"t":"b","d":[{"v":3},{"v":4,"t":"possibleMoves","d":{"f7":"f6f5","g8":"f6h6","g7":"g6g5","b7":"b6b5","e7":"e6e5","b8":"a6c6","h7":"h6h5","d7":"d6d5","c7":"c6c5","a7":"a6a5"}},{"v":5,"t":"state","d":{"color":"black","turns":1}},{"v":6,"t":"move","d":{"type":"move","from":"h2","to":"h4","color":"white"}},{"v":7,"t":"premove","d":null},{"v":8,"t":"clock","d":{"white":300.0,"black":300.0}}]}
{"t":"move","d":{"from":"c7","to":"c5","b":0,"lag":22}}
{"t":"ack"}
{"t":"b","d":[{"v":9},{"v":10,"t":"possibleMoves","d":null},{"v":11,"t":"state","d":{"color":"white","turns":2}},{"v":12,"t":"move","d":{"type":"move","from":"c7","to":"c5","color":"black"}},{"v":13},{"v":14,"t":"clock","d":{"white":300.0,"black":300.0}},{"v":15},{"v":16,"t":"reloadTable","d":null}]}
{"t":"b","d":[{"v":17,"t":"end","d":null},{"v":18,"t":"clock","d":{"white":0.0,"black":300.0}}]}

That should say "first move" up above.

issue solved?

Yes, the bug is fixed now. Sorry all for the inconvenience.