As of 3:25pm Eastern we've lost access to all things Google -- Hangouts, Youtube, Google Search. Even pinging google.com results in no response.
What region/ISP? On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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 results in no response. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Pennsylvania On 12/10/19 3:32 PM, Ross Tajvar wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Working here in PA. (Verizon Business, Comcast Business, Comcast Residential, CCI Inc. all tested) Might need to specify your region/ISP to get a better grasp on what's going on, might be region-specific or ISP specific to your region. On 12/10/19 3:32 PM, Ross Tajvar via Outages wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
-- Thomas ------ Thomas Ward Thomas Ward Consulting, LLC.
Or to be more specific, Allegheny County area in PA if you need region-specific identifiers to compare against. Thomas On 12/10/19 3:35 PM, Thomas Ward via Outages wrote:
Working here in PA. (Verizon Business, Comcast Business, Comcast Residential, CCI Inc. all tested)
Might need to specify your region/ISP to get a better grasp on what's going on, might be region-specific or ISP specific to your region.
On 12/10/19 3:32 PM, Ross Tajvar via Outages wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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 --
Thomas
------ Thomas Ward Thomas Ward Consulting, LLC.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Thomas ------ Thomas Ward Thomas Ward Consulting, LLC.
OK.. not sure what happened... all services, including pinging of google.com was down for about 4 minutes.. everything else worked fine. On 12/10/19 3:37 PM, Thomas Ward wrote:
Or to be more specific, Allegheny County area in PA if you need region-specific identifiers to compare against.
Thomas
On 12/10/19 3:35 PM, Thomas Ward via Outages wrote:
Working here in PA. (Verizon Business, Comcast Business, Comcast Residential, CCI Inc. all tested)
Might need to specify your region/ISP to get a better grasp on what's going on, might be region-specific or ISP specific to your region.
On 12/10/19 3:32 PM, Ross Tajvar via Outages wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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 --
Thomas
------ Thomas Ward Thomas Ward Consulting, LLC.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
--
Thomas
------ Thomas Ward Thomas Ward Consulting, LLC.
*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> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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 results in no response. _______________________________________________ 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
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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
Please take this to -discussion. On Tue, Dec 10, 2019, 3:55 PM Matt Hoppes <mattlists@rivervalleyinternet.net> 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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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-discussion@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> 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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
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-discussion@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> wrote:
outages-discussion@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> 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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
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.vb@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-discussion@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> wrote: outages-discussion@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> 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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
Posts talking about it are greater in numbers than just letting it be. Be like Dave Grohl and Let It Die Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Dec 10, 2019, 5:02 PM Matt Hoppes via Outages <outages@outages.org> wrote:
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.vb@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-discussion@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> wrote:
outages-discussion@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> 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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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.begarowicz@cit-4u.com www.cit-4u.com For Technical Support: support@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-bounces@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.vb@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.vb@gmail.com<mailto:brad.vb@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-discussion@outages.org<mailto:outages-discussion@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-discussion@outages.org<mailto:outages-discussion@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
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.begarowicz@cit-4u.com www.cit-4u.com For Technical Support: support@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-bounces@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.vb@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.vb@gmail.com <mailto:brad.vb@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-discussion@outages.org <mailto:outages-discussion@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-discussion@outages.org <mailto:outages-discussion@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
At the very least, check to see if popular availability sites like https://downforeveryoneorjustme.com https://www.isitdownrightnow.com show the same problem you're seeing. If it's up for multiple testing sites, and just affecting you, it's probably a localized issue. If multiple test sites *also* show a problem, it's probably significant enough to report. Matt On Tue, Dec 10, 2019 at 2:02 PM Matt Hoppes via Outages <outages@outages.org> wrote:
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.vb@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-discussion@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> wrote:
outages-discussion@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> 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>> wrote:
What region/ISP?
On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
In my experience it has been helpful to say, hey, Cisco.com is down for me in the Chicago area. Is anyone else experiencing this? This way you keep list bloat down to a certain geographical area and can get more accurate information to and from the community. Just my two cents and I hope it keeps list abuse down to a minimum. Sincerely, Richard Golodner
While I agree, I think this type of message should also go on -discussion. On Tue, Dec 10, 2019, 4:33 PM Richard via Outages <outages@outages.org> wrote:
In my experience it has been helpful to say, hey, Cisco.com is down for me in the Chicago area. Is anyone else experiencing this?
This way you keep list bloat down to a certain geographical area and can get more accurate information to and from the community.
Just my two cents and I hope it keeps list abuse down to a minimum.
Sincerely, Richard Golodner
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I'm in the middle of managing a domain, and adding domain names. No issues with that or email. Located in Phoenix AZ. On Tue, Dec 10, 2019 at 1:31 PM Matt Hoppes via Outages <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 results in no response. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Carlos Alvarez 602-368-6403
All three of those work here for me via Spectrum/Charter. Pinging google.com [172.217.4.110] with 32 bytes of data: Reply from 172.217.4.110: bytes=32 time=39ms TTL=51 C:\Users\jluthman>tracert google.com Tracing route to google.com [172.217.4.110] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.10.1 2 1 ms 1 ms 1 ms fwbb-192-149-254-1.inxnet.net [192.149.254.1] 3 2 ms 1 ms 1 ms fwb-74-218-88-129.inxnet.net [74.218.88.129] 4 10 ms 9 ms 10 ms network-065-189-190-191.bcs.neo.rr.com [65.189.190.191] 5 10 ms 9 ms 10 ms be39.gmtwoh0501r.midwest.rr.com [65.29.38.114] 6 12 ms 14 ms 14 ms be12.blasohdp01r.midwest.rr.com [65.29.33.68] 7 10 ms 14 ms 11 ms be28.clmkohpe01r.midwest.rr.com [65.29.1.44] 8 22 ms 29 ms 29 ms bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68] 9 26 ms 20 ms 20 ms 66.109.5.136 10 22 ms 22 ms 22 ms 66.109.5.225 11 27 ms 21 ms 22 ms ix-ae-27-0.tcore2.ct8-chicago.as6453.net [64.86.79.97] 12 45 ms 45 ms 45 ms if-ae-30-2.tcore1.w6c-montreal.as6453.net [66.198.96.25] 13 35 ms 35 ms 36 ms 209.85.149.230 14 35 ms 35 ms 35 ms 108.170.251.53 15 42 ms 42 ms 42 ms 209.85.254.199 16 40 ms 41 ms 40 ms 172.253.67.238 17 46 ms 46 ms 46 ms 209.85.250.147 18 43 ms 44 ms 44 ms 108.170.243.225 19 43 ms 43 ms 42 ms 108.170.233.111 20 40 ms 39 ms 40 ms ord36s04-in-f14.1e100.net [172.217.4.110] Trace complete. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Dec 10, 2019 at 3:31 PM Matt Hoppes via Outages <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 results in no response. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Also work for tMobile, Sprint and Cogent. -bruce ________________________________ From: Outages <outages-bounces@outages.org> on behalf of Josh Luthman via Outages <outages@outages.org> Sent: Tuesday, December 10, 2019 3:35:36 PM To: Matt Hoppes <mattlists@rivervalleyinternet.net> Cc: outages@outages.org <outages@outages.org> Subject: [EXT] Re: [outages] Google Down? All three of those work here for me via Spectrum/Charter. Pinging google.com<http://google.com> [172.217.4.110] with 32 bytes of data: Reply from 172.217.4.110<http://172.217.4.110>: bytes=32 time=39ms TTL=51 C:\Users\jluthman>tracert google.com<http://google.com> Tracing route to google.com<http://google.com> [172.217.4.110] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.10.1 2 1 ms 1 ms 1 ms fwbb-192-149-254-1.inxnet.net<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2ffwbb-192-149-254-1.inxnet.net&c=E,1,Ny9dPWrTB_25ef-11b6UNJwVePjIBj3USCWHPr3NZIIr7QJzMGruRjNnOk1Om6Q0K3FNnsAmhnVkPp83O73xAi4J6SkSEfEhlmvlKZilMXoc&typo=1> [192.149.254.1] 3 2 ms 1 ms 1 ms fwb-74-218-88-129.inxnet.net<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2ffwb-74-218-88-129.inxnet.net&c=E,1,fWAza9AwBx6P4tf4mb-zmtIZByYfPA9XWnXZ2gsJO99QB6wCJdhTEBZ--2ML01_FiJsndB3h-N6GPsHGFuYbnDq8sGVGcfDj4izEENlUMajF&typo=1> [74.218.88.129] 4 10 ms 9 ms 10 ms network-065-189-190-191.bcs.neo.rr.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fnetwork-065-189-190-191.bcs.neo.rr.com&c=E,1,FiFqPxwBnYwxb8cgeNN4NnBDxSatoDb1dhil8yY0BYp6jvBKDq7PVpCP0t4HqiJ5nv2SZTHVZ8X_inulGZWUH7ha-spqjwGEVUpvfJwnJIYEs0zPrI1RFjy0&typo=1> [65.189.190.191] 5 10 ms 9 ms 10 ms be39.gmtwoh0501r.midwest.rr.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fbe39.gmtwoh0501r.midwest.rr.com&c=E,1,dOlUJ3Rr2u4yhyiO1ziuEMgDKiVF-_uYY2l5aDyCvBaXb-d0tezmTcZmv8DYMoKSQfEnhbtPenH0xrmJVFvgb7Fk9oZE_Zb6n2YKxFWARzWah02q_w,,&typo=1> [65.29.38.114] 6 12 ms 14 ms 14 ms be12.blasohdp01r.midwest.rr.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fbe12.blasohdp01r.midwest.rr.com&c=E,1,7Ei1SC5QesFxYS2X1a8Ndr6YpIiQBByjqYxziEjwgggN2ZUtIIynET_bwEVLxf4XAKoKYQC1psttimTIiBEytLcZ8xEfLpNatUuJ3RLrkb2cW8R8-sAK__Fd7mLS&typo=1> [65.29.33.68] 7 10 ms 14 ms 11 ms be28.clmkohpe01r.midwest.rr.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fbe28.clmkohpe01r.midwest.rr.com&c=E,1,qj-OEq-PPMZVIOn32BzBnIkC9UEhnnuCzDqtqd7hy7z1JfYhnymMeb6ridfofY56QWECEqhpZe-W3tLC68uz65Xl5tu5sYPvf4P64iFI35Ju&typo=1> [65.29.1.44] 8 22 ms 29 ms 29 ms bu-ether15.chctilwc00w-bcr00.tbone.rr.com<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fbu-ether15.chctilwc00w-bcr00.tbone.rr.com&c=E,1,a4oNJZJox-AAPcm_ztV3VlXWCrqCzmMBWJBOhxwkBjG8AS8BtHHZsjprPQGWJZ96ECWzOBQVZHErjJvtP4UwcduyOe58DenCax9Cw8TBglivUQ,,&typo=1> [66.109.6.68] 9 26 ms 20 ms 20 ms 66.109.5.136 10 22 ms 22 ms 22 ms 66.109.5.225 11 27 ms 21 ms 22 ms ix-ae-27-0.tcore2.ct8-chicago.as6453.net<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fix-ae-27-0.tcore2.ct8-chicago.as6453.net&c=E,1,OgdRrl24z6BI9-X8h_S0on7Tpk0i7xX2MFK9Dk-yzrQRLmKcgM7RTY5E6QgWeugI2QRSgxRm5b_FXirRZ_6kxra10sz0JbqFi75ogwBDwld6NMUWQhFs2qk,&typo=1> [64.86.79.97] 12 45 ms 45 ms 45 ms if-ae-30-2.tcore1.w6c-montreal.as6453.net<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fif-ae-30-2.tcore1.w6c-montreal.as6453.net&c=E,1,pPLQvvJWoRhR2LWMMSdILJUceYYbDCaaYUyfKZlI2JZp9wKyE7fvBgo5celezBDwbUM_C4S1UHa6oHHPDa1DThSJoiV844IVLvbqTYW3Qes9KWgw&typo=1> [66.198.96.25] 13 35 ms 35 ms 36 ms 209.85.149.230 14 35 ms 35 ms 35 ms 108.170.251.53 15 42 ms 42 ms 42 ms 209.85.254.199 16 40 ms 41 ms 40 ms 172.253.67.238 17 46 ms 46 ms 46 ms 209.85.250.147 18 43 ms 44 ms 44 ms 108.170.243.225 19 43 ms 43 ms 42 ms 108.170.233.111 20 40 ms 39 ms 40 ms ord36s04-in-f14.1e100.net<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2ford36s04-in-f14.1e100.net&c=E,1,BD9jdb6tuVU3058Nb8bYszquFv8IOF6HHH_tAZtSb-QS8xozNoGlWCUWkcU-zAKQ0SUycmBLHNUtI6mpxmSPDiLz-yatjumPqn0pPAH2ja1XQKY,&typo=1> [172.217.4.110] Trace complete. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Dec 10, 2019 at 3:31 PM Matt Hoppes via Outages <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> results in no response. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fpuck.nether.net%2fmailman%2flistinfo%2foutages&c=E,1,DYVdodOiSFHCZt_Ce2JaqYZR_i0WcQNI4i9LIClObjRSTdccOk6pXHwnDoBjoX2Tdhtg6Oe6wpM0VNCeeEvZjCtczb9wMU5859YRrCZgsQ,,&typo=1>
participants (12)
-
Begarowicz, Shawn -
Brad Vanden Boogaard -
Brett Dikeman -
Bruce Freshwater -
Carlos Alvarez -
Josh Luthman -
Matt Hoppes -
Matthew Petach -
Mike Bolitho -
Richard -
Ross Tajvar -
Thomas Ward