Oh yeah and it was not my issue :) It was as I suspected. Elijah Savage wrote:
Got it figured out shortly after I sent this message.
Sorry and Thank you.
Elijah Savage wrote:
All,
I had about 20 customer down today which connect back to me via vpn connectivity across the internet, but we also have a private Sprint MPLS conection that was down at this time. My VPN tunnels all started to come up at about 2:20pm today at the same time and at exactly that time my private Sprint MPLS connectivity came back up which was weird. Below you will find traceroutes that stops in Sprints address space but then after it all came back up the very next hop is AT&TMPLS. I then did some correlation and found out that all my tunnels that were down the peering address belongs to AT&T all were 12.x addresses. Were there some sort of routing issue between AT&T and Sprint between Noon and 2:30 today? I do not peer with AT&T or Sprint so I am sure they will not give me any info if I called in. But I do have a ticket open with my provider to see if they can get info out of them.
Incomplete 1 68.250.30.130 4 msec\par 2 66.73.28.97 0 msec\par 3 65.43.25.116 4 msec\par 4 151.164.188.201 12 msec\par 5 151.164.242.129 20 msec\par 6 151.164.42.168 20 msec\par 7 151.164.191.114 20 msec\par 8 151.164.42.139 20 msec\par 9 144.223.241.57 24 msec\par
Complete
1 68.250.30.130 0 msec\par 2 66.73.28.97 4 msec\par 3 65.43.25.116 0 msec\par 4 151.164.188.201 12 msec\par 5 151.164.242.129 180 msec\par 6 151.164.42.168 20 msec\par 7 151.164.191.114 20 msec\par 8 151.164.42.139 20 msec\par 9 144.223.241.57 20 msec\par 10 192.205.32.141 236 msec\par 11 AT&T[MPLS: Label 32752 Exp 0] 52 msec\par 12 12.122.10.46 [MPLS: Label 32451 Exp 0] 52 msec\par 13 12.122.9.141 [MPLS: Label 32326 Exp 0] 52 msec\par 14 12.122.10.90 [MPLS: Label 32259 Exp 0] 52 msec\par 15 12.122.9.161 [MPLS: Label 32279 Exp 0] 52 msec\par 16 12.122.10.130 [MPLS: Label 32761 Exp 0] 52 msec\par 17 12.122.12.150 [MPLS: Label 450 Exp 0] 56 msec\par