Recently especially from 5pm EST on, the app either doesn’t load or takes forever. And if it loads, it’s only a partial load of the app. Bottom line, Tablo is not providing enough server capacity during peak times (in the evenings). This is easy to see when you compare the quick load times of the app in the AM versus the long evening loads.
Can you ramp up server capacity to improve the customer experience? If not, this will kill your customer base and potentially your entire business.
You bring up a good point, which I just connected to my experience of delayed application startup at night (I’m on the East Coast).
What is not clear is after connection (solid blue light), what other interactions with the Tablo servers are involved (e.g. loading application, playing content); such interactions would explain delayed loading and buffering due to server bandwidth issues.
I’ve posed this question to this forum but no response (I guess everyone is in the dark on this topic).
Tablo Support: can you weigh in on this. Thank you.
We’ve been out of town since Fri, 8/15 to last night but, ya, we saw this sporadically in the early evenings beginning early last week in the CDT zone. Thankfully it was only 30 sec or less of Spinning Wheel, Got To Go Round.
EDIT: that’s funny - after I was done typing and submitted this I looked up and saw a “Timeout waiting for video data” error. Retry cleared it and it’s back up and running again. This isn’t something we typically see, but it just occured 4x within 10-11 minutes.
Tablo Support: After initial connection (solid blue light), what other interactions with the Tablo servers are involved (e.g. loading application, playing content)? Please respond.
This is an ongoing issue for me. For about 1500-1900 PDT at the beginning of every hour for about 10-15 minutes the Tablo will not work. Then it will start acting normally. The errors I get will be cannot connect to Tablo, blank channel guide, or errors when I try to select a channel. I have gen 4 Tablo and a Roku Ultra. This has been going on since before the July 27 crash.
“Watching free streaming channels, guide data, and firmware updates also require a server connection”. I think the Tablo server interaction goes well beyond that.
As mentioned, application loading and startup vary during the day, indicating server dependence.
Display of guide data (not just guide updating) is also an issue. You would think that the guide data is locally cached, but the lagging display of guide information indicates otherwise.
This significant interdependence on server availability and bandwidth for proper Tablo function may be the reason the “offline mode” is difficult to implement (server and Tablo device are too intertwined).
If this is true, the user community should be advised of both server bandwidth and server down status.
I’m still awaiting a response from Tablo support on this.
