I do believe that the event was programmed by the siteowner to end at this particular time. And he's away at the moment so he couldn't alter the coding to make it last longer.