here's some more from that site i found...maybe Rogers has no clue how to really fix this issue????
seems David Lemon and Shai Balasingham are two people from Rogers who are apparently working on this issue. I'm not sure what to do from here, maybe contact them directly, or continue to go the route through Rogers service????
As you can see we do indeed own these blocks:
Nope, you do NOT own these blocks:
OrgName: Rogers Cable Communications Inc.
Address: One Mount Pleasant
NetRange: 126.96.36.199 - 188.8.131.52
CIDR: 184.108.40.206/12, 220.127.116.11/13, 18.104.22.168/14, 22.214.171.124/16,
NetType: Direct Allocation
In my book, Direct Allocation means that they were set aside for you to
use, but you do NOT own them.
> If anyone has any questions, or I can provide any additional
> which anyone may require,
We can't do your job for you. You need to set up a server, or servers,
with IP addresses in each of the blocks that are causing you grief. Then
when a customer says that they cannot reach something in network X, you
must contact the NOC of network X, and ask them to traceroute to the IP
address that you KNOW is functioning. If they can't directly fix the
problem, then ask them to email you the traceroute so that you can
figure out where the problem is (probably a 3rd party newtork upstream
of network X) and contact them yourself.
Rinse and repeat. That's generally how operational problems get fixed.
And that's how networks have been dealing with this specific issue for
the past two or three (or more) years.