|
|
发表于 2020-9-1 17:27:04
|
显示全部楼层
Summary of Incident:
& p1 c( o$ Z7 x———————————————, Q* `: F. u/ k7 F8 g
) X& R$ b& k; g/ z$ L/ J
& Y7 X/ P' ?' n9 R% Y2 S
( _2 v" A$ `; E$ FYesterday, August 30, 2020 at 6:04am EST, the Hivelocity NOC received alerts regarding a network connectivity issue tied to our Century Link/Level3 (ASN 3356) transit. At this time, our Network Engineering Team noticed BGP sessions with ASN 3356 were flapping and immediately shut them down across our network. However, after we disabled these BGP sessions, effectively de-peering CenturyLink/Level3, they continued announcing our IP space which caused our traffic to be blacked-holed within their backbone network. In laymen’s terms, if your provider was using this backbone, it could not reach our network. We quickly found that this issue was a major outage affecting the entire AS3356 backbone. This included several common Internet Service Providers who lean heavily on this backbone, such as Spectrum and other local ISPs. Due to the nature and scope of this issue, including the fact CenturyLink/Level3 was improperly announcing our routes, the typical solutions we would implement were ineffective. While working with our other transit providers to work around the problem, at roughly 11:00am the Hivelocity network as well as networks across the globe began to normalize as CenturyLink/Level3 began resolving the issue internally
& r. |# {4 W% K( j9 ^
" P7 R3 P+ _1 Q6 z& B+ a0 oBelow is an excerpt from the official CenturyLink RFO we received this morning:
- \' }+ w; U: i9 l2 i6 A: r+ P4 ]3 a% o" I1 |1 W' d/ [
Cause0 K8 x2 A% O1 V
An offending flowspec announcement prevented Border Gateway Protocol (BGP) from establishing correctly, impacting client services.
. a* {1 R* a" B( c
! l, `5 v4 m% iResolution
1 ]! n3 k# j( s- B! D: f3 H, PThe IP NOC deployed a configuration change to block the offending flowspec announcement, thus restoring services to a stable state.' i2 x/ a4 G8 @# ?4 `9 I
; _4 B/ h, {; _" M
Summary o* V, _0 n- |5 a) r% m3 a
On August 30, 2020 10:04 GMT, CenturyLink identified an issue to be affecting users across multiple markets. The IP Network Operations Center (NOC) was engaged, and initial research identified that an offending flowspec announcement prevented Border Gateway Protocol (BGP) from establishing across multiple elements throughout the CenturyLink Network. The IP NOC deployed a global configuration change to block the offending flowspec announcement, which allowed BGP to begin to correctly establish. As the change propagated through the network, the IP NOC observed all associated service affecting alarms clearing and services returning to a stable state.
+ t0 r: c2 {: `7 ~7 T1 e m* B$ U; d8 ]6 e3 y% ^: \2 \: \, L+ F% x
; }( ~& e- P+ f, t4 U& _
1 C7 J2 O: {" {& X Y) mService Impact Times:
" X% y1 h9 u2 {3 V5 P- U( d) h———————————————
) [# `2 V% y2 q, ?, M }5 R- E
& ]1 m5 f2 A/ n# ]( \( W; y4 lAugust 30th, 6:04am EST - 11:30am EST
- B0 x- P) u& D; j
2 B) Y4 {6 @2 x3 n' U! G5 L/ _, w" j7 B
Additional Information:8 b y' f, M$ I' M3 L
———————————————2 H+ D+ t, j8 e: U$ @
9 V: Y' @2 x1 D4 J# B0 F: `You can find further information regarding the global impact of yesterday's event at the following links. ' h) r1 K& F. l9 `8 S+ g
3 B8 T# I0 I1 Y2 Q5 [7 zhttps://www.theverge.com/2020/8/ ... hulu-feedly-discord
0 E9 c9 O0 o% t, H4 U5 L% Ihttps://9to5mac.com/2020/08/30/centurylink-outage/7 Q* M* l6 b+ `# @1 w9 X4 q& f
https://www.bleepingcomputer.com ... steam-discord-more/
9 z: I/ V8 E, u% R" b3 k8 J
 |
|
发表于 2020-8-30 22:43:06
发表于 2020-8-31 00:17:50
发表于 2020-8-31 09:01:38
