Send Outages-discussion mailing list submissions to
outages-discussion@outages.org
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
outages-discussion-requ...@outages.org
You can reach the person managing the list at
outages-discussion-ow...@outages.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Re: [outages] sales critter Ben Reynolds (Jim Popovitch)
2. Re: [outages] Office 365 global outage (Gary Leato)
3. Re: [outages] Fixing "Google Down?" (Ryan Chewning)
4. Re: [outages] Fixing "Google Down?" (Mike Bolitho)
5. Re: [outages] Fixing "Google Down?" (Chris Adams)
6. Re: [outages] Fixing "Google Down?" (Matt Hoppes)
----------------------------------------------------------------------
Message: 1
Date: Sat, 19 Oct 2019 13:32:34 -0400
From: Jim Popovitch <jim...@domainmail.org>
To: Outages List <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] sales critter Ben Reynolds
Message-ID: <74023f92-8e1e-1d18-50ee-7e06be2cd...@domainmail.org>
Content-Type: text/plain; charset=utf-8; format=flowed
On 10/19/2019 12:54 PM, Jared Mauch via Outages wrote:
> This person spammed all sorts of weird addresses for projects that I run (eg:
> Open Resolver) so clearly has no clue.
>
> That domain is currently banned on my mail server so it?s unlikely they can
> get anything else through.
>
Here's the headers since nobody has posted them yet.
Received: from mail.cytranet.net (mail.cytranet.net [66.172.17.5])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by smtp.domainmail.net (Postfix) with ESMTPS id 46vqpt1Zw3z119J
for <jim...@domainmail.org>; Fri, 18 Oct 2019 15:35:02 +0000 (UTC)
Received: from [192.168.5.250]
(adsl-99-39-171-70.dsl.wlfrct.sbcglobal.net [99.39.171.70]) by
mail.cytranet.net with SMTP
(version=TLS\Tls
cipher=Aes128 bits=128);
Fri, 18 Oct 2019 10:34:51 -0500
Message-Id: <0e4ladsndpxw5zvvdbf5f7mnocgeaf3w24sezylpf...@cytranet.com>
Mime-Version: 1.0
From: Ben Reynolds <breyno...@cytranet.com>
To: "jimpop" <jim...@domainmail.org>
Disposition-Notification-To: <breyno...@cytranet.com>
Subject: Introduction - Voice & Data Services
Date: Fri, 18 Oct 2019 10:34:48 -0500
X-Bounce-Tracking-Info:
<amltcG9wCQkJamltcG9wQGRvbWFpbm1haWwub3JnCUludHJvZHVjdGlvbiAtIFZvaWNlICYgRGF0YSBTZXJ2aWNlcwkyNAkJMjM1NDYJYm91bmNlCW5vCW5v>
Content-type: text/plain; charset=iso-8859-1; format=flowed
Content-transfer-encoding: quoted-printable
X-Declude-Sender: breyno...@cytranet.com [192.168.5.250]
X-Declude-Spoolname: 39665034.eml
X-Declude-RefID:
X-Declude-Note: Scanned by Declude 4.12.11
X-Declude-Scan: Outgoing Score [0] at 10:34:54 on 18 Oct 2019
X-Declude-Tests: None
X-Country-Chain:
X-Declude-Code: 0
X-HELO: [192.168.5.250]
X-Identity: 192.168.5.250 | | domainmail.org
X-Exim-Id: 0E4LAdSNDpxw5zvVdBF5F7mnocgeAf3w24sEzYlpfeVC
X-Virus-Status: Clean
------------------------------
Message: 2
Date: Fri, 25 Oct 2019 10:20:34 -0500
From: Gary Leato <leato2...@gmail.com>
To: Stipo <vst...@gmail.com>
Cc: Stephane Bortzmeyer <bortzme...@nic.fr>,
outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Office 365 global outage
Message-ID:
<CAOx5p8X6=a=9vr8_iyf_8ykuokug4wkjt6zctg5y2xqfwmf...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
how many of you who experienced the connectivity issues are running on
cogent internet?
Cogent Customers are experiencing difficulty connecting to Microsoft
domains. Engineers are investigating the cause and working to resolve.
There is NO ETR, please reference Support MASTER CASE HD10871010
On Fri, Oct 25, 2019 at 10:16 AM Stipo via Outages <outa...@outages.org>
wrote:
> Short O365 outage, reports of Outlook not responding, from Denver, New
> Orleans, Atlanta, Miami. From: 7:00 to 7:30am PST, O365 Outage status
> confirms this. Unable to gather useful troubleshooting info, netflow for MS
> seems normal during and after outage.
>
> -Vinny
>
> On Fri, Oct 25, 2019 at 8:03 AM Stephane Bortzmeyer via Outages <
> outa...@outages.org> wrote:
>
>> On Fri, Oct 25, 2019 at 07:56:26AM -0700,
>> Mike Bolitho <mikeboli...@gmail.com> wrote
>> a message of 108 lines which said:
>>
>> > I mean just because you can hit office.com via ICMP doesn't mean there
>> > aren't issue.
>>
>> I certainly know that, like all the people on this list. But because
>> there was zero details in the original message (no description of
>> symptoms, no tests done), it is hard to know if we see the same thing
>> or not.
>> _______________________________________________
>> Outages mailing list
>> outa...@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20191025/c7005b9f/attachment-0001.htm>
------------------------------
Message: 3
Date: Tue, 10 Dec 2019 16:34:43 -0500
From: Ryan Chewning <r...@chewning.us>
To: Richard <rgolod...@infratection.com>, Matt Hoppes
<mattli...@rivervalleyinternet.net>
Cc: outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Fixing "Google Down?"
Message-ID:
<CAFEzzZDbuCeMT_X=t9lnbpoalp-neq5nfrvptwxxdc9sqng...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
To add onto what Richard is saying. when you include your region it's also
helpful to provide any information about your upstream carriers or if
you're multi-homed which carrier you're seeing the outage over.
On Tue, Dec 10, 2019 at 4:31 PM Richard via Outages <outa...@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
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20191210/0b872dd3/attachment-0001.htm>
------------------------------
Message: 4
Date: Tue, 10 Dec 2019 14:41:08 -0700
From: Mike Bolitho <mikeboli...@gmail.com>
To: Ryan Chewning <r...@chewning.us>
Cc: Richard <rgolod...@infratection.com>, Matt Hoppes
<mattli...@rivervalleyinternet.net>, outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Fixing "Google Down?"
Message-ID:
<caconlrwy8e0q5hoqbmthxqcqsukv2oala26sdt4mdn7xu-i...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Yep. A traceroute would have been very helpful.
- Mike Bolitho
On Tue, Dec 10, 2019 at 2:36 PM Ryan Chewning <r...@chewning.us> wrote:
> To add onto what Richard is saying. when you include your region it's also
> helpful to provide any information about your upstream carriers or if
> you're multi-homed which carrier you're seeing the outage over.
>
> On Tue, Dec 10, 2019 at 4:31 PM Richard via Outages <outa...@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
>> outa...@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20191210/4476787b/attachment-0001.htm>
------------------------------
Message: 5
Date: Tue, 10 Dec 2019 15:40:14 -0600
From: Chris Adams <c...@cmadams.net>
To: Ryan Chewning <r...@chewning.us>
Cc: Richard <rgolod...@infratection.com>, Matt Hoppes
<mattli...@rivervalleyinternet.net>, outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Fixing "Google Down?"
Message-ID: <20191210214014.ga5...@cmadams.net>
Content-Type: text/plain; charset=us-ascii
Once upon a time, Ryan Chewning <r...@chewning.us> said:
> To add onto what Richard is saying. when you include your region it's also
> helpful to provide any information about your upstream carriers or if
> you're multi-homed which carrier you're seeing the outage over.
Also include what IP(s) you're trying to reach (I've been guilty of
forgetting this). Like - I had issues getting to smtp.google.com
earlier, but it was just one IP. I got a different IP from a different
recursive server and it worked.
--
Chris Adams <c...@cmadams.net>
------------------------------
Message: 6
Date: Tue, 10 Dec 2019 16:43:24 -0500
From: Matt Hoppes <mattli...@rivervalleyinternet.net>
To: Mike Bolitho <mikeboli...@gmail.com>
Cc: Ryan Chewning <r...@chewning.us>, Richard
<rgolod...@infratection.com>, outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Fixing "Google Down?"
Message-ID:
<56a7aea1-77fa-499b-a384-c361ffc5d...@rivervalleyinternet.net>
Content-Type: text/plain; charset="us-ascii"
Subject: Instability - I2 Core Services AL2S / IP / PX
Services: IP PX AL2S
Affected: Core Services AL2S / IP / PX
Description: The Internet2 network is experiencing widespread outages
of unknown origin. This is causing frequent iBGP and LSP resets at
various points across the footprint. Network engineers are engaged
and actively investigating to isolate the source of the outage and
will provide an update as soon as the issue is better
understood. Internet2 is declaring a major incident and will share
updates on a regular cadence.
Looks like this may have been the source of what we saw.
Unfortunately until we got into full diagnostic swing, the pings to google.com
started flying again.
> On Dec 10, 2019, at 4:41 PM, Mike Bolitho <mikeboli...@gmail.com> wrote:
>
> Yep. A traceroute would have been very helpful.
>
> - Mike Bolitho
>
>
>> On Tue, Dec 10, 2019 at 2:36 PM Ryan Chewning <r...@chewning.us> wrote:
>> To add onto what Richard is saying. when you include your region it's also
>> helpful to provide any information about your upstream carriers or if you're
>> multi-homed which carrier you're seeing the outage over.
>>
>>> On Tue, Dec 10, 2019 at 4:31 PM Richard via Outages <outa...@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
>>> outa...@outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
>> _______________________________________________
>> Outages-discussion mailing list
>> Outages-discussion@outages.org
>> https://puck.nether.net/mailman/listinfo/outages-discussion
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20191210/3f447785/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 121, Issue 1
**************************************************
