Non-league side produce arguably the greatest technical difficulty in livetweeting history

When livetweeting football matches goes wrong right.

One of Sleaford Town FC's updates for their United Counties League Premier Division clash against Boston Town is quickly gathering up the interactions on Twitter, for a very good reason. However, if we give you the punchline straight away, the joke will die quicker than ambition in the midlands. The game was livetweeted by Sleaford’s official account, and began just like any other Twitter commentary of a football game - with the team news. https://twitter.com/SleafordTownFC/status/714451808178073601 Lineup done, then it was time to bring the game to life, through the power of 140 character maximum updates. Sleaford began dominating the action and racking up the goals. https://twitter.com/SleafordTownFC/status/714453542292074496 https://twitter.com/SleafordTownFC/status/714460425232977921 https://twitter.com/SleafordTownFC/status/714461484781334529 With the first half in the bag, Sleaford decided to not make any substitutions at the break, while the trailing Boston brought on one pair of fresh legs. https://twitter.com/SleafordTownFC/status/714463813484019713 https://twitter.com/SleafordTownFC/status/714467280889970688 Boston managed to pull one back to bring the scoreline to 3-1 and then something strange happened with the commentary. https://twitter.com/SleafordTownFC/status/714469177365557249 Straight after Boston’s goal, the updates dried up and Sleaford's timeline became extremely quiet. Exactly one hour passed before the next update, which explained exactly why the livetweeting had ceased. https://twitter.com/SleafordTownFC/status/714483538213646336 Incredible.