Same here:

Jun 14 20:12:13  er1.511.msp rpd[1832]: bgp_hold_timeout:4677: NOTIFICATION sent to 2001:504:27::2846:0:1 (External AS 10310): code 4 (Hold Timer Expired Error), Reason: holdtime expired for 2001:504:27::2846:0:1 (External AS 10310), socket buffer sndcc: 38 rcvcc: 0 TCP state: 4, snd_una: 715538896 snd_nxt: 715538934 snd_wnd: 16384 rcv_nxt: 937051995 rcv_adv: 937068379, hold timer 90s, hold timer remain 0s, last sent 26s, TCP port (local 60544, remote 179)

Jun 14 20:12:30  er1.511.msp rpd[1832]: bgp_hold_timeout:4677: NOTIFICATION sent to 206.108.255.58 (External AS 10310): code 4 (Hold Timer Expired Error), Reason: holdtime expired for 206.108.255.58 (External AS 10310), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4, snd_una: 3794713179 snd_nxt: 3794713236 snd_wnd: 16384 rcv_nxt: 58606928 rcv_adv: 58623312, hold timer 90s, hold timer remain 0s, last sent 22s, TCP port (local 179, remote 65426)

—
Andrew Hoyos
[log in to unmask]



> On Jun 14, 2019, at 5:44 PM, Frank Bulk <[log in to unmask]> wrote:
>
> I assume some others are seeing the same, that peering with one of Yahoo!'s IPs has been down since just before 3:45 pm?
>
> Host premier.sxct-north.fbnt.netins.net [207.32.15.28] with interface to BGP peer AS10310-1.micemn.net [206.108.255.58/AS 10310 (Oath Holdings Inc., US)]: the BGP peer state is in state connect
>
> Frank