Reliance Jio and Hathway are blocking Twitch Streams during IPL matches

  • Thread starter Thread starter RedskyITM
  • Start date Start date
  • Replies Replies 116
  • Views Views 11,128
Messages
562
Location
NA
Looks like JioFiber (and therefore Hathway Fiber too) is stopping streams from loading on Twitch past 6:20PM. Chat and everything else works fine but the stream fails to load. Might be due to bootleg IPL streams.

I think it's really stupid that they're doing this. Gonna drop my Hathway connection as soon as feasible if it doesn't look like they're going to stop.
 
It’s working perfectly fine here, Hathway Fiber (H-Fiber) and Jio Fiber are two separate subsidiaries and identities. Posting your issue on some other sub forum won’t help you.
 
But it does not mean that it will provide the same quality of service for all their subsidiaries. My streams are working perfectly well and I don’t even watch IPL.
By the way it could be the Jio DNS causing the issue as it resolves from ‘dnscache.jio.com’ - for my setup I have disabled Jio’s DHCP so that my Pi-Hole can have hundred percent control over the connected local clients with proper DNS switching which probably should mitigate the issue.
 
But it does not mean that it will provide the same quality of service for all their subsidiaries. My streams are working perfectly well and I don’t even watch IPL.
By the way it could be the Jio DNS causing the issue as it resolves from ‘dnscache.jio.com’ - for my setup I have disabled Jio’s DHCP so that my Pi-Hole can have hundred percent control over the connected local clients with proper DNS switching which probably should mitigate the issue.
What was the point of your first post if you're circumventing their DNS hijacking to begin with? Of course it's going to work for you.


According to the Reddit thread I linked, Twitch is still working on mobile data @Phanindra Musinada
 
@RedskyITM If it's just a DNS blocking you could just change the DNS right? Or are they hijacking DNS so even if you change it, it still won't work (unless DoH/DoT is used).

I mean yes it's shitty that they are doing this but considering a custom DNS can fix it I don't think it's bad bad.
 
ESNI or TLS ECH as it is called now(?) would probably make it quite hard for ISPs to block domains. Firefox and CloudFlare are supporting early versions of this tech. Chrome is waiting for spec development to reach a certain stability.


It's hard to intercept so China decided to block all traffic using this technology.

 
Last edited:

Back