<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>I know this isn't exactly work related, but it's my day off and I'm trying to watch some Netflix in the Midwest area and I can't get anything. I'm thinking this is related, ping times out and tracert jumps to random public IP's before timing out.</p>
<p><br>
</p>
<p></p>
<div>C:\Users\nick>ping www.netflix.com<br>
<br>
Pinging www.us-east-1.prodaa.netflix.com [52.72.205.255] with 32 bytes of data:<br>
Request timed out.<br>
Request timed out.<br>
Request timed out.<br>
Request timed out.<br>
<br>
Ping statistics for 52.72.205.255:<br>
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),</div>
<p></p>
<p><br>
</p>
<p></p>
<div>C:\Users\nick>tracert www.netflix.com<br>
<br>
Tracing route to www.us-east-1.prodaa.netflix.com [54.236.170.9]<br>
over a maximum of 30 hops:<br>
<br>
  1     1 ms     1 ms     1 ms  192.168.1.1<br>
  2     *        *        *     Request timed out.<br>
  3    10 ms    13 ms    11 ms  dtr01sstlmo-tge-0-0-1-2.sstl.mo.charter.com [96.34.49.141]<br>
  4    16 ms    15 ms    10 ms  crr01blvlil-bue-20.blvl.il.charter.com [96.34.76.198]<br>
  5    18 ms    18 ms    14 ms  bbr01blvlil-bue-80.blvl.il.charter.com [96.34.2.168]<br>
  6    17 ms    21 ms    14 ms  bbr01olvemo-bue-3.olve.mo.charter.com [96.34.0.14]<br>
  7    22 ms    23 ms    29 ms  bbr02chcgil-bue-2.chcg.il.charter.com [96.34.0.12]<br>
  8    19 ms    17 ms    21 ms  prr01chcgil-bue-4.chcg.il.charter.com [96.34.3.11]<br>
  9    20 ms    20 ms    17 ms  96-34-152-11.static.unas.mo.charter.com [96.34.152.11]<br>
 10    26 ms    29 ms    30 ms  52.95.62.22<br>
 11    20 ms    27 ms    18 ms  52.95.62.31<br>
 12    44 ms    37 ms    40 ms  52.95.62.148<br>
 13    39 ms    43 ms    37 ms  54.239.42.59<br>
 14    39 ms    43 ms    50 ms  54.239.42.198<br>
 15    68 ms    62 ms    61 ms  54.239.110.153<br>
 16    45 ms    47 ms    37 ms  54.239.108.199<br>
 17    62 ms    40 ms    42 ms  52.93.24.10<br>
 18    41 ms    39 ms    48 ms  52.93.24.5<br>
 19     *        *        *     Request timed out.<br>
 20     *        *        *     Request timed out.<br>
 21     *        *        *     Request timed out.<br>
 22     *        *        *     Request timed out.<br>
 23     *        *        *     Request timed out.<br>
 24     *        *        *     Request timed out.<br>
 25     *        *        *     Request timed out.<br>
 26     *        *        *     Request timed out.<br>
 27     *        *        *     Request timed out.<br>
 28     *        *        *     Request timed out.<br>
 29     *        *        *     Request timed out.<br>
 30     *        *        *     Request timed out.<br>
<br>
Trace complete.</div>
<br>
<p></p>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> Outages <outages-bounces@outages.org> on behalf of outages-request@outages.org <outages-request@outages.org><br>
<b>Sent:</b> Friday, October 21, 2016 12:53 PM<br>
<b>To:</b> outages@outages.org<br>
<b>Subject:</b> Outages Digest, Vol 101, Issue 51</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send Outages mailing list submissions to<br>
        outages@outages.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
        <a href="https://puck.nether.net/mailman/listinfo/outages" id="LPlnk736992" previewremoved="true">
https://puck.nether.net/mailman/listinfo/outages</a>
<div id="LPBorder_GT_14770728426640.5421126553253053" style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id="LPContainer_14770728426610.7017635970507436" style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td id="TextCell_14770728426620.5533053847648928" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" colspan="2">
<div id="LPRemovePreviewContainer_14770728426620.0804695811067081"></div>
<div id="LPTitle_14770728426620.5821359207910005" style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;">
<a id="LPUrlAnchor_14770728426620.7671040903055492" style="text-decoration: none;" href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">Outages Info Page - Welcome to puck.nether.net</a></div>
<div id="LPMetadata_14770728426630.14807561767989652" style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;">
puck.nether.net</div>
<div id="LPDescription_14770728426630.8801957297728289" style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;">
Welcome to the outages list! The primary goal of this mailing list ("outages") is for outages-reporting that would apply to failures of major communications ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
or, via email, send a message with subject or body 'help' to<br>
        outages-request@outages.org<br>
<br>
You can reach the person managing the list at<br>
        outages-owner@outages.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Outages digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
   1. Re: Dyn outage continuing (David Miller)<br>
   2. Re: Dyn outage continuing (Sajal Kayan)<br>
   3. Re: Dyn outage continuing (Kun, Mike)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 21 Oct 2016 13:39:27 -0400<br>
From: David Miller <dmiller@tiggee.com><br>
To: "Patrick W. Gilmore" <patrick@ianai.net><br>
Cc: "outages@outages.org" <outages@outages.org><br>
Subject: Re: [outages] Dyn outage continuing<br>
Message-ID:<br>
        <CAE5R536-sMam2OtgQomsxPK=U858d7RgZNWpvJWeWoqL5DK5gw@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
What are you basing your claims on?<br>
<br>
On Fri, Oct 21, 2016 at 1:09 PM, Patrick W. Gilmore via Outages<br>
<outages@outages.org> wrote:<br>
> It is a shame in that PagerDuty is affected.<br>
><br>
> However, Dyn is far, far better positioned to withstand attacks than a<br>
> company like PagerDuty could possibly be on their own. So I think PagerDuty<br>
> did the right thing in using Dyn.<br>
><br>
> Remember, Twitter, Pingdom, github, and lots of other people use Dyn. And<br>
> this is the first major outage I have heard of their service.<br>
<br>
Everyone has issues.  Here is one:<br>
<br>
<a href="http://hub.dyn.com/dyn-status/update-managed-dns-issue-july-6-2015" id="LPlnk359354" previewremoved="true">http://hub.dyn.com/dyn-status/update-managed-dns-issue-july-6-2015</a><br>
<br>
> Let?s all be clear that Dyn has to be in the top 10 DNS infrastructures on<br>
> the planet. Possibly the largest that sells DNS as a service. This is a<br>
> serious attack, and the entire community should help track this miscreant<br>
> down, then crush them like a bug.<br>
<br>
Let's actually be clear...<br>
<br>
Do you have some inside information the rest of us are not privy to?  Sources?<br>
<br>
How did you come to your earlier statement re: this being a ransom attack?<br>
<br>
Do you have detailed information describing the top 10 DNS<br>
infrastructures on the planet, such that you could make any sort of<br>
comparison of infrastructure or size?  I'll grant you Akamai, how<br>
about the other 9?<br>
<br>
What do you know about this attack, such that you can make claims that<br>
this is "serious" or that there is a single miscreant that can be<br>
tracked down or that the community can assist in any way?<br>
<br>
Without actual details this looks to be wild conjecture and doesn't<br>
provide any helpful direction.<br>
<br>
-DMM<br>
[ I work for DNS Made Easy ]<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 21 Oct 2016 17:40:23 +0000<br>
From: Sajal Kayan <sajal83@gmail.com><br>
To: Andrew Bunde <abunde@tower-research.com>, "outages@outages.org"<br>
        <outages@outages.org><br>
Subject: Re: [outages] Dyn outage continuing<br>
Message-ID:<br>
        <CAPdYNsB4n=81ROM41CXLQzQ13oD8G83N65L17r=7=5ucsQLFkg@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
It appears most of the world cant reach Dyn :<br>
<a href="https://pulse.turbobytes.com/results/580a5178ecbe402e2201a74c/" id="LPlnk116660" previewremoved="true">https://pulse.turbobytes.com/results/580a5178ecbe402e2201a74c/</a>
<div id="LPBorder_GT_14770729039270.3749479145020821" style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id="LPContainer_14770729039250.987374846913588" style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td id="TextCell_14770729039250.5449605922921089" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" colspan="2">
<div id="LPRemovePreviewContainer_14770729039250.08748338649036458"></div>
<div id="LPTitle_14770729039250.19880272514706743" style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;">
<a id="LPUrlAnchor_14770729039260.7085316131772756" style="text-decoration: none;" href="https://pulse.turbobytes.com/results/580a5178ecbe402e2201a74c/" target="_blank">TurboBytes Pulse: global DNS, HTTP and Traceroute testing</a></div>
<div id="LPMetadata_14770729039260.7744027243649076" style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;">
pulse.turbobytes.com</div>
<div id="LPDescription_14770729039270.029694226809764968" style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;">
{{metadesc}}</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
But for the most part, its resolving thru Google DNS/OpenDNS :<br>
<a href="https://pulse.turbobytes.com/results/580a51ceecbe402e2201a74e/" id="LPlnk156658" previewremoved="true">https://pulse.turbobytes.com/results/580a51ceecbe402e2201a74e/</a>
<div id="LPBorder_GT_14770729041840.1531806878588291" style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id="LPContainer_14770729041820.13447404297505383" style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td id="TextCell_14770729041820.9492511680085484" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" colspan="2">
<div id="LPRemovePreviewContainer_14770729041820.41374060829513915"></div>
<div id="LPTitle_14770729041830.4526687533787369" style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;">
<a id="LPUrlAnchor_14770729041830.38837334883057983" style="text-decoration: none;" href="https://pulse.turbobytes.com/results/580a51ceecbe402e2201a74e/" target="_blank">TurboBytes Pulse: global DNS, HTTP and Traceroute testing</a></div>
<div id="LPMetadata_14770729041830.7129621198528081" style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;">
pulse.turbobytes.com</div>
<div id="LPDescription_14770729041840.6093559375576455" style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;">
{{metadesc}}</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
<br>
On Sat, Oct 22, 2016 at 12:31 AM Andrew Bunde via Outages <<br>
outages@outages.org> wrote:<br>
<br>
> Don?t forget <a href="https://bit.namecoin.info/" id="LPlnk885070" previewremoved="true">
https://bit.namecoin.info/</a>
<div id="LPBorder_GT_14770729013720.625073411464714" style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id="LPContainer_14770729013700.7757732538108436" style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td id="TextCell_14770729013700.66290088137762" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" colspan="2">
<div id="LPRemovePreviewContainer_14770729013710.21569901386977752"></div>
<div id="LPTitle_14770729013710.16500462515466763" style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;">
<a id="LPUrlAnchor_14770729013710.4889072321902861" style="text-decoration: none;" href="https://bit.namecoin.info/" target="_blank">Dot-Bit: Secure Decentralized DNS</a></div>
<div id="LPMetadata_14770729013710.17817023403704024" style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;">
bit.namecoin.info</div>
<div id="LPDescription_14770729013720.04817576355938935" style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;">
Dot-Bit. Dot-Bit-enabled websites end with ".bit" instead of ".com" or something similar. Dot-Bit uses Bitcoin technology to decentralize and free website addresses ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
><br>
><br>
><br>
><br>
><br>
> *From:* Outages [<a href="mailto:outages-bounces@outages.org">mailto:outages-bounces@outages.org</a>] *On Behalf Of *Jason<br>
> Antman via Outages<br>
> *Sent:* Friday, October 21, 2016 1:25 PM<br>
> *Cc:* outages@outages.org<br>
><br>
><br>
> *Subject:* Re: [outages] Dyn outage continuing<br>
><br>
><br>
><br>
> This is just a horribly painful example of why we/they should all follow<br>
> the route of NetFlix (<br>
> <a href="http://techblog.netflix.com/2013/05/denominating-multi-region-sites.html">
http://techblog.netflix.com/2013/05/denominating-multi-region-sites.html</a><br>
> ) and use multiple DNS providers. Denominator (<br>
> <a href="https://github.com/Netflix/denominator">https://github.com/Netflix/denominator</a> ) the tool NetFlix uses for this<br>
> and open-sourced, currently supports managing (mirrored) DNS records across<br>
> AWS Route53, RackSpace CloudDNS, DynECT and UltraDNS.<br>
><br>
><br>
><br>
> -Jason<br>
><br>
><br>
><br>
> On Fri, Oct 21, 2016 at 1:09 PM, Patrick W. Gilmore via Outages <<br>
> outages@outages.org> wrote:<br>
><br>
> It is a shame in that PagerDuty is affected.<br>
><br>
><br>
><br>
> However, Dyn is far, far better positioned to withstand attacks than a<br>
> company like PagerDuty could possibly be on their own. So I think PagerDuty<br>
> did the right thing in using Dyn.<br>
><br>
><br>
><br>
> Remember, Twitter, Pingdom, github, and lots of other people use Dyn. And<br>
> this is the first major outage I have heard of their service.<br>
><br>
><br>
><br>
> Let?s all be clear that Dyn has to be in the top 10 DNS infrastructures on<br>
> the planet. Possibly the largest that sells DNS as a service. This is a<br>
> serious attack, and the entire community should help track this miscreant<br>
> down, then crush them like a bug.<br>
><br>
><br>
><br>
> --<br>
><br>
> TTFN,<br>
><br>
> patrick<br>
><br>
><br>
><br>
> On Oct 21, 2016, at 1:00 PM, Terry Hardie via Outages <outages@outages.org><br>
> wrote:<br>
><br>
><br>
><br>
> It's a shame services like PagerDuty use Dyn. Now they're down too...<br>
><br>
> On Fri, Oct 21, 2016 at 9:57 AM, Justin Krejci via Outages<br>
> <outages@outages.org> wrote:<br>
><br>
> Previously it was not affecting upper midwest for me, traces went to<br>
> Chicago.<br>
><br>
> Now traces to twitter DNS servers in Chicago are failing.<br>
><br>
><br>
> ________________________________<br>
> From: Neil Hanlon via Outages [outages@outages.org]<br>
> Sent: Friday, October 21, 2016 11:16 AM<br>
> To: Terry Hardie; outages@outages.org<br>
> Subject: Re: [outages] Dyn outage continuing<br>
><br>
> The attacks appear to be continuing again. We are experiencing issues in<br>
> Europe/Asia.<br>
><br>
> On Fri, Oct 21, 2016 at 12:13 PM Terry Hardie via Outages<br>
> <outages@outages.org> wrote:<br>
><br>
><br>
> Even though their page says the outage is resolved, I'm still getting<br>
> DNS failures (return SERVFAIL, not no answer) to their anycast<br>
> networks from California:<br>
><br>
> $ dig @ns2.p34.dynect.net video.twimg.com<br>
><br>
> ; <<>> DiG 9.3.2 <<>> @ns2.p34.dynect.net video.twimg.com<br>
> ; (1 server found)<br>
> ;; global options:  printcmd<br>
> ;; Got answer:<br>
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 170<br>
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0<br>
><br>
> ;; QUESTION SECTION:<br>
> ;video.twimg.com.               IN      A<br>
><br>
> ;; Query time: 3103 msec<br>
> ;; SERVER: 204.13.250.34#53(204.13.250.34)<br>
> ;; WHEN: Fri Oct 21 17:11:36 2016<br>
> ;; MSG SIZE  rcvd: 33<br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
><br>
><br>
> --<br>
><br>
> KAYAK<br>
><br>
> Neil Hanlon<br>
><br>
> Devops Engineer<br>
><br>
><br>
> +1 978 902 8171<br>
><br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
><br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
><br>
><br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/outages/attachments/20161021/002b8297/attachment-0001.html">https://puck.nether.net/pipermail/outages/attachments/20161021/002b8297/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 21 Oct 2016 17:53:10 +0000<br>
From: "Kun, Mike" <mkun@akamai.com><br>
To: Sajal Kayan <sajal83@gmail.com><br>
Cc: Andrew Bunde <abunde@tower-research.com>, "outages@outages.org"<br>
        <outages@outages.org><br>
Subject: Re: [outages] Dyn outage continuing<br>
Message-ID: <98A4E087-1FF1-4306-B4F7-C13D1E3A79F9@akamai.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Does anyone have volume or attack information? What sort of attack(s) are suspected?<br>
<br>
-Mike Kun<br>
> On Oct 21, 2016, at 1:40 PM, Sajal Kayan via Outages <outages@outages.org> wrote:<br>
> <br>
> It appears most of the world cant reach Dyn : <a href="https://pulse.turbobytes.com/results/580a5178ecbe402e2201a74c/">
https://pulse.turbobytes.com/results/580a5178ecbe402e2201a74c/</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__pulse.turbobytes.com_results_580a5178ecbe402e2201a74c_&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=xo1rCQZipTQbUei0LoYKV-rqVaj3BIcZ11klJCE8lIM&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__pulse.turbobytes.com_results_580a5178ecbe402e2201a74c_&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=xo1rCQZipTQbUei0LoYKV-rqVaj3BIcZ11klJCE8lIM&e=</a>><br>
> But for the most part, its resolving thru Google DNS/OpenDNS : <a href="https://pulse.turbobytes.com/results/580a51ceecbe402e2201a74e/">
https://pulse.turbobytes.com/results/580a51ceecbe402e2201a74e/</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__pulse.turbobytes.com_results_580a51ceecbe402e2201a74e_&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=QGOdvuwYNF_7tdMiWdrf0JaBxlalMIIdfStw8rcnLDE&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__pulse.turbobytes.com_results_580a51ceecbe402e2201a74e_&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=QGOdvuwYNF_7tdMiWdrf0JaBxlalMIIdfStw8rcnLDE&e=</a>><br>
> <br>
> <br>
> On Sat, Oct 22, 2016 at 12:31 AM Andrew Bunde via Outages <outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>>> wrote:<br>
> Don?t forget <a href="https://bit.namecoin.info/">https://bit.namecoin.info/</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__bit.namecoin.info_&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=rJP7Os_7EgCO59pliAnbnIx4WmpVRgaKUsTNRUIgIG8&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__bit.namecoin.info_&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=rJP7Os_7EgCO59pliAnbnIx4WmpVRgaKUsTNRUIgIG8&e=</a>><br>
> <br>
> <br>
> <br>
> <br>
> From: Outages [<a href=""></a>mailto:outages-bounces@outages.org <<a href="mailto:outages-bounces@outages.org">mailto:outages-bounces@outages.org</a>>] On Behalf Of Jason Antman via Outages<br>
> Sent: Friday, October 21, 2016 1:25 PM<br>
> Cc: outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>><br>
> <br>
> Subject: Re: [outages] Dyn outage continuing<br>
> <br>
> <br>
> <br>
> This is just a horribly painful example of why we/they should all follow the route of NetFlix (
<a href="http://techblog.netflix.com/2013/05/denominating-multi-region-sites.html">
http://techblog.netflix.com/2013/05/denominating-multi-region-sites.html</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__techblog.netflix.com_2013_05_denominating-2Dmulti-2Dregion-2Dsites.html&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=Z8GkKqlEGlieBt3NindCLAcFVWecC-y9JLtSKzsWPxg&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__techblog.netflix.com_2013_05_denominating-2Dmulti-2Dregion-2Dsites.html&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=Z8GkKqlEGlieBt3NindCLAcFVWecC-y9JLtSKzsWPxg&e=</a>>
 ) and use multiple DNS providers. Denominator ( <a href="https://github.com/Netflix/denominator">
https://github.com/Netflix/denominator</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Netflix_denominator&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=5IyT0KIl6YhsW30mOHzSC6O5nLy_kYKPNEzYvg2Nr7U&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Netflix_denominator&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=5IyT0KIl6YhsW30mOHzSC6O5nLy_kYKPNEzYvg2Nr7U&e=</a>>
 ) the tool NetFlix uses for this and open-sourced, currently supports managing (mirrored) DNS records across AWS Route53, RackSpace CloudDNS, DynECT and UltraDNS.<br>
> <br>
> <br>
> <br>
> -Jason<br>
> <br>
> <br>
> <br>
> On Fri, Oct 21, 2016 at 1:09 PM, Patrick W. Gilmore via Outages <outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>>> wrote:<br>
> <br>
> It is a shame in that PagerDuty is affected.<br>
> <br>
> <br>
> <br>
> However, Dyn is far, far better positioned to withstand attacks than a company like PagerDuty could possibly be on their own. So I think PagerDuty did the right thing in using Dyn.<br>
> <br>
> <br>
> <br>
> Remember, Twitter, Pingdom, github, and lots of other people use Dyn. And this is the first major outage I have heard of their service.<br>
> <br>
> <br>
> <br>
> Let?s all be clear that Dyn has to be in the top 10 DNS infrastructures on the planet. Possibly the largest that sells DNS as a service. This is a serious attack, and the entire community should help track this miscreant down, then crush them like a bug.<br>
> <br>
> <br>
> <br>
> --<br>
> <br>
> TTFN,<br>
> <br>
> patrick<br>
> <br>
> <br>
> <br>
> On Oct 21, 2016, at 1:00 PM, Terry Hardie via Outages <outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>>> wrote:<br>
> <br>
> <br>
> <br>
> It's a shame services like PagerDuty use Dyn. Now they're down too...<br>
> <br>
> On Fri, Oct 21, 2016 at 9:57 AM, Justin Krejci via Outages<br>
> <outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>>> wrote:<br>
> <br>
> <br>
> Previously it was not affecting upper midwest for me, traces went to<br>
> Chicago.<br>
> <br>
> Now traces to twitter DNS servers in Chicago are failing.<br>
> <br>
> <br>
> ________________________________<br>
> From: Neil Hanlon via Outages [outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>>]<br>
> Sent: Friday, October 21, 2016 11:16 AM<br>
> To: Terry Hardie; outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>><br>
> Subject: Re: [outages] Dyn outage continuing<br>
> <br>
> The attacks appear to be continuing again. We are experiencing issues in<br>
> Europe/Asia.<br>
> <br>
> On Fri, Oct 21, 2016 at 12:13 PM Terry Hardie via Outages<br>
> <outages@outages.org <<a href="mailto:outages@outages.org">mailto:outages@outages.org</a>>> wrote:<br>
> <br>
> <br>
> <br>
> Even though their page says the outage is resolved, I'm still getting<br>
> DNS failures (return SERVFAIL, not no answer) to their anycast<br>
> networks from California:<br>
> <br>
> $ dig @ns2.p34.dynect.net <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__ns2.p34.dynect.net&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=nYgZcWsJA0qHxpscoM-las_Fkv2f_TC9OWy-twSs530&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__ns2.p34.dynect.net&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=nYgZcWsJA0qHxpscoM-las_Fkv2f_TC9OWy-twSs530&e=</a>>
 video.twimg.com <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__video.twimg.com&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=3YtpUj_uVR1HzhOlgLFT2JMnLwLB4rzUWdpUQq61Ht0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__video.twimg.com&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=3YtpUj_uVR1HzhOlgLFT2JMnLwLB4rzUWdpUQq61Ht0&e=</a>><br>
> <br>
> ; <<>> DiG 9.3.2 <<>> @ns2.p34.dynect.net <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__ns2.p34.dynect.net&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=nYgZcWsJA0qHxpscoM-las_Fkv2f_TC9OWy-twSs530&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__ns2.p34.dynect.net&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=nYgZcWsJA0qHxpscoM-las_Fkv2f_TC9OWy-twSs530&e=</a>>
 video.twimg.com <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__video.twimg.com&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=3YtpUj_uVR1HzhOlgLFT2JMnLwLB4rzUWdpUQq61Ht0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__video.twimg.com&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=3YtpUj_uVR1HzhOlgLFT2JMnLwLB4rzUWdpUQq61Ht0&e=</a>><br>
> ; (1 server found)<br>
> ;; global options:  printcmd<br>
> ;; Got answer:<br>
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 170<br>
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0<br>
> <br>
> ;; QUESTION SECTION:<br>
> ;video.twimg.com <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__video.twimg.com&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=3YtpUj_uVR1HzhOlgLFT2JMnLwLB4rzUWdpUQq61Ht0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__video.twimg.com&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=3YtpUj_uVR1HzhOlgLFT2JMnLwLB4rzUWdpUQq61Ht0&e=</a>>.              
 IN      A<br>
> <br>
> ;; Query time: 3103 msec<br>
> ;; SERVER: 204.13.250.34#53(204.13.250.34)<br>
> ;; WHEN: Fri Oct 21 17:11:36 2016<br>
> ;; MSG SIZE  rcvd: 33<br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org <<a href="mailto:Outages@outages.org">mailto:Outages@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=</a>><br>
> <br>
> --<br>
> <br>
> KAYAK<br>
> <br>
> Neil Hanlon<br>
> <br>
> Devops Engineer<br>
> <br>
> <br>
> +1 978 902 8171 <tel:%2B1%20978%20902%208171><br>
> <br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org <<a href="mailto:Outages@outages.org">mailto:Outages@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=</a>><br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org <<a href="mailto:Outages@outages.org">mailto:Outages@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=</a>><br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org <<a href="mailto:Outages@outages.org">mailto:Outages@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=</a>><br>
> <br>
> <br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org <<a href="mailto:Outages@outages.org">mailto:Outages@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a> <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DQMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=JKX8L6GOKvRiNpSp-mnjjQ&m=NlUSnBfE_pOQTYFrnNz03CXHFDf-thc56BitRGGX2HE&s=XPLQiTtTSnqFkQpyPWGEQCbi4k2BRGuDxT51QCjhMpY&e=</a>><br>
> _______________________________________________<br>
> Outages mailing list<br>
> Outages@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/outages/attachments/20161021/2f1f08a9/attachment.html">https://puck.nether.net/pipermail/outages/attachments/20161021/2f1f08a9/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 842 bytes<br>
Desc: Message signed with OpenPGP using GPGMail<br>
URL: <<a href="https://puck.nether.net/pipermail/outages/attachments/20161021/2f1f08a9/attachment.sig">https://puck.nether.net/pipermail/outages/attachments/20161021/2f1f08a9/attachment.sig</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
Outages@outages.org<br>
<a href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Outages Digest, Vol 101, Issue 51<br>
****************************************<br>
</div>
</span></font></div>
</div>
</body>
</html>