>>/18324/
Does it always do this? Or did it eventually go through? My best guess is a backend restart or a captcha expired.