Not quite sure whether this should go to outages, or here. I'm not confident that there actually *is* an outage of any sort...having a tough time characterizing it. I have an IPSec tunnel between 64.6.220.219 (upstreams Sprint, AT&T, and LeveL3/legacy TWTelecom) and 64.199.98.162 (upstream Windstream). Egress from 64.6.220.219 was going through Sprint until I turned that session down. traceroute to 64.199.98.162 (64.199.98.162), 30 hops max, 60 byte packets 1 1a-1-vlan11.int.appriss.com (10.10.35.1) 0.995 ms 0.965 ms 0.947 ms 2 lsces03-e-1-13.office.appriss.com (10.9.3.45) 0.283 ms 0.344 ms 0.421 ms 3 lscorpfw01a-ge2-0-0-0.int.appriss.com (64.6.219.41) 0.275 ms 0.299 ms 0.272 ms 4 clinetedge01-ge-0-3-0-0.appriss.net (64.6.221.157) 0.731 ms 0.762 ms 0.752 ms 5 sl-gw10-nsh-0-1-0-0-si204.sprintlink.net (144.228.97.29) 45.753 ms 45.782 ms 45.772 ms 6 144.232.11.73 (144.232.11.73) 44.496 ms 44.321 ms 44.296 ms 7 144.232.5.212 (144.232.5.212) 46.955 ms 45.695 ms 46.958 ms 8 144.232.2.225 (144.232.2.225) 42.132 ms 144.232.15.111 (144.232.15.111) 41.922 ms 144.232.10.218 (144.232.10.218) 41.928 ms 9 atl-bb1-link.telia.net (62.115.49.157) 42.872 ms 42.863 ms 42.955 ms 10 * * * 11 * * * traceroute from the 64.199.98.162 side back towards 64.6.220.219: Type escape sequence to abort. Tracing the route to 64.6.220.219  1  64.199.98.161 0 msec 10 msec 0 msec  2  205.147.221.153 0 msec 10 msec 0 msec  3  40.128.249.156 10 msec 0 msec 0 msec  4  40.136.117.74 0 msec 0 msec 10 msec  5  40.128.10.138 10 msec 20 msec     40.128.248.62 10 msec  6  40.128.10.150 10 msec     40.128.10.146 10 msec     40.128.10.150 10 msec  7  80.239.194.41 20 msec 10 msec 10 msec  8  213.248.87.254 10 msec 10 msec 30 msec  9  12.122.133.34 20 msec 20 msec 20 msec  10 12.122.152.137 20 msec 20 msec 20 msec  11 12.122.152.209 50 msec 20 msec 20 msec  12 12.118.107.122 40 msec 40 msec 40 msec  13 170.75.217.4 50 msec 40 msec 50 msec  14  *  *  *   15  *  *  *   (the 170.75.217.4 is my edge facing AT&T) When I shut down my BGP session to Sprint, my traffic shifted to AT&T and the tunnel came up. Anyone else seeing any issues around this area (I know, pretty vague), seemingly specifically related to interconnections between Sprint, Telia, and Windstream? I know Telia experienced some issues yesterday that were apparently resolved, maybe some lingering issues resulting from that? Shot in the dark, here. -- Jeff