IP Address does not match my Geographical location

NotInLondon
Contributor II

Since a couple of weeks ago, my IP address is displaying as my location as "London, ON", whereas I am physically located outside of Ottawa, ON.  While the internet itself is fine, this 600 km difference seems to mean that I am not getting the desired sports coverage as a result of regional coverage... the wrong blackout information is being applied.

Note that I don't have or have never used any kind of IP manipulating software/VPN... I am getting this information from lookup sites like "whatismyip", etc.  

Is this something that is within my ability to change?  Without having to 'trick' sites to believing my IP is something else?  No shenanigans; just want it to be accurate so I can get my regular sports back (which has been fine since moving here, about 2 years ago)...

Any suggestions are appreciated! 

 

4 80 27.7K
3 helpful replies

Accepted Solutions

I kept badgering TSN until they finally escalated my request to someone who finally found this solution. 

View reply in original post

Good evening @DWC1990 

Thank you for reaching out to the Bell Community 🙂

We wanted to check in and see if you were able to reach out to TSN directly. They will be able to gather some additional information from you and help fix that up.

Also, are you using a VPN?

Please keep the Community posted,

@BellPatricia 

View reply in original post

Hi @gaby31, thank you for your reply 🙂

We recommend that you chat with a specialist from Sportsnet directly on their website in order to have this resolved. For more information check out: I think an NHL regional blackout is being incorrectly applied. What do I do?Opens in a new tab or window

@BellPatricia 

View reply in original post

80 REPLIES 80

I live in Northern Alberta and keep experiencing "regional blackouts" on Sportsnet West while trying to watch Oilers hockey games. I've never had an issue up until about 3 weeks ago, Fibe App has worked, SportsNet app has worked now both give the same error. My receivers still work and this issue is strictly on the Apps.

I've reached out to Bell support on 2 different occasions, both conversations were well over an hour long with zero resolution and customer support saying it is SportsNet. This is clearly a bell related issue and customer support has been brutal, I was told I would receive a follow up call which never happened.

Time to step up your customer support Bell.....

AlexS
Expert Contributor II

"SportsNet app has worked now both give the same error. My receivers still work and this issue is strictly on the Apps." So u mean u cannot watch the feed at all?

I can watch the channel until a hockey game start either Oilers or Flames. Both give me a black screen that says “Regional Blackout Restrictions apply”. I’ve validated my postal code to ensure it’s Northern Alberta so I see no reason I’m getting this error. 

AlexS
Expert Contributor II

So the problem is across all platforms right? Both dvr, bell & sn apps?

Just Bell Fibe App and SN app I get the black out restrictions. 

My receivers/satellite work fine.  

Wakka197
Valued Contributor

From your storey I’ve never heard of a problem . I’ve never exsperienced it . You using something to change your location for your internet .

Ya its frustrating because I can't even test it until there is a game on lol. No VPN or anything to change location and did validate my postal code in Bell.

Hey @NorthernB, Thanks for your post, and welcome to the Community. 🙂

Thank you for all the troubleshooting you've completed. It's great to hear that you can still catch the game on your Satellite TV receiver.
As you mentioned the regional black out message is occurring on your Bell Fibe TV App and through the Sportsnet App it would appear that your IP address is listed outside of Alberta, thus causing the regional blackout message. Have you contacted your ISP to confirm where your IP is pointing to? 

Keep the Community posted!

- Patricia

 

 

DoubleP
Contributor III

Hello, silly question maybe, but have you tried turning your Bell fibe modem off/on to ensure it re-negotiate for a new IP address?  Maybe you got assigned an IP from a different zone (London area) because the Ottawa IP assignment service was temporarily unavailable at the moment your modem was requesting for a new IP address?

if you connect to https://www.speedtest.net/, what city shows up, for the server used to do the speed test?

You may also provide us with your Traceroute information, providing a record on the route through the internet from your computer to another.  You can google Traceroute if you are not familiar with this utility.

Thank you for your reply and insight.

The modem does get reset often, both intentionally and as a result of power outages.  The location had flipped back to 'Clarence-Rockland' yesterday, which would be correct, but this morning the IP has changed and is back to London.  I am thinking that if there is a recent problem (never had an issue before a few weeks ago) with the local assignment service, it seems to be...persistently intermittent!  

The server used in Speedtest vary, but all results are reasonably local, with Cornwall, 90km away, being the furthest geographically.

Related but outside the direct scope of Bell, would be how those sports stations are determining my location, and whether they do this on-demand with each access, or whether this information has been checked and is now stored somewhere... If it's through a local browser cookie, I guess I can purge and try again...

Anyway, thank you again... I will continue with some testing, and escalate to the forum you reference if I am unsuccessful.

 

Regularly going back to London almost seem like if there is a VLAN configuration error in a switch near your area, because even if this was a load balancing issue, your modem would certainly pick up another switch that is physically closer to you than London, ON... To me, this would warrant a chat with an engineer from the forum I mentioned in my previous post.

When you look at the first hop of a traceroute, does the 10.50.xxx.xxx address change depending of if you are mapped to Rockland vs London?  if may be that the switch allocates you with an IP from a subnet that used to be in London, if the 10.50.x.x IP is exactly the same each time...

if its not... then maybe, just maybe your modem encounters such slow IP addressing response from so many regional switches that it only gets picked up by a London switch (this sounds very unlikely... my bet is a misconfiguration on a switch near you)

BellPatricia
Moderator

Hi everyone, and welcome to the Bell Community 🙂

We have a couple of suggestions we'd like you to review.

  • Are you connected while using a work or personal VPN? If so, please disconnect the VPN and test again.
  • Does the same thing happen when you test different sites that identify your location (such as Home DepotOpens in a new tab or window or any other that you may use)?

Keep the Community posted with your results.

- Patricia

Help!!!!!

 

I have been experiencing this problem since I got my bell internet last may! 

I attempt to watch the Ottawa Senators on the TSN app and get blackouts all the time. My ip location constantly registers as being somewhere in the GTA region even though I am in Ottawa.

I’m fed up with this! I’ve heard all the excuses from bell techs. Oh sir your IP address is dynamic, yeah well the dynamics are causing my Senators games to be blacked out! 

oh sir, you need to call TSN, it’s on their end. No it isn’t, I know this because as soon as I disconnect the wifi and run the app on my cellular data, no black out! 

Can anyone actually help me resolve this issue rather than deflecting it! Last time I called about it I was told it would be passed on to the higher ups in the tech department and I would be contacted within 48 hours. I was never contacted!

Senators home opener starts in 1 hour and as of now I won’t be able to watch it!

I am using whatismyipaddress.com to check the IP. Always in GTA or Hamilton. 

I am ready to switch to Rogers if you can’t help me fix this. 

@NotInLondon had the same issue.