If it's every 60 seconds, I'd suspect the BGP timer is the root. They
probably forgot to use next-hop self or a static route to a peer. The
end result being that the route to the bgp peer is learned via bgp
itself...
Eric Krichbaum, Chief Engineer
MCSE, CCNP, CCDP, CCSP, CCIP
If it's every 60 seconds, I'd suspect the BGP timer is the root. They
probably forgot to use next-hop self or a static route to a peer. The
end result being that the route to the bgp peer is learned via bgp
itself...
Maybe. Hard to say if thats what their default hold time is. I am still seeing the odd hit in their network. For the sites we connect with inside Bell, the tunnel LQR expire is 10 seconds and we have seen 2 big bounces since routing around this morning. I emailed their noc, but no response. The Bell looking glass doesnt seem to have any flap statistics so I dont know if things are bouncing inside 
It is looking different once again. Via Cogent to me,
194# traceroute 199.212.134.1
traceroute to 199.212.134.1 (199.212.134.1), 64 hops max, 44 byte packets
1 HSE-MTL-ppp12931.qc.sympatico.ca (209.226.183.241) 266.986 ms 229.511 ms 209.679 ms
2 Hamilton-ppp278329.sympatico.ca (206.172.130.250) 419.439 ms 219.614 ms 199.657 ms
3 kitcorr01-fe0-0-0.15.in.bellnexxia.net (206.47.229.8) 219.461 ms 239.605 ms 187.514 ms
4 badBellDNS (64.230.241.125) 221.605 ms 209.597 ms 199.655 ms
5 badBellDNS (64.230.242.194) 219.439 ms 227.155 ms 202.135 ms
6 core2-chicago23-pos10-0.in.bellnexxia.net (206.108.103.118) 229.386 ms 249.620 ms 346.174 ms
7 bx1-chicago23-pos11-0.in.bellnexxia.net (206.108.103.125) 228.434 ms 234.041 ms 219.645 ms
8 p13-0.core01.ord01.atlas.cogentco.com (154.54.11.29) 249.438 ms 239.589 ms 199.658 ms
9 p15-0.core02.ord01.atlas.cogentco.com (66.28.4.62) 239.441 ms 249.618 ms 229.679 ms
10 p5-0.core01.yyz01.atlas.cogentco.com (66.28.4.214) 249.409 ms 237.480 ms 231.808 ms
11 g0-1.na01.b011027-0.yyz01.atlas.cogentco.com (66.250.14.230) 251.504 ms 259.618 ms 219.669 ms
12 1572534Ontario.demarc.cogentco.com (38.112.5.166) 239.467 ms 249.593 ms 219.660 ms
13 tor-hespler-360-dslgate.sentex.ca (64.7.143.43) 229.489 ms 249.606 ms 214.908 ms
14 hespler-tor-360-i4.sentex.ca (64.7.143.46) 241.707 ms 229.615 ms 219.680 ms
15 ns.sentex.ca (199.212.134.1) 259.436 ms 239.613 ms 215.514 ms
Hops 6 and 8 were coming back as * * * on the traceroute a few hrs ago, but packets were getting to and from me. Hopefully someone from Bell will pipe up on or offlist as to what the problem was / is and if its resolved. Telus is my main transit, and I dont like having to use such a blunt approach to working around this issue
---Mike