That is where the trace-routes come in. Do some investigation before you make a general query.
_Google WAS down for us, and potentially others who route that traffic through Internet2. _ _Here is what I am seeing_ _Trace-route 10/10/10/1 tracing route to google via rtsw.clev.net.internet2.edu_ Tracing route to google.com: ******** ******** Etc. Richard On 12/10/19 4:06 PM, Begarowicz, Shawn via Outages wrote: > I think being more specific with region area would solve this issue > > > Thank You, > Shawn Begarowicz (Technology/Service Manager) > Complete Interactive Technologies > 44265 Groesbeck Highway > Clinton Township, MI 48036 > 586-439-2000 Ext. 120 | 586-439-2001 Fax > 586-913-2420 Direct Tel | 586-203-4940 Direct Fax > 586-883-4037 Cell > shawn.begarow...@cit-4u.com > www.cit-4u.com > For Technical Support: > supp...@cit-4u.com > Website: > www.cit-4u.com > cid:image003.png@01CF7F09.DECD1850 > > Celebrating 30 Years of your VISION our SOLUTION > > 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. > Please think twice before printing out this email! > ------------------------------------------------------------------------ > *From:* Outages <outages-boun...@outages.org> on behalf of Matt Hoppes > via Outages <outages@outages.org> > *Sent:* Tuesday, December 10, 2019 5:01:06 PM > *To:* Brad Vanden Boogaard <brad...@gmail.com> > *Cc:* OUTAGES Mailing List <outages@outages.org> > *Subject:* Re: [outages] Google Down? > > 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). > > So where does the line get drawn? Google WAS down for us, and > potentially others who route that traffic through Internet2. > > > > On Dec 10, 2019, at 4:53 PM, Brad Vanden Boogaard <brad...@gmail.com > <mailto:brad...@gmail.com>> wrote: > >> Weighing in here, >> >> I believe the purpose of the outages list is mostly to report >> confirmed outages. From the site >> "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 " >> >> 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: >> 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. >> >> As mentioned by another user, discussion can be used for post-mortem, >> troubleshooting, and discussion. >> outages-discuss...@outages.org >> <mailto:outages-discuss...@outages.org> - Post outages >> meta-discussion (troubleshooting, analysis, post-mortem, etc) >> >> "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. >> >> 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. >> >> Thanks and regards, >> >> On Tue, Dec 10, 2019 at 4:12 PM Mike Bolitho via Outages >> <outages@outages.org <mailto:outages@outages.org>> wrote: >> >> outages-discuss...@outages.org >> <mailto:outages-discuss...@outages.org> >> >> "Post outages related discussion, including troubleshooting, >> analysis, post-mortem pertaining to ongoing or post outages." >> >> - Mike Bolitho >> >> >> On Tue, Dec 10, 2019 at 1:57 PM Matt Hoppes via Outages >> <outages@outages.org <mailto:outages@outages.org>> wrote: >> >> Brett >> >> So what is this list for then? I see posts often about >> "Office 362 is >> down from WallaWalla". How is that different than "Is Office >> 362 down >> for anyone else"? >> >> In all cases, major internet sites WERE down.... to what >> extent or >> geographic area remains to be seen. >> >> Is there a geographic limit to the outage list? For example, >> if Google >> is only down to New York Comcast customers, is that an outage >> or an >> outage-discussion post? >> >> On 12/10/19 3:50 PM, Brett Dikeman wrote: >> > *Yet another reminder* that this list is not for >> troubleshooting, >> > discussion, diagnostics, polling people if something is >> down, etc. *Take >> > it to the -discuss list.* >> > >> > Also, it is worth noting that Mr. Hoppes has on >> *several* occasions >> > pinged this list to ask if various major internet sites are >> down, when >> > they were in fact not down. >> > >> > On Tue, Dec 10, 2019 at 3:34 PM Ross Tajvar via Outages >> > <outages@outages.org <mailto:outages@outages.org> >> <mailto:outages@outages.org <mailto:outages@outages.org>>> wrote: >> > >> > What region/ISP? >> > >> > On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages >> > <outages@outages.org <mailto:outages@outages.org> >> <mailto:outages@outages.org <mailto:outages@outages.org>>> wrote: >> > >> > As of 3:25pm Eastern we've lost access to all >> things Google -- >> > Hangouts, >> > Youtube, Google Search. >> > >> > Even pinging google.com <http://google.com> >> <http://google.com> results in no response. >> > _______________________________________________ >> > Outages mailing list >> > Outages@outages.org <mailto:Outages@outages.org> >> <mailto:Outages@outages.org <mailto:Outages@outages.org>> >> > https://puck.nether.net/mailman/listinfo/outages >> > >> > _______________________________________________ >> > Outages mailing list >> > Outages@outages.org <mailto:Outages@outages.org> >> <mailto:Outages@outages.org <mailto:Outages@outages.org>> >> > https://puck.nether.net/mailman/listinfo/outages >> > >> _______________________________________________ >> Outages mailing list >> Outages@outages.org <mailto:Outages@outages.org> >> https://puck.nether.net/mailman/listinfo/outages >> >> _______________________________________________ >> Outages mailing list >> Outages@outages.org <mailto:Outages@outages.org> >> https://puck.nether.net/mailman/listinfo/outages >> > > _______________________________________________ > Outages mailing list > Outages@outages.org > https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages