There are no caps that I know of in TWC or Spectrum.
There is an "abuse causing system harm" clause but I've only seen it enforced onexcessive peer to peer sharing and residential service servers.
That can be interpretted as paying for 50 meg service and trying to pull 50 megs 24 hours a day... like via streaming video.
Got this fixed from Tier 3 Support assistant, there is some DNS issue.
Thanks a ton Shane (Customer support) you really made me stay back with TWC.
Note: You have call the customer support and ask them to connect to Tier 3 support team to resolve this issue.
Thanks for telling me the IP system may be FUBARed and not to worry about it.
Google is requiring 0Auth 2.0 and AFAIK Outlook doesn't support that so the direction is to go to the google site and allow less secure devices to access the acount. Since that's likely a bad idea in a 2.0 world, I downloaded Thunderbird (which is 0Auth 2.0 compatible) and set up my e-mail accounts in that e-mail client. I just have to remember to set the view to Original HTML. It will probably save me money next time I buy a new version of M$ Office that omits Outlook.
I can go to google dot com and do a Search for any item, hit enter, then scroll down to the bottom of the results page and it will tell me the IP location information.
pop up blocker working
ads were on top of twc.com/news home page
your agent was able to see them, could not solve
i do not know if TWC solved the problem but they disappeared within 1 day of calling you
Your idea that that webhosts need to register domains with all the DNS servers around the world is not true. The webhosts register them in a central place and DNS servers need to regularly go to them and update their lists, not the other way around. And if they don't have a website address in their database they are supposed to ask other DNS servers to help find it, not take a shortcut to an error page.
Here is a helpful webpage explaining how the nuts and bolts work:
Here is a short version copy and paste quote:
DNS servers accept requests from programs and other name servers to convert domain names into IP addresses. When a request comes in, the DNS server can do one of four things with it:
It seems to me like TWC DNS server did 1. and 4. above, concluding that if it was not already included on their server that it must not exist. As a very helpful comenter above pointed out, no other DNS servers were having trouble resolving the website except TWC.
I assume you already tried clearing the DNS cache & cookies. If so, contact your hosting service and file a complaint. They need to push the new routing/ site / webpage info to TWC.
This is a common problem everywhere