Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Xentrk

  • Rank
  1. Xentrk

    SlingTV from California IP

    sling.com website has been working using Firefox now when connected to LA server for the past 12 plus hours or so. The current IP address of the server is is I'll keep checking periodically and post my results.
  2. Xentrk

    SlingTV from California IP

    If you are interested, I maintain a list of IPv4 addresses for SlingTV on my GitHub page https://github.com/Xentrk/Asuswrt-Merlin-Selective-Routing There are two lists for SlingTV. You need both of them for it to work. I use the lists on both pfSense and Asuswrt-Merlin. Move Networks is the primary source for SlingTV https://bgp.he.net/AS35873 I had to harvest some other IP addresses using the IPSET feature of dnsmasq on Asuswrt-Merlin to collect a few others.
  3. Xentrk

    SlingTV from California IP

    On my Windows 10 laptop, I only have issues with the Sling.com website when using Firefox or Firefox Nightly. MS Edge and Chrome no problems. I am still able to route SlingTV traffic to different server locations with no issues though. It is just the sling.com website itself when using Firefox on my Windows 10 laptop. The sling.com website on the Firefox browser on my iPad works fine. When the issue first started occurring, it happened on all browsers. I don't have the issue when using my Asuswrt-Merlin firmware router and route all traffic from my Windows 10 laptop to a VPN tunnel. I use the Asus router as a backup and write programs on it. My primary router is pfSense and that is where I am having the issue. In case you are interested, I determined the following domains are being used on the sling.com website. sling.com, slingtv.com, help.sling.com, tags.tiqcdn.com, cart.sling.com, whatson.sling.com, news.sling.com
  4. Xentrk

    SlingTV from California IP

    I also started having issues with the sling.com website only when using LA. Only the website was affected. No impact to streaming. I changed to NY and the problem went away. Later in the week, the LA server was reported as being in a foreign country from one of the sites that allows you to lookup your IP address. Perhaps that is what has been causing the issue. I think that may be the issue as I have had this problem in the past with other sites. I will keep monitoring and report back. But this sounds like the best explanation for the issue.