Wasn't trying to be condescending, and wasn't assuming you didn't get escalation. You simply stated you called them a few times, so wanted clarification on just how far you've been able to take it. Way too many people settle for what they are told over the phone and never get past those lower level people. Wanted to make sure just where you stood in the progression. Really sucks they've been that unhelpful with your problems. I've been lucky with pretty much one email exchange to get them fixing things on my routing. It's amazing how different things can be from market to market.
Really miss how it was under the RR name--I could just go straight to the operator and ask for Tier3 and get someone that would actually do something to fix the problems. I've found I do better to not even use the phone anymore unless it's to report an outage--I just contact them through the website and via email anymore for anything else. Seems to be more effective, even though the response may be slower.
One thing that really strikes me as odd in your situation, is why they are looking at everything on your local segment if you've fingered an issue with their routing partner? Sounds more lik they are suspecting a signalling issue with their hardware, when it is something going on with their partner. Perhaps it needs further escalation, maybe some trace data needs to be sent to the regional NOC or something.
{Edit:}
grr... seems they've gone and updated whois data again. Not seeing direct contacts. Looks like they've gone the way of the generic address now. Not sure how much traction you will get out of it, but you could try sending a short note about the packet loss you've noticed and paste in a tracert or pathping report to this email address:
hrn.ipaddreg@twcable.com
That is still showing on their ARIN record. Only other ones I'm seeing now are the more generic ones in whois:
ipaddreg@rr.com
abuse@rr.com
Who knows, might manage to leapfrog your local guys and get someone further up to take notice.



Reply With Quote

