Clueful BGP from TW-Telecom/L3

Is there per chance anyone hanging on here who is clueful about BGP working with TW-Telecom and the recent integration with Level3???

I have a client that I consult with whose route is not getting sent from TW to L3 and the techs on the case are convinced we need to put different BGP communities in (both to TW link and other provider link) which of course we are putting in to satisfy them, but magically it is not working. This SHOULD be an easy thing to figure out using the Looking Glass servers within both TW and Level3, but this concept is lost on techs we are dealing with.

Anyone internal there who can contact me off-list would be greatly appreciated!


Last I dealt with TW Telecom and BGP we had to explain to them that putting
in a static route on both routers on top of BGP was not desired. Then they
reconfigured a circuit 30 miles away when trying to turn it up again
causing an outage in our data center.

Sorry, not super hopeful when it comes to TW Telecom.


Yeah, considering that I STILL haven’t managed to get anyone in their supposed “Tier 3” group to call back on the open case is just completely baffling to me. And with the Level 3 side, I’ve tried all sorts of different communities they supposedly use only to find that other policies override how those are treated along the way. I just don’t understand how customer support can be such a difficult thing.


We recently had a similar case and had to solve the problem by working with IO and another provider outside of Level3. We got the same Level3 instruction to install various community strings, and when that didn’t work their response was basically “oh, well.” We have jury rigged a fix by trial and error, and Level3 says they will converge the Level3 and TWTelecom networks in a couple months. Whether that means an ASN change I don’t know.