Menu
Reply
Highlighted
  • 30.27K
  • 1.51K
  • 5.25K
Very Insightful Person
Very Insightful Person
468 Views
Message 31 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

as there is nothing they can do you might as well switch.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 6.16K
  • 459
  • 1.07K
Hero
459 Views
Message 32 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

Here are my trace routes.

C:\>tracert ipv4-c003-lin001-teleit-isp.1.oca.nflxvideo.net

Tracing route to ipv4-c003-lin001-teleit-isp.1.oca.nflxvideo.net [151.99.109.23]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    11 ms    12 ms     8 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    13 ms    11 ms     9 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     *        *        *     Request timed out.
  7    12 ms    11 ms    11 ms  uk-lon01b-ri1-ae23-0.aorta.net [84.116.135.30]
  8    11 ms    10 ms    10 ms  213.46.174.14
  9     *       39 ms     *     149.3.183.61
 10    37 ms    41 ms    38 ms  ibs-resid.milano1.mil.seabone.net [195.22.192.86]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    39 ms    38 ms    36 ms  151.99.109.23

Trace complete.


C:\>tracert ipv4-c040-mil001-ix.1.oca.nflxvideo.net

Tracing route to ipv4-c040-mil001-ix.1.oca.nflxvideo.net [23.246.50.152]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms    12 ms     8 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    13 ms    10 ms     9 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     *        *        *     Request timed out.
  7    80 ms    80 ms    79 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  8    97 ms    97 ms    96 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
  9    98 ms    98 ms    97 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
 10    97 ms    96 ms    97 ms  4.15.212.250
 11    97 ms    97 ms    97 ms  po302.es02.nyc005.ix.nflxvideo.net [23.246.61.45]
 12    82 ms    82 ms    83 ms  po306.es01.lhr005.ix.nflxvideo.net [23.246.61.141]
 13    84 ms    84 ms    84 ms  po307.es02.lhr004.ix.nflxvideo.net [23.246.60.203]
 14    86 ms    85 ms    88 ms  po304.es02.ams001.ix.nflxvideo.net [23.246.60.37]
 15    88 ms    87 ms    87 ms  po301.es01.dus002.ix.nflxvideo.net [23.246.60.180]
 16    89 ms    87 ms    88 ms  po300.es02.dus002.ix.nflxvideo.net [23.246.61.207]
 17    92 ms    91 ms    93 ms  po301.es02.fra002.ix.nflxvideo.net [23.246.60.183]
 18    97 ms    97 ms   104 ms  po303.es02.zrh001.ix.nflxvideo.net [23.246.60.237]
 19    98 ms   104 ms    98 ms  po300.es01.zrh001.ix.nflxvideo.net [23.246.60.240]
 20   101 ms   100 ms   102 ms  po302.es02.mil001.ix.nflxvideo.net [23.246.60.239]
 21   102 ms   102 ms   111 ms  po300.es01.mil001.ix.nflxvideo.net [23.246.60.16]
 22   102 ms   102 ms   101 ms  ipv4_1.lagg0.c040.mil001.ix.nflxvideo.net [23.246.50.152]

Trace complete.


C:\>tracert ipv4-c010-mil001-ix.1.oca.nflxvideo.net

Tracing route to ipv4-c010-mil001-ix.1.oca.nflxvideo.net [23.246.51.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms    11 ms     9 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    10 ms     9 ms    10 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     *        *        *     Request timed out.
  7    84 ms    82 ms    79 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  8    97 ms    97 ms    98 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
  9    97 ms    99 ms    97 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
 10    97 ms    97 ms   106 ms  4.15.212.250
 11    98 ms    98 ms    96 ms  po302.es02.nyc005.ix.nflxvideo.net [23.246.61.45]
 12    82 ms    91 ms    91 ms  po306.es01.lhr005.ix.nflxvideo.net [23.246.61.141]
 13    86 ms    86 ms    84 ms  po307.es02.lhr004.ix.nflxvideo.net [23.246.60.203]
 14    85 ms    86 ms    87 ms  po304.es02.ams001.ix.nflxvideo.net [23.246.60.37]
 15    87 ms    91 ms    91 ms  po301.es01.dus002.ix.nflxvideo.net [23.246.60.180]
 16    87 ms    90 ms    89 ms  po300.es02.dus002.ix.nflxvideo.net [23.246.61.207]
 17    92 ms    93 ms   107 ms  po301.es02.fra002.ix.nflxvideo.net [23.246.60.183]
 18   100 ms    98 ms   100 ms  po303.es02.zrh001.ix.nflxvideo.net [23.246.60.237]
 19    98 ms    98 ms   107 ms  po300.es01.zrh001.ix.nflxvideo.net [23.246.60.240]
 20   102 ms   102 ms   101 ms  po302.es02.mil001.ix.nflxvideo.net [23.246.60.239]
 21   102 ms   102 ms   100 ms  ipv4_1.lagg0.c010.mil001.ix.nflxvideo.net [23.246.51.130]

Trace complete.


C:\>tracert ipv4-c015-mil001-ix.1.oca.nflxvideo.net

Tracing route to ipv4-c015-mil001-ix.1.oca.nflxvideo.net [23.246.51.135]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     4 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    11 ms     9 ms    10 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    10 ms    10 ms    25 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     *        *        *     Request timed out.
  7    82 ms    89 ms    82 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  8    98 ms    98 ms    97 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
  9    99 ms    97 ms    96 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
 10    97 ms    97 ms    97 ms  4.15.212.250
 11    99 ms    96 ms    97 ms  po302.es02.nyc005.ix.nflxvideo.net [23.246.61.45]
 12    82 ms    81 ms    81 ms  po306.es01.lhr005.ix.nflxvideo.net [23.246.61.141]
 13    86 ms    85 ms    85 ms  po307.es02.lhr004.ix.nflxvideo.net [23.246.60.203]
 14    87 ms    86 ms    84 ms  po304.es02.ams001.ix.nflxvideo.net [23.246.60.37]
 15    88 ms    90 ms    89 ms  po301.es01.dus002.ix.nflxvideo.net [23.246.60.180]
 16    90 ms    88 ms    88 ms  po300.es02.dus002.ix.nflxvideo.net [23.246.61.207]
 17    92 ms    92 ms   101 ms  po301.es02.fra002.ix.nflxvideo.net [23.246.60.183]
 18    96 ms    98 ms    98 ms  po303.es02.zrh001.ix.nflxvideo.net [23.246.60.237]
 19   100 ms    97 ms    97 ms  po300.es01.zrh001.ix.nflxvideo.net [23.246.60.240]
 20   101 ms   101 ms   101 ms  po302.es02.mil001.ix.nflxvideo.net [23.246.60.239]
 21   102 ms   102 ms   101 ms  ipv4_1.cxl0.c015.mil001.ix.nflxvideo.net [23.246.51.135]

Trace complete.


C:\>tracert ipv4-c028-mil001-ix.1.oca.nflxvideo.net

Tracing route to ipv4-c028-mil001-ix.1.oca.nflxvideo.net [23.246.50.145]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms    10 ms     8 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    12 ms    12 ms    19 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     *        *        *     Request timed out.
  7    83 ms    80 ms    79 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  8    97 ms    96 ms    97 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
  9    98 ms    97 ms    98 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
 10    98 ms    96 ms    97 ms  4.15.212.250
 11    98 ms    98 ms    97 ms  po302.es02.nyc005.ix.nflxvideo.net [23.246.61.45]
 12    83 ms    82 ms    82 ms  po306.es01.lhr005.ix.nflxvideo.net [23.246.61.141]
 13    84 ms    84 ms    86 ms  po307.es02.lhr004.ix.nflxvideo.net [23.246.60.203]
 14    85 ms    86 ms    86 ms  po304.es02.ams001.ix.nflxvideo.net [23.246.60.37]
 15    89 ms    88 ms    96 ms  po301.es01.dus002.ix.nflxvideo.net [23.246.60.180]
 16    88 ms    90 ms    88 ms  po300.es02.dus002.ix.nflxvideo.net [23.246.61.207]
 17    93 ms    93 ms    99 ms  po301.es02.fra002.ix.nflxvideo.net [23.246.60.183]
 18    99 ms   106 ms    97 ms  po303.es02.zrh001.ix.nflxvideo.net [23.246.60.237]
 19    98 ms    96 ms    99 ms  po300.es01.zrh001.ix.nflxvideo.net [23.246.60.240]
 20   102 ms   102 ms   102 ms  po302.es02.mil001.ix.nflxvideo.net [23.246.60.239]
 21   103 ms   102 ms   103 ms  po300.es01.mil001.ix.nflxvideo.net [23.246.60.16]
 22   102 ms   103 ms   109 ms  ipv4_1.mce0.c028.mil001.ix.nflxvideo.net [23.246.50.145]

Trace complete.


C:\>tracert ipv4-c023-mil001-ix.1.oca.nflxvideo.net

Tracing route to ipv4-c023-mil001-ix.1.oca.nflxvideo.net [23.246.51.140]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     8 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    10 ms     9 ms    12 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     *        *        *     Request timed out.
  7    82 ms    83 ms    80 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
  8    98 ms    96 ms    98 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
  9    98 ms    98 ms    97 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
 10    98 ms    98 ms    98 ms  4.15.212.250
 11    99 ms    98 ms   105 ms  po302.es02.nyc005.ix.nflxvideo.net [23.246.61.45]
 12    83 ms    82 ms    82 ms  po306.es01.lhr005.ix.nflxvideo.net [23.246.61.141]
 13    85 ms    84 ms    87 ms  po307.es02.lhr004.ix.nflxvideo.net [23.246.60.203]
 14    86 ms    86 ms    86 ms  po304.es02.ams001.ix.nflxvideo.net [23.246.60.37]
 15    89 ms    88 ms    89 ms  po301.es01.dus002.ix.nflxvideo.net [23.246.60.180]
 16    89 ms    90 ms    90 ms  po300.es02.dus002.ix.nflxvideo.net [23.246.61.207]
 17    92 ms    91 ms    93 ms  po301.es02.fra002.ix.nflxvideo.net [23.246.60.183]
 18    98 ms   107 ms    98 ms  po303.es02.zrh001.ix.nflxvideo.net [23.246.60.237]
 19    98 ms    98 ms   100 ms  po300.es01.zrh001.ix.nflxvideo.net [23.246.60.240]
 20   110 ms   101 ms   101 ms  po302.es02.mil001.ix.nflxvideo.net [23.246.60.239]
 21   102 ms   103 ms   100 ms  ipv4_1.cxl0.c023.mil001.ix.nflxvideo.net [23.246.51.140]

Trace complete.

C:\>
--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG1008D 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection
0 Kudos
Reply
Highlighted
  • 5.3K
  • 596
  • 1.76K
Very Insightful Person
Very Insightful Person
454 Views
Message 33 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

@poor_doggy 

Many large companies don't do their network security/blocking themselves, but out source it to companies like Akamai.  Sony, eBay, Ikea and many others do this and so when people call them to complain about blocking the companies have idea why they are being blocked.

I don't know if Netflix use Akamai's services but you could try entering your IP on this page and see if it reveals anything:

https://www.akamai.com/us/en/clientrep-lookup/

Normally these blocks are temporary, especially if the activity that triggered the block was by the previous owner of the IP address, but it is impossible to say how long it might last.

As others have said the way to get a different IP with VM is to use modem mode and your own router as their system has no way of manually assigning you a new IP.

______________________
Scott

Disclaimer - I don't work for Virgin Media. I'm just another VM user trying to help out.
My setup: V6 TV box, M350 Fibre broadband with Hub 3 in modem mode connected to a Netgear R7000 router. Telewest/VM user since 2001.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Highlighted
  • 18
  • 0
  • 1
Tuning in
424 Views
Message 34 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

Thanks, it says my ip address "didn't receive a bad risk score"

0 Kudos
Reply
Highlighted
  • 18
  • 0
  • 1
Tuning in
378 Views
Message 35 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

Alright. I've switched to modem mode and it works. Obviously, this is less than ideal because I can't use the wifi... For anyone that has the same problem my recommendation is: change to modem mode, get your own router and connect your router to the hub. It's cheaper and less of a hassle than changing the ISP.

But... VM seems to be unwilling to help with this sort of issue, it's a farce, the IP is an asset that obviously belongs to the ISP and if they decided to redistribute it they should first take the accountability for making sure the IP isn't blacklisted by at least the most popular streaming services...

0 Kudos
Reply
Highlighted
  • 87
  • 3
  • 3
Dialled in
368 Views
Message 36 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

For other reasons I gave up trying to use the virgin hub 3 with WiFi on.  I could not log into the hub when it was fully connected, the WiFi signal wasn't great, it was causing jitter and additional lag and it took forever to reboot.  It was less stress just to buy a good second hand WiFi router and use that and leave the hub free to do everything else.

I understand your specific problem with the way IPs are used in the two different modes but it may just be easier to kill off possibly a few issues using a good WiFi router.  If you do go that road I found I had to reboot the two devices at the same time to get them to connect reliably.  Your results may differ as there are posts about alternative reboot ordering.

0 Kudos
Reply
Highlighted
  • 3.85K
  • 234
  • 427
Forum Team
Forum Team
316 Views
Message 37 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

Hi poor_doggy,

 

Thank you for reaching out to mus in our community, I am sorry that you have had to revert to a 3rd party router to tackle this issue.

 

I have spoken to our 2nd line faults team and we only control our IP and MAC addresses, when it comes to the blacklist Netflix or other company's have, we have no control whatsoever , when we provide the services we don't have a way of checking if the I P address is blacklisted anywhere.

 

I am sorry this isn't the answer you were looking for, it would only be Netflix that would be able to remove your I P address from the list.

 

Using a 3rd party router seems to be a good fix and is highly recommended for many issues throughout our forums.

 

Kind regards

 

Paul.

 

 

Highlighted
  • 9
  • 0
  • 0
Joining in
286 Views
Message 38 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

Having not had netflix, because of this problem, for the last three weeks, it's now been resolved by Virgin providing me with a new hub and hence new IP address. They get a perfectly working hub back from me - so the cost to Virgin has been postage only.

I'm sure my returned hub will get tested by Virgin and sent out to some other customer who will get problems if they try to connect to Netflix.

This should not be a customer issue to resolve - I did all the debugging of the problem from my end, providing the Virgin support team with detailed error logs I obtained form my browser console. Thsi is a problem that could occur to anyone at any time - I had been using Netflix perfectly happily for over 2 years before this problem occurred , so Netflix must occasionally update the list of blocked IP addresses and it's Russian roulette as to whether they make a mistake and accidentally add yours !!

I got extremely frustrated talking to VM support which was no fault of the individuals - simply that most did not have the technical knowledge or background to properly understand the information I was giving them. At one point the 'solution' to the problem, it was decided, was to send me a new V6 box - despite the fact that the same issue was happening on all devices attached to my Virgin network and then not happening to those devices when they were attached to my phone's data as a way of access the internet. So Virgin went to all the effort and cost of sending me a new V6 box .... which of course did not resolve the issue.

When I was finally passed onto a 'specialist' support person to talk to , who was extremely knowledgable and helpful, quickly agreed with my diagnosis and agreed that whilst the fault was with Netflix for blocking my IP, that he would arrange for a new router to be sent. (he also agreed that it was ridiculous of them to have sent me a new V6 box to try and resolve the problem).

Should this not be an issue that is taken up between Virgin and Netflix - surely Netflix should share with Virgin the IP addresses they are blocking or at least have an arrangement whereby VM support can use an API to determine if a specific IP address is blocked. Virgin advertise that you can watch netflix through their V6 box as long as you have an account with Netflix - this isn't always true !!

The netflix sport team were no more helpful - first of all denying that they ever block IP addresses .... which they later admitted wasn't true. They then told me that they only supported streaming over IPV6 and the fact that my Virgin hub 3.0 was IPV4 was the cause of the problem ..... which I also pointed out to them wasn't true.

At least it was resolved in the end - I knew I could have taken the approach of getting my own router - but it just annoyed me that I should have to fix a problem relating to communication between such large companies as Netflix and Virgin !!

 

 

0 Kudos
Reply
Highlighted
  • 30.27K
  • 1.51K
  • 5.25K
Very Insightful Person
Very Insightful Person
283 Views
Message 39 of 39
Flag for a moderator

Re: Netflix blocks my VM IP?

someone else is going to get the blacked IP and all customers end up paying for replacement boxes. When the next price rise happens make sure you do not object as it covers replacments of perfectly good hardware. The SH you sent back is unlikely to get reused for a new customer

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply