No, people need to call and clearly communicate the issue to Rogers stating that:Will this ever correct itself?
We understand and share your frustration, but please rest assured that at this point the problem is not at our end. As some users here have already correctly pointed out, the issue is that Rogers.com's own domain name servers appear to have incorrect data for some of our hosts and they have not yet updated it with the correct information.
In simplified terms: when you load pages from imdb.com, some of the content (such as images and graphic/layout information) is retrieved from other servers, specifically i.media-imdb.com and ia.media-imdb.com -- the information on where to actually access those servers (i.e. which IP addresses are meant to be accessed by your browser when you go 'i.media-imdb.com') is provided via a service called DNS (Domain Name System). Your browser sends a requests to these DNS servers and basically asks "Where is i.media-imdb.com?" and the DNS server replies to your browser "that server is located at 188.8.131.52, that's where you need to go" (this is of course a broad simplification: for more details about how the domain name system works, see: http://en.wikipedia.org/wiki/Domain_Name_System )
For some yet-undetermined reason, a few days ago this information within Rogers' DNS system has somehow become incorrect. When Rogers.com users try to access those servers, they are directed to the wrong IP addresses. The requested content is not there of course, so the page doesn't load correctly.
We have done all we can at our end to ensure that the information is accurate, and the problem appears to affect only Rogers.com's servers and, apparently, some Vodafone users in Europe. Nobody else seems to be affected. We're not sure why this information is incorrect within those DNS servers but we double-checked that the DNS data is correct at the source, and other servers are supposed to refresh this information periodically and frequently. For reasons that are outside of our control, Rogers'.com DNS is still using this outdated information. Until they update their DNS records, their users will continue experiencing this problem.
At this point, we recommend that Rogers.com customers contact their ISP's customer support and raise the issue with them, explaining the problem and pointing out that their DNS information for i.media-imdb.com and ia.media-imdb.com is incorrect and that they need to refresh/update their records. Repeated queries from internal customers rather than from an external entity (i.e. us) may lead to a faster resolution.
In the meantime, a workaround for the tech-savvy, as already suggested by some users here, is to configure your machine to use different/public DNS servers. Google offers free DNS servers and their information is correct and up-to-date. Instructions on how to configure your system to use Google's free DNS instead of Rogers.com's are listed here:
As soon as we have an update, we will post it here.
Thank you for your patience.