By default we shape on protocols, not per specific site unless something out of the ordinary is required. So as long as that Vevo app connects to the right backend servers and delivers content in the correct streaming format, it will be fine. What we see is that the apps guys build for specific products (Apple and Samsung are particular culprits here) is that they route the request via their servers so that they can monitor who is doing what on their products at all times, rather than simply relaying the request to the streaming servers directly. So when they have issues on these servers, so do you, and the very easy test here is to see if Vevo works in a browser at the same time. If it's working on a browser but not your media device, then it's very difficult for us to do anything about it, as we can't be sure if that server is under strain, their peering is working correctly with their own partners, or a plethora of other reasons. Troubleshooting that sort of thing can be quite a frustrating process from our side, but frustration doesn't deter us from helping out. Happy to take a look if you next experience this, so when it happens come talk to live support and we'll see how it is routing to investigate properly for you.