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: Cogent disconnecting Russia (Jay Hennigan)
2. Re: Cogent disconnecting Russia (Charles Sprickman)
3. Re: [outages] .fj TLD down (Siyuan Miao)
4. Re: [outages] .fj TLD down (Stephane Bortzmeyer)
5. Re: [outages] Discord, Wikipedia, Spotify, AWS down - common
denominator? (Andy Ringsmuth)
----------------------------------------------------------------------
Message: 1
Date: Fri, 4 Mar 2022 16:09:26 -0800
From: Jay Hennigan <j...@west.net>
To: outages-discussion@outages.org
Subject: Re: [Outages-discussion] Cogent disconnecting Russia
Message-ID: <a4c4a6ab-e428-e80d-e6f2-211b1710b...@west.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 3/4/22 15:49, Bill Woodcock wrote:
>
>
>> On Mar 5, 2022, at 12:39 AM, Jay R. Ashworth <j...@baylink.com> wrote:
>> Let me take a moment to rule "What's a Tier 1" OFF-topic for this list, in
>> perpetuity.
>
> Allow me to provide the canonical answer, once and for all:
>
> Tier-1 is yourself.
> Tier-2 is your customer or your competitor.
> Tier-3 is your customer?s competitor or your competitor?s customer.
Nope. "We are a tier-1 provider" is code for "I am a salesperson".
--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV
------------------------------
Message: 2
Date: Fri, 4 Mar 2022 19:28:19 -0500
From: Charles Sprickman <sp...@bway.net>
To: Bill Woodcock <wo...@pch.net>
Cc: Outages Discussion <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] Cogent disconnecting Russia
Message-ID: <80cc6f1c-1311-454b-a9fa-10e41217e...@bway.net>
Content-Type: text/plain; charset="utf-8"
> On Mar 4, 2022, at 6:48 PM, Bill Woodcock <wo...@pch.net> wrote:
>
> Signed PGP part
> Rudolf just pointed out that someone at Cogent probably looked at the ruble
> exchange rate and realized that if they don?t cut Russian customers off now,
> they?re just going to have to do it at the end of the month, and then they?re
> going to have a loss on their books.
>
> https://twitter.com/internetthought/status/1499795346804858888?s=20&t=FDPYNLMo67tzlcn2pxcBVQ
>
> It?s always refreshing to me to be reminded that there?s someone who looks at
> telcos with even less rosy glasses than mine! :-)
I think he?s spot on?
And given some of their past reputation for hosting total garbage customers and
being not-so-responsive on the abuse front, the bit in the WaPo piece about
them ?wanting to not be a conduit for russian cyberattacks? gave me a real
chuckle.
Charles
>
> -Bill
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 528 bytes
Desc: Message signed with OpenPGP
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220304/cfb229ec/attachment-0001.sig>
------------------------------
Message: 3
Date: Tue, 8 Mar 2022 17:33:01 +0800
From: Siyuan Miao <siy...@misaka.io>
To: Jonathan S?lea <jonathan.se...@portsgroup.com>
Cc: outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] .fj TLD down
Message-ID:
<CAO3CAMoLA0fc=FFE6sJA6nEQ43-xX__jnjjDkD_=tjchq7e...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Looks fine here?
aveline@us-iad04-p01:~$ dig usp.ac.fj +trace
; <<>> DiG 9.11.5-P4-5.1+deb10u6-Debian <<>> usp.ac.fj +trace
;; global options: +cmd
. 518400 IN NS M.ROOT-SERVERS.NET.
. 518400 IN NS A.ROOT-SERVERS.NET.
. 518400 IN NS B.ROOT-SERVERS.NET.
. 518400 IN NS C.ROOT-SERVERS.NET.
. 518400 IN NS D.ROOT-SERVERS.NET.
. 518400 IN NS E.ROOT-SERVERS.NET.
. 518400 IN NS F.ROOT-SERVERS.NET.
. 518400 IN NS G.ROOT-SERVERS.NET.
. 518400 IN NS H.ROOT-SERVERS.NET.
. 518400 IN NS I.ROOT-SERVERS.NET.
. 518400 IN NS J.ROOT-SERVERS.NET.
. 518400 IN NS K.ROOT-SERVERS.NET.
. 518400 IN NS L.ROOT-SERVERS.NET.
;; Received 811 bytes from 172.26.0.2#53(172.26.0.2) in 0 ms
fj. 172800 IN NS ns1.fj.
fj. 172800 IN NS ns2.fj.
fj. 172800 IN NS ns3.fj.
fj. 172800 IN NS ns4.fj.
fj. 172800 IN NS ns5.fj.
fj. 86400 IN DS 18952 8 2
B22F5938AD822A76499A3AC295E061CC07FCE36D7956E26A4F51AEDE 1717F993
fj. 86400 IN RRSIG DS 8 1 86400 20220321050000 20220308040000 9799 .
GV9jHAYa1/THxNVXY8xfd9KpkgfWJH9etKm6d13p95DpDI/i8q8gDCYH
K3s7+QkQWmwnuhyIajYXbJGpwjpIZFJJdUlL6kJyApAbx8p+XvnMRE8I
iI7HwjE+SReu4iOVhuXysBEDGvdwHjENYes8g7S909FefLFCaBfZ8WVW
VBWOOQNYueERcBFn6kAUSM8Es5xzt7B0UnivO+dWX6NSXxzVPxTW8hTs
WXoyLle6Qkxti2+4zQJS/UlQYYeSUZbj/bGTlV/j8z7GdoFngXNwyZXr
GxmdqxSvzFUh9/38Idn0xC1HAvFW4jhDCS1WV9NPiBs0Wx/VG8yMM0KG Xbi+Fg==
;; Received 599 bytes from 2001:500:1::53#53(H.ROOT-SERVERS.NET) in 3 ms
usp.ac.fj. 86400 IN NS ns1.usp.ac.fj.
usp.ac.fj. 86400 IN NS ns2.usp.ac.fj.
61bq6ngv0tbeoktd23ep0igj77v6hej8.fj. 3600 IN NSEC3 1 0 5 F0EA3EA23B519104
61C5S482Q3BBK77BO9ITSFN2GQQ069KD NS
61bq6ngv0tbeoktd23ep0igj77v6hej8.fj. 3600 IN RRSIG NSEC3 8 2 3600
20220316160628 20220302225344 24459 fj.
0nAzeSUc71cT1kbHeZ+aVEg8CHmHaD/FrnhJ0q0G859Blg56hHaNBTai
1EmYNVo7bpOS0fpoGetk4vo5sYfz1yzQAJh3fSFS/VDaZyxg1/DgjWFz
4qLHIpg+zPbDYiXmLMF3S10VQZZYcyc4mSpSQPxP4CBaP126RVnd8t8d
gdc5MbmH4Swv1LoSkD9s0RjfMZYA5KLAWeA7DWGlCo5wBx6l6CNpA4U5
OGBtzGg5TZipbA6He1Vv50sjA5073A85TsBorglsZBzjQIsidTPdx/Fc
XXWXIxujx22EeX2hUy22BSKCkYQhZECOcG4L4s9KBAp+TAaJIsZJ21lw NlUtsg==
;; Received 478 bytes from 185.38.108.108#53(ns3.fj) in 846 ms
usp.ac.fj. 86400 IN A 144.120.141.80
usp.ac.fj. 86400 IN NS ns2.usp.ac.fj.
usp.ac.fj. 86400 IN NS ns1.usp.ac.fj.
;; Received 206 bytes from 144.120.146.2#53(ns1.usp.ac.fj) in 253 ms
On Tue, Mar 8, 2022 at 5:30 PM Jonathan S?lea via Outages <
outa...@outages.org> wrote:
> It seems like that the .fj TLD is completely down.
>
> The .fj zone seems empty.
>
>
>
> Anyone have any interesting insight on why?
>
>
>
> / J
>
>
> _______________________________________________
> 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/20220308/30b41ddc/attachment-0001.htm>
------------------------------
Message: 4
Date: Tue, 8 Mar 2022 10:48:09 +0100
From: Stephane Bortzmeyer <bortzme...@nic.fr>
To: Siyuan Miao <siy...@misaka.io>
Cc: Jonathan S?lea <jonathan.se...@portsgroup.com>,
outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] .fj TLD down
Message-ID: <yicmwttcm8sku...@nic.fr>
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 08, 2022 at 05:33:01PM +0800,
Siyuan Miao <siy...@misaka.io> wrote
a message of 178 lines which said:
> Looks fine here?
May be because you use a non-validating resolver?
------------------------------
Message: 5
Date: Tue, 8 Mar 2022 13:29:07 -0600
From: Andy Ringsmuth <a...@andyring.com>
To: Outages Discussion <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] Discord, Wikipedia,
Spotify, AWS down - common denominator?
Message-ID: <e6af9c74-5827-4f54-bb19-07f9deecf...@andyring.com>
Content-Type: text/plain; charset=us-ascii
Discord actually does have a Status page:
https://discordstatus.com
And currently says:
Update - Oncall Engineering continues to investigate the root cause of this
issue. We have engaged our partners and are preparing contingencies to restore
service.
Mar 8, 10:59 PST
Update - We are continuing to investigate the issue impacting the API to find
root cause.
Mar 8, 10:29 PST
Investigating - While monitoring this issue a new issue has occurred causing an
major outage of the API. Oncall Engineering is working to correct this
situation.
Mar 8, 10:12 PST
Update - As part of recovery, the root cause was also detected in our streaming
service. A controlled restart was performed of this service which would have
caused a temporary disruption of streaming, this should be operating correctly
at this time.
Mar 8, 10:08 PST
Monitoring - Remediations appear to have restored service to normal operation,
Oncall Engineering will monitor for full recovery
Mar 8, 09:54 PST
Identified - The root cause has been determined, remediations have been
executed to restore service.
Mar 8, 09:53 PST
Investigating - We are currently investigating an increase in API Errors and
Push Notification Errors.
Mar 8, 09:16 PST
----
Andy Ringsmuth
5609 Harding Drive
Lincoln, NE 68521-5831
(402) 304-0083
a...@andyring.com
> On Mar 8, 2022, at 12:54 PM, Phineas Walton via Outages <outa...@outages.org>
> wrote:
>
> A lot of services seem to be having issues - I know Discord and
> Spotify use GCP but the rest don't (to my knowledge). I wonder what
> the common denominator to these widespread outages is.
>
> Services with reported issues:
> - Discord (completely down)
> - Spotify (completely down)
> - Wikipedia (completely down)
> - AWS
> - Twitter
> - GCP
> - Youtube
> - Facebook / Instagram
> - Cloudflare
> - Twitch
>
> https://downdetector.com
>
> Phin
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
------------------------------
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 145, Issue 12
***************************************************
