<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>T<font size="+1">hat is where the trace-routes come in.</font></p>
    <p><font size="+1">Do some investigation before you make a general
        query.<br>
      </font></p>
    <p><u><font size="+1">Google WAS down for us, and potentially others
          who route that traffic through Internet2. <br>
        </font></u></p>
    <p><u><font size="+1">Here is what I am seeing</font></u></p>
    <p><u><font size="+1">Trace-route 10/10/10/1 tracing route to google
          via rtsw.clev.net.internet2.edu</font></u></p>
    <p><font size="+1">Tracing route to google.com:</font></p>
    <p><font size="+1">********</font></p>
    <p><font size="+1">********</font></p>
    <p><font size="+1">Etc.</font></p>
    <p><font size="+1">Richard</font><br>
    </p>
    <div dir="ltr"><br>
    </div>
    <div dir="ltr"><br>
    </div>
    <div class="moz-cite-prefix">On 12/10/19 4:06 PM, Begarowicz, Shawn
      via Outages wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:DM6PR12MB324243B4663248AEBB58D5CCF15B0@DM6PR12MB3242.namprd12.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>
        <div>
          <div style="direction: ltr;">I think being more specific with
            region area would solve this issue
          </div>
        </div>
        <div><br>
        </div>
        <div class="ms-outlook-ios-signature">
          <div><br>
          </div>
          <div style="direction: ltr;">Thank You,</div>
          <div style="direction: ltr;">Shawn Begarowicz
            (Technology/Service Manager)</div>
          <div style="direction: ltr;">Complete Interactive Technologies</div>
          <div style="direction: ltr;">44265 Groesbeck Highway</div>
          <div style="direction: ltr;">Clinton Township, MI 48036</div>
          <div style="direction: ltr;">586-439-2000 Ext. 120 |
            586-439-2001 Fax</div>
          <div style="direction: ltr;">586-913-2420 Direct Tel |
            586-203-4940 Direct Fax</div>
          <div style="direction: ltr;">586-883-4037 Cell</div>
          <div style="direction: ltr;"><a class="moz-txt-link-abbreviated" href="mailto:shawn.begarowicz@cit-4u.com">shawn.begarowicz@cit-4u.com</a></div>
          <div style="direction: ltr;"><a class="moz-txt-link-abbreviated" href="http://www.cit-4u.com">www.cit-4u.com</a></div>
          <div style="direction: ltr;">For Technical Support:</div>
          <div style="direction: ltr;"><a class="moz-txt-link-abbreviated" href="mailto:support@cit-4u.com">support@cit-4u.com</a></div>
          <div style="direction: ltr;">Website:</div>
          <div style="direction: ltr;"><a class="moz-txt-link-abbreviated" href="http://www.cit-4u.com">www.cit-4u.com</a></div>
          <div style="direction: ltr;"><a class="moz-txt-link-freetext" href="cid:image003.png@01CF7F09.DECD1850">cid:image003.png@01CF7F09.DECD1850</a></div>
          <div><br>
          </div>
          <div style="direction: ltr;">Celebrating 30 Years of your
            VISION our SOLUTION</div>
          <div><br>
          </div>
          <div style="direction: ltr;">The information contained in this
            message is confidential and, if addressed to a client or
            certain counsel, is subject to the attorney-client or
            work-product privilege, and is intended only for the use of
            the individual or entity named above. If the reader of this
            message is not the intended recipient, you are hereby
            notified that any dissemination, distribution or copying of
            this communication is strictly prohibited. If you have
            received this communication in error, please reply or notify
            us immediately by email or telephone, and destroy or erase
            the message.</div>
          <div style="direction: ltr;">Please think twice before
            printing out this email!</div>
        </div>
      </div>
      <hr style="display:inline-block;width:98%" tabindex="-1">
      <div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
          face="Calibri, sans-serif" color="#000000"><b>From:</b>
          Outages <a class="moz-txt-link-rfc2396E" href="mailto:outages-bounces@outages.org"><outages-bounces@outages.org></a> on behalf of Matt
          Hoppes via Outages <a class="moz-txt-link-rfc2396E" href="mailto:outages@outages.org"><outages@outages.org></a><br>
          <b>Sent:</b> Tuesday, December 10, 2019 5:01:06 PM<br>
          <b>To:</b> Brad Vanden Boogaard <a class="moz-txt-link-rfc2396E" href="mailto:brad.vb@gmail.com"><brad.vb@gmail.com></a><br>
          <b>Cc:</b> OUTAGES Mailing List <a class="moz-txt-link-rfc2396E" href="mailto:outages@outages.org"><outages@outages.org></a><br>
          <b>Subject:</b> Re: [outages] Google Down?</font>
        <div> </div>
      </div>
      <div dir="auto">
        <div dir="ltr">Ok. But here’s where I’m confused. I know believe
          the Google issue we experienced was related to the Internet2
          issue (we peer with them).</div>
        <div dir="ltr"><br>
        </div>
        <div dir="ltr">So where does the line get drawn?  Google WAS
          down for us, and potentially others who route that traffic
          through Internet2. </div>
        <div dir="ltr"><br>
        </div>
        <div dir="ltr"><br>
        </div>
        <div dir="ltr"><br>
          On Dec 10, 2019, at 4:53 PM, Brad Vanden Boogaard <<a
            href="mailto:brad.vb@gmail.com" moz-do-not-send="true">brad.vb@gmail.com</a>>
          wrote:<br>
          <br>
        </div>
        <blockquote type="cite">
          <div dir="ltr">
            <div dir="ltr">  Weighing in here,
              <div><br>
              </div>
              <div>I believe the purpose of the outages list is mostly
                to report confirmed outages.  From the site </div>
              <div><font face="monospace">"The primary goal of this
                  mailing list ("outages") is for outages-reporting that
                  would apply to failures of major communications
                  infrastructure components having significant
                  traffic-carrying capacity "
                </font><br>
                <div><br>
                </div>
                <div>It should not be used for troubleshooting.  If you
                  are seeing issues and have spoken with your carrier
                  who confirmed that they have a major fiber cut,
                  reporting it here saves many people a large number of
                  phone calls and ticket creations.  Also from their
                  site:</div>
                <font face="monospace">The purpose of this list is to
                  have a central place to lookup and report so that end
                  users & network operators know why their services
                  (e-mail, phones, etc) went down eliminating the need
                  to open tons of trouble tickets during a major event.
                  One master ticket - such as fiber cut affect xxx
                  OC48's would suffice. We hope this would empower users
                  and network operators to post such events so that
                  everyone could benefit from it.  </font>
                <div><br>
                </div>
                <div>As mentioned by another user, discussion can be
                  used for post-mortem, troubleshooting, and discussion.</div>
                <font face="monospace"><a
                    href="mailto:outages-discussion@outages.org"
                    moz-do-not-send="true">outages-discussion@outages.org</a>
                  - Post outages meta-discussion (troubleshooting,
                  analysis, post-mortem, etc)  </font>
                <div><br>
                </div>
                <div>"I am seeing x issue, is anyone else seeing x
                  issue" is part of the troubleshooting process.  This
                  is part of discovering the scope and whether your
                  infrastructure or carrier infrastructure is facing
                  issues.</div>
                <div><br clear="all">
                  <div>
                    <div class="x_gmail_signature">Today's outage report
                      of Internet2 around 4:30 PM EST is a good
                      example.  It lets everyone know this is an issue,
                      the incident number, and may save people initial
                      troubleshooting time.</div>
                  </div>
                </div>
              </div>
              <div class="x_gmail_signature"><br>
              </div>
              <div class="x_gmail_signature">Thanks and regards,</div>
            </div>
            <br>
            <div class="x_gmail_quote">
              <div dir="ltr" class="x_gmail_attr">On Tue, Dec 10, 2019
                at 4:12 PM Mike Bolitho via Outages <<a
                  href="mailto:outages@outages.org"
                  moz-do-not-send="true">outages@outages.org</a>>
                wrote:<br>
              </div>
              <blockquote class="x_gmail_quote" style="margin:0px 0px
                0px 0.8ex; border-left:1px solid rgb(204,204,204);
                padding-left:1ex">
                <div dir="ltr">
                  <div class="x_gmail_default"
                    style="font-family:arial,helvetica,sans-serif"><span
                      style="color:rgb(0,0,0); font-family:"Times
                      New Roman"; font-size:medium"> </span><a
                      href="mailto:outages-discussion@outages.org"
                      target="_blank" style="font-family:"Times New
                      Roman"; font-size:medium"
                      moz-do-not-send="true">outages-discussion@outages.org</a> </div>
                  <div class="x_gmail_default"
                    style="font-family:arial,helvetica,sans-serif"><br>
                  </div>
                  <div class="x_gmail_default"
                    style="font-family:arial,helvetica,sans-serif"><span
                      style="color:rgb(0,0,0); font-family:"Times
                      New Roman"; font-size:medium">"Post outages
                      related discussion, including troubleshooting,
                      analysis, post-mortem pertaining to ongoing or
                      post outages."</span> <br clear="all">
                  </div>
                  <div>
                    <div dir="ltr">
                      <div dir="ltr"><font face="arial, helvetica,
                          sans-serif" color="#000000"><br>
                          - Mike Bolitho</font></div>
                    </div>
                  </div>
                  <br>
                </div>
                <br>
                <div class="x_gmail_quote">
                  <div dir="ltr" class="x_gmail_attr">On Tue, Dec 10,
                    2019 at 1:57 PM Matt Hoppes via Outages <<a
                      href="mailto:outages@outages.org" target="_blank"
                      moz-do-not-send="true">outages@outages.org</a>>
                    wrote:<br>
                  </div>
                  <blockquote class="x_gmail_quote" style="margin:0px
                    0px 0px 0.8ex; border-left:1px solid
                    rgb(204,204,204); padding-left:1ex">
                    Brett<br>
                    <br>
                    So what is this list for then?   I see posts often
                    about "Office 362 is <br>
                    down from WallaWalla".  How is that different than
                    "Is Office 362 down <br>
                    for anyone else"?<br>
                    <br>
                    In all cases, major internet sites WERE down.... to
                    what extent or <br>
                    geographic area remains to be seen.<br>
                    <br>
                    Is there a geographic limit to the outage list?  For
                    example, if Google <br>
                    is only down to New York Comcast customers, is that
                    an outage or an <br>
                    outage-discussion post?<br>
                    <br>
                    On 12/10/19 3:50 PM, Brett Dikeman wrote:<br>
                    > *Yet another reminder* that this list is not
                    for troubleshooting, <br>
                    > discussion, diagnostics, polling people if
                    something is down, etc. *Take <br>
                    > it to the -discuss list.*<br>
                    > <br>
                    > Also, it is worth noting that Mr. Hoppes has on
                    *several* occasions <br>
                    > pinged this list to ask if various major
                    internet sites are down, when <br>
                    > they were in fact not down.<br>
                    > <br>
                    > On Tue, Dec 10, 2019 at 3:34 PM Ross Tajvar via
                    Outages <br>
                    > <<a href="mailto:outages@outages.org"
                      target="_blank" moz-do-not-send="true">outages@outages.org</a>
                    <mailto:<a href="mailto:outages@outages.org"
                      target="_blank" moz-do-not-send="true">outages@outages.org</a>>>
                    wrote:<br>
                    > <br>
                    >     What region/ISP?<br>
                    > <br>
                    >     On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes
                    via Outages<br>
                    >     <<a href="mailto:outages@outages.org"
                      target="_blank" moz-do-not-send="true">outages@outages.org</a>
                    <mailto:<a href="mailto:outages@outages.org"
                      target="_blank" moz-do-not-send="true">outages@outages.org</a>>>
                    wrote:<br>
                    > <br>
                    >         As of 3:25pm Eastern we've lost access
                    to all things Google --<br>
                    >         Hangouts,<br>
                    >         Youtube, Google Search.<br>
                    > <br>
                    >         Even pinging <a
                      href="http://google.com" rel="noreferrer"
                      target="_blank" moz-do-not-send="true">
                      google.com</a> <<a href="http://google.com"
                      rel="noreferrer" target="_blank"
                      moz-do-not-send="true">http://google.com</a>>
                    results in no response.<br>
                    >       
                     _______________________________________________<br>
                    >         Outages mailing list<br>
                    >         <a href="mailto:Outages@outages.org"
                      target="_blank" moz-do-not-send="true">Outages@outages.org</a>
                    <mailto:<a href="mailto:Outages@outages.org"
                      target="_blank" moz-do-not-send="true">Outages@outages.org</a>><br>
                    >         <a
                      href="https://puck.nether.net/mailman/listinfo/outages"
                      rel="noreferrer" target="_blank"
                      moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/outages</a><br>
                    > <br>
                    >   
                     _______________________________________________<br>
                    >     Outages mailing list<br>
                    >     <a href="mailto:Outages@outages.org"
                      target="_blank" moz-do-not-send="true">Outages@outages.org</a>
                    <mailto:<a href="mailto:Outages@outages.org"
                      target="_blank" moz-do-not-send="true">Outages@outages.org</a>><br>
                    >     <a
                      href="https://puck.nether.net/mailman/listinfo/outages"
                      rel="noreferrer" target="_blank"
                      moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/outages</a><br>
                    > <br>
                    _______________________________________________<br>
                    Outages mailing list<br>
                    <a href="mailto:Outages@outages.org" target="_blank"
                      moz-do-not-send="true">Outages@outages.org</a><br>
                    <a
                      href="https://puck.nether.net/mailman/listinfo/outages"
                      rel="noreferrer" target="_blank"
                      moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/outages</a><br>
                  </blockquote>
                </div>
                _______________________________________________<br>
                Outages mailing list<br>
                <a href="mailto:Outages@outages.org" target="_blank"
                  moz-do-not-send="true">Outages@outages.org</a><br>
                <a
                  href="https://puck.nether.net/mailman/listinfo/outages"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/outages</a><br>
              </blockquote>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Outages mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Outages@outages.org">Outages@outages.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a>
</pre>
    </blockquote>
  </body>
</html>