3 ms·

ówò

zackees 6y ago
This was a coordinated attack that took down a bunch of services all at the same time: https://downdetector.com/ https://downdetector.com/ https://twitter.com/KEEMSTAR/status/1284240539437740033 https://twitter.com/KEEMSTAR/status/1284240539437740033 Update: People are accusing me of using KEEMSTAR as a source and have somehow missed the link to downdetector.com, which keemstar is looking at.
- brian-armstrong 6y ago
  This was a BGP/routing issue and has already been documented. Please don't spread misinformation and hysteria, especially on technical issues like this https://twitter.com/eastdakota/status/1284253034596331520 https://twitter.com/eastdakota/status/1284253034596331520
  - zackees 6y ago
    CEO's are notorious liars. I just had a discussion with John McAfee who said that all good CEO's are feeding misinformation to the press as standard business practice. You can see it here: https://www.youtube.com/watch?v=w_QWrzjKC9I&lc=UgyXzVtjVLbEs8C14f14AaABAg https://www.youtube.com/watch?v=w_QWrzjKC9I&lc=UgyXzVtjVLbEs... The willingness that you believe a CEO who has every incentive to lie to the press, and the preposterous narrative that this was a simple "router issue" - as if half the USA internet system is dependent on a router not failing and there is not redundancy, is simply baffling. I don't care how many downvotes I get. I'm not buying this flimsy narrative. And neither should you. This was a coordinated attack.
    - eastdakota 6y ago
      It was a misconfiguration we applied to a router in Atlanta during routine maintenance. That caused bad routes on our private backbone. As a result, traffic from any locations connected to the backbone got routed to Atlanta. It resulted in about 50% of traffic to our network to not resolve for about 20 minutes. Locations not connected to our backbone were not impacted. It was a human error. It was not an attack. It was not a failure or bug in the router. We're adding mitigations to our backbone network as we speak to ensure that a mistake like this can't have broad impacts in the future. We'll have a blog post with a full explanation up in the next hour or so — being written now by our CTO.
    - fsociety 6y ago
      You should really read up on BGP. It really is that flimsy.
    - Godel_unicode 6y ago
      It's not failure, it's misconfiguration. Totally different issue to be resilient to fat fingers than fires.
- dtertman 6y ago
  It was no such thing. A Cloudflare router advertised some bad routes.
- kingbirdy 6y ago
  I wouldn't count on Keemstar as a reliable source of cyber-attack coverage
- v0tary 6y ago
  Keemstar? Not reliable source. The dude has no idea what he is talking about.

ówò

This was a coordinated attack that took down a bunch of services all at the same time: https://downdetector.com/ https://downdetector.com/ https://twitter.com/KEEMSTAR/status/1284240539437740033 https://twitter.com/KEEMSTAR/status/1284240539437740033 Update: People are accusing me of using KEEMSTAR as a source and have somehow missed the link to downdetector.com, which keemstar is looking at.

brian-armstrong 6y ago
This was a BGP/routing issue and has already been documented. Please don't spread misinformation and hysteria, especially on technical issues like this https://twitter.com/eastdakota/status/1284253034596331520 https://twitter.com/eastdakota/status/1284253034596331520
- zackees 6y ago
  CEO's are notorious liars. I just had a discussion with John McAfee who said that all good CEO's are feeding misinformation to the press as standard business practice. You can see it here: https://www.youtube.com/watch?v=w_QWrzjKC9I&lc=UgyXzVtjVLbEs8C14f14AaABAg https://www.youtube.com/watch?v=w_QWrzjKC9I&lc=UgyXzVtjVLbEs... The willingness that you believe a CEO who has every incentive to lie to the press, and the preposterous narrative that this was a simple "router issue" - as if half the USA internet system is dependent on a router not failing and there is not redundancy, is simply baffling. I don't care how many downvotes I get. I'm not buying this flimsy narrative. And neither should you. This was a coordinated attack.
  - eastdakota 6y ago
    It was a misconfiguration we applied to a router in Atlanta during routine maintenance. That caused bad routes on our private backbone. As a result, traffic from any locations connected to the backbone got routed to Atlanta. It resulted in about 50% of traffic to our network to not resolve for about 20 minutes. Locations not connected to our backbone were not impacted. It was a human error. It was not an attack. It was not a failure or bug in the router. We're adding mitigations to our backbone network as we speak to ensure that a mistake like this can't have broad impacts in the future. We'll have a blog post with a full explanation up in the next hour or so — being written now by our CTO.
  - fsociety 6y ago
    You should really read up on BGP. It really is that flimsy.
  - Godel_unicode 6y ago
    It's not failure, it's misconfiguration. Totally different issue to be resilient to fat fingers than fires.
dtertman 6y ago
It was no such thing. A Cloudflare router advertised some bad routes.
kingbirdy 6y ago
I wouldn't count on Keemstar as a reliable source of cyber-attack coverage
v0tary 6y ago
Keemstar? Not reliable source. The dude has no idea what he is talking about.