In this guide, we will be discussing some plausible methods to fix the BritBox is not currently available in your country error. This online digital video subscription service has firmly established its dominance in the UK, US, Canada, Australia, and South Africa. Mainly focusing on British television series and films, you could treat yourself to content from BBC, ITV, Channel 4, and Channel 5.
Apart from that, it also has its own contents lined up as well. However, not many users are able to enjoy these contents due to a weird issue that has suddenly popped up. Various users have voiced their concern that they are now getting an error message which states that this service is not available in their regions, when in fact it is supported. The issue seems to be more prominent in the US and Australia.
It has first made its way on the 5th of February and is still going strong. Moreover, it isn’t limited to any particular device, as the likes of Amazon Firestick, Roku, and Samsung TV are also currently bugged with this error. If you are also on the same page, then this guide shall help you out. In this tutorial, we will be looking at some workarounds that might help you fix the BritBox is not currently available in your country error.
How to Fix BritBox is not currently available in your country
Do note that this is a server-side error and the
developers haven’t yet acknowledged this issue [check the update below], let alone release a fix. In the meantime, you could try uninstalling the app and then installing its latest build from your respective device’s store and check if it fixes the BritBox is not currently available in your country error.
Apart from that, there’s not much that we could currently do, and it is in the hands of the developers to release the patch at the earliest. As and when that happens, we will update this guide accordingly. In the meantime, you could drop in your queries in the comments section below.
Update 1 [February 5th]
According to BritboxUS, they had a server disruption issue. While they haven’t explicitly mentioned if this resulted in the aforementioned error, however, they have recommended a workaround. You should sign out of your account and then reboot your device. Once it boots up, re-login to your account and then check if the issue is resolved or not.