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] Trouble in Chicago (Jay R. Ashworth)
2. Re: [outages] NetSol issues via Cloudflare in Toronto
(ns61.worldnic.com) ? (Frank Bulk)
3. windstream ? ? (Bryan Holloway)
4. Re: [outages] Massive DNS Trouble today 2021-04-01 17:25 EDT
(Andy Ringsmuth)
5. Re: [outages] Facebook, Instagram down (Frank Bulk)
----------------------------------------------------------------------
Message: 1
Date: Fri, 12 Mar 2021 03:12:23 +0000 (UTC)
From: "Jay R. Ashworth" <j...@baylink.com>
To: Ross Tajvar <r...@tajvar.io>
Cc: "Hiers, David" <david.hi...@cdk.com>, outages-discussion
<outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] Trouble in Chicago
Message-ID: <1592117699.269.1615518743519.javamail.zim...@baylink.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Ross Tajvar" <r...@tajvar.io>
> Hi David,
>
> I'm sending this to -discussion since it's not directly related to the issue.
>
> Maybe I'm off-base here, but I don't see how an email like this really helps
> anyone. At a minimum I would want to know what carrier(s) you are having an
> issue with and when the issue started. An email this vague doesn't provide me
> any actionable info, or even really give me an idea of what I might need to
> check. If you said "my Telia transit out of 350 E Cermak started experiencing
> loss at 11:01 AM" or something like that, I would know to check my Telia
> service in that building. But with no info, I can't do anything with this.
> Even
> if I did notice a problem in Chicago, I have no way of knowing if it's the
> same
> problem you had.
>
> I hope this doesn't come across too critical - I just want to make the Outages
> list more useful for everyone.
Ross is correct; we really do like to see more detail in -- especially --
initial reports to the list.
Cheers,
-- jr '</moderator>' a
--
Jay R. Ashworth Baylink j...@baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
------------------------------
Message: 2
Date: Wed, 17 Mar 2021 10:56:11 -0500
From: "Frank Bulk" <frnk...@iname.com>
To: <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] NetSol issues via
Cloudflare in Toronto (ns61.worldnic.com) ?
Message-ID: <000001d71b46$0d7856d0$28690470$@iname.com>
Content-Type: text/plain; charset="utf-8"
Yes, here's a tweet about it:
https://twitter.com/netsolcares/status/1372180247207153665
Frank
-----Original Message-----
From: Outages <outages-boun...@outages.org> On Behalf Of mike tancsa via Outages
Sent: Wednesday, March 17, 2021 9:48 AM
To: Jay Ashworth via Outages <outa...@outages.org>
Subject: [outages] NetSol issues via Cloudflare in Toronto (ns61.worldnic.com) ?
I noticed a couple of domains that have netsol as authoritative timing
out, specifically ns61.worldnic.COM resolving to 207.204.40.131 which I
pick it up via Cloudflare in Toronto Canada via our Torix peer
% traceroute -I -q1 -n 207.204.40.131
traceroute to 207.204.40.131 (207.204.40.131), 64 hops max, 48 byte packets
1 199.212.134.10 0.139 ms
2 205.211.165.118 4.263 ms
3 206.108.34.208 31.456 ms
4 108.162.240.24 4.331 ms
5 108.162.240.14 4.404 ms
6 *
e.g
% time host -tns washconnect.com
washconnect.com name server ns62.worldnic.com.
washconnect.com name server ns61.worldnic.com.
% time host host1.washconnect.com ns62.worldnic.com.
Using domain server:
Name: ns62.worldnic.com.
Address: 207.204.21.131#53
Aliases:
host1.washconnect.com has address 204.186.31.41
0.000u 0.002s 0:00.10 0.0% 0+0k 3+0io 0pf+0w
% time host host1.washconnect.com ns61.worldnic.com.
;; connection timed out; no servers could be reached
0.000u 0.002s 0:10.05 0.0% 0+0k 3+0io 0pf+0w
I am having problems with their whois server as well
% time whois -h whois.networksolutions.com washconnect.com
whois: connect(): Operation timed out
0.000u 0.001s 1:15.18 0.0% 0+0k 1+0io 0pf+0w
route-views.routeviews.org doesnt see their prefix either :(
route-views>sh ip bgp 64.69.216.61
BGP routing table entry for 0.0.0.0/0, version 33108733
Paths: (1 available, best #1, table default, RIB-failure(17))
Not advertised to any peer
Refresh Epoch 1
53767 3257
162.251.163.2 from 162.251.163.2 (162.251.162.3)
Origin IGP, localpref 100, valid, external, best
Community: 53767:5000
path 7FE0F6ED4BE8 RPKI State not found
rx pathid: 0, tx pathid: 0x0
route-views>
% host whois.networksolutions.com
whois.networksolutions.com has address 64.69.216.61
whois.networksolutions.com has IPv6 address 2607:f408:1010:a:64:69:216:61
% whois -h 2607:f408:1010:a:64:69:216:61 washconnect.com
whois: connect(): Operation timed out
_______________________________________________
Outages mailing list
outa...@outages.org
https://puck.nether.net/mailman/listinfo/outages
------------------------------
Message: 3
Date: Wed, 17 Mar 2021 21:31:31 +0100
From: Bryan Holloway <br...@shout.net>
To: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: [Outages-discussion] windstream ? ?
Message-ID: <8b5b1978-5385-5050-1573-7a24e31ee...@shout.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Supposedly had emergency maintenance in the Chicago area last night,
gave our downstreams 5 hours notice ... fine ... I understand ... these
things sometimes happen.
Now I have a 100G circuit down. Been trying to reach out to their NOC
several times now, and I keep getting disconnected.
I don't have evidence to point to a systemic issue, but I'm curious if
anyone is having similar issues.
------------------------------
Message: 4
Date: Thu, 1 Apr 2021 18:09:10 -0500
From: Andy Ringsmuth <a...@andyring.com>
To: Outages Discussion <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] Massive DNS Trouble today
2021-04-01 17:25 EDT
Message-ID: <0b523eba-fa10-4c41-9508-9bb87e20f...@andyring.com>
Content-Type: text/plain; charset=utf-8
DNS again?
It?s always DNS?
Sheesh. Microsoft, WTF? Get it together.
----
Andy Ringsmuth
5609 Harding Drive
Lincoln, NE 68521-5831
(402) 304-0083
a...@andyring.com
?Better even die free, than to live slaves.? - Frederick Douglas, 1863
> On Apr 1, 2021, at 5:06 PM, Jeffrey Ollie via Outages <outa...@outages.org>
> wrote:
>
> Can confirm that all of our Azure DNS was offline for a few minutes. Seems to
> be coming back now.
>
> Jeff
>
>
> On Thu, Apr 1, 2021 at 4:59 PM Cary Wiedemann via Outages
> <outa...@outages.org> wrote:
> Details scant so far, but there's something awful going on with DNS for a
> large portion of the Internet, especially Azure.
>
> Microsoft just posted this to Twitter via @MSFT365Status:
> <image.png>
> https://twitter.com/MSFT365Status/status/1377738432265396225
>
> But I have vendors using UltraDNS (for example) that are also failing to
> resolve, and those servers aren't hosted in Azure.
>
> Investigating now. Early warning. Further reports would be appreciated.
>
> Thanks all!
>
> - Cary
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
> --
> Jeff Ollie
> The majestik m??se is one of the m?ni interesting furry animals in Sweden.
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
------------------------------
Message: 5
Date: Thu, 8 Apr 2021 20:16:16 -0500
From: "Frank Bulk" <frnk...@iname.com>
To: <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] Facebook, Instagram down
Message-ID: <000001d72cdd$f0ced3c0$d26c7b40$@iname.com>
Content-Type: text/plain; charset="utf-8"
Our monitoring system?s checks of HTTPv6 failed twice between 4:39 and 5:03 pm
(U.S. Central)
Frank
From: Outages <outages-boun...@outages.org> On Behalf Of Bart Boryczko via
Outages
Sent: Thursday, April 8, 2021 6:48 PM
Cc: outa...@outages.org
Subject: Re: [outages] Facebook, Instagram down
Looks like it may be resolved, at least for Facebook:
On Thu, Apr 8, 2021 at 2:52 PM Gareth Tupper via Outages <outa...@outages.org
<mailto:outa...@outages.org> > wrote:
Per subject ? widespread North American reports of facebook & Instagram being
down. No cause atm.
This electronic mail transmission contains information from Warner Pacific
Insurance Services that may be confidential or privileged. Such information is
solely for the intended recipient, and use by any other party is not
authorized. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of this message, its contents or any
attachments is prohibited. Any wrongful interception of this message is
punishable as a Federal Crime. If you have received this message in error,
please notify the sender immediately by telephone (800) 801-2300 or by
electronic mail at postmas...@warnerpacific.com
<mailto:postmas...@warnerpacific.com> .
[PHI] - Please note that this email is being sent securely as it may contain
attachments or content that include PHI (Protected Health Information), PII
(Personally Identifiable Information) or other sensitive information.
_______________________________________________
Outages mailing list
outa...@outages.org <mailto: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/20210408/b334e04a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 37717 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20210408/b334e04a/attachment.png>
------------------------------
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 134, Issue 1
**************************************************
