I tried syncing a client on my computer from mid march and so far it seems to sync until block 277934 and 277940 :
Height Date Amount Fee Nr TX Generator Payload Base Target
277940 4/7/2015 22:44:05 0 0 0 NAS-VBK9-5ZXA-CJQ8-GEWVU 0 B 1266 %
277939 4/7/2015 22:44:00 0 0 0 NAS-VBK9-5ZXA-CJQ8-GEWVU 0 B 2531 %
277938 4/7/2015 22:43:58 0 0 0 NAS-VBK9-5ZXA-CJQ8-GEWVU 0 B 5062 %
277937 4/7/2015 22:43:46 0 0 0 NAS-VBK9-5ZXA-CJQ8-GEWVU 0 B 10124 %
277936 4/7/2015 22:43:23 0 0 0 NAS-VBK9-5ZXA-CJQ8-GEWVU 0 B 20249 %
277935 4/7/2015 22:43:22 1'000 1 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 160 B 40498 %
277934 4/5/2015 16:01:21 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 20249 %
277933 4/5/2015 16:00:19 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 19596 %
Blocks after 277934 appearing and dissapearing ...
Very strange thing and it seems we have, again(sigh) a messed up network.
So your client is stuck where my nodes are. That means that the blocks creating the longer chain contain something bad that those nodes accepted for some unknown reason.
If a new node is stuck at the same spot as my nodes then chances are we won't be fixing my nodes to reach patapato's block height. We could try re-syncing again with my nodes shut down to see what happens but that might make things worse for the network.