It's nice to know I'm not the only one.
The problem went away recently when my usage cycle refreshed. I listed before all the reasons that I think it's related to the usage notification, so I won't repeat them.
I also tried changing DNS servers and running NoScript with the same results as you (no change). I did confirm via ARIN Whois that the IP is registered to Rogers: http://whois.arin.net/rest/net/NET-64-71-240-0-1/pft .
Anyway, thanks for responding. Again, it's reassuring to know I'm not alone.
I can also confirm that the Rogers Usage Notification http header injection appears to be failing.
You can capture this html being placed in the stream, the server at 188.8.131.52 is unresponsive. This is preventing pages from loading until reload is hit. Anyone know if you can opt out of this message altogether? I am in the SamKnows program and do not get charged for overages, the messages are not needed.
You just confirmed a thought I had was worth wondering. I know that recently I have reached 75% usage and you highlighting your experience on that topic is interesting. In the past I use to use the Rogers DNS and I would receive inline browser notifcation about recent usage. Is this possibly still related to that notifcation system but is only causing problems when not utilizing Rogers DNS? I believe my usage refresh cycle arrived today so I too will see if a change occurs here. But as a current measure I added a block rule to my firewall to prevent access to 184.108.40.206 only because other users in my house do not utilize noscript.
A lot of http pges will hang before loading, trying to connect to 220.127.116.11, which is a rogers address. I have to stop loading the page, then click reload, and the page will load normally.
From what I've read, that's rogers trying to insert a cap warning, but my billing period ending yesterday, and it's still happening.
I've tried rebooting my modem, but it's still happening.
I've tried a different DNS server (18.104.22.168,22.214.171.124), but it's still happening.
I've tried calling rogers, but was on hold for 10 minutes.
This looks like the same problem already reported here.
My guess is that the Rogers server which is responsible for the data feed at that address is either unserviceable or defunct. This is going to take someone from inside the Rogers organization to find whom ever is responsible for the notification system and the server and have him or her determine what the problem is with the server.
Mind you i have regularily been on packages which normally i dont get anywhere near my cap..
I beleive you wont see these messages when you are using an alternate DNS
Back on the old express (70g cap one i think, before the d3 modems)... i was already on an alternate DNS.. and DID go over my limit, with no notification..
(but also was not having any other issues, like it was TRYING but couldnt, etc)
The 126.96.36.199 timeout issue is back, just around when I hit 75% of my limit, and I see a new thread with the same problem. Is anyone at Rogers working on this?
PS: I did try switching DNS servers. It didn't fix it.