According to Deadline, overwhelming demand to watch the episode during the East Coast airing caused an HBO Now overload crash from 9 PM and 10 p.m ET, leaving more 15,000 would-be users hungrier than Ramsay's hounds.
HBO Now addressed the outage in a tweet marked 9:43 p.m., then updated at 10:12 p.m. that it was fixed.
We're aware members are experiencing technical difficulties tonight. We hope to resolve this ASAP. Please follow @hbonowhelp for updates.
— HBO NOW (@hbonow) June 20, 2016
We are pleased to confirm that successful streaming has resumed across all devices.
— HBO NOW (@hbonow) June 20, 2016
If you still experience trouble, please DM @HBONOWhelp.
But oh man did they take a beating before, during, and after those tweets (just look at the replies), with some users saying it still wasn't working for them; others threatening to cancel their services after that night; others wanting refunds; still others saying it didn't matter anymore 'cause the episode had been spoiled online by the time they got to see it; and at least one noting that maybe they should've apologized at least once for the inconvenience.
Best moment of season six , you deserve it ππΌπ #GameofThrones #got http://pic.twitter.com/04EPkpcnqh
— Haifaa ⚔ (@HaifaaAlweteid) June 20, 2016
Yes, fans take their TV shows very seriously, but if you're paying for a service to work when you need it, 9 p.m. for East Coasters was exactly when they needed it, so you can understand the frustration. (The service costs $14.99 per month for access to HBO's shows without a cable subscription.) However, other users said their service worked just fine, so they clearly won the Game of Thrones and the others ... well, you know what happens to the losers.
Want more stuff like this? Like us on Facebook.
from Moviefone News RSS Feed - Moviefone.com http://ift.tt/28JAmum
via IFTTT
No comments:
Post a Comment