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: [EXTERNAL] Re: Mediacom intermittent packet loss
      (Matthew Petach)
   2. SLACK Outage (Jay R. Ashworth)
   3. Re: [outages] rt.com (outages)
   4. Re: [outages] rt.com (Bill Woodcock)
   5. Re: [outages] [Preemptive Strike] Ukraine requests Internet
      Death Penalty for Russia (Paul M - outages)


----------------------------------------------------------------------

Message: 1
Date: Mon, 21 Feb 2022 11:27:53 -0800
From: Matthew Petach <m...@petach.org>
To: "Chapman, Brad (NBCUniversal)" <brad.chap...@nbcuni.com>
Cc: Scott Buettner <dasterintem...@outlook.com>,
        outages-discussion@outages.org
Subject: Re: [Outages-discussion] [EXTERNAL] Re: Mediacom intermittent
        packet loss
Message-ID:
        <CAEmG1=osu=-zPeu+zfwRLr+A2Cmd9gR7UyvHNYn8R-=zm81...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

The 12 seconds of jitter and 98% of the packets being tagged as "late
packets" really, really points to a pretty bad buffer bloat problem.

If other customers are seeing similar problems, it could be a cascading
series of large buffer devices along a pathway with an intermittently
congested series of upstream links beyond them, so what you're seeing isn't
just packets being stuck in a single large buffer, but a procession of
large buffers, each of which adds delay and loss.

Definitely not a good customer experience, that's for sure.  ^_^;

Matt


On Sat, Feb 19, 2022, 20:34 Chapman, Brad (NBCUniversal) <
brad.chap...@nbcuni.com> wrote:

> devicetests.com is interesting.  However, the latency / packet loss test
> is only capable of blasting a max of 450 KB/s (3.6Mbps) even when cranked
> to its maximum silliness... but his sample shows a *steadily increasing*
> ping time over the length of the test.  That's strange.
>
> It could be an oversubscribed line, or the original repair wasn't done
> right (or has failed again), or he just doesn't have sufficient bandwidth
> to stream at all.
>
> 1. What is his chosen streaming platform?
>
> 2. What is the resolution, frame rate, bitrate etc?
>
> 3. What is his *contracted* upload rate from Mediacom ("up to ____ Mbps
> upload")?
>
> 4. Has he run a 24-hour twitch stream to track the latency around the
> clock?  Maybe there's a pattern.
>
>
> ?Sent from my iPhone
>
> On Feb 19, 2022, at 7:46 PM, Chad Austin <m...@chadaustin.org> wrote:
>
> ?22 seconds of latency?
>
> Do you have gigabytes of buffers, or is something sending pause frames?
>
> +1 to 'did you plug your PC into the modem directly?'
>
> -Chad
>
> On 2/19/2022 9:57 PM, Scott Buettner wrote:
>
> The cable carrier has done the standard "have him powercycle then send a
> tech out" and the techs have not found a problem in this most recent issue.
> (He had a similar problem in December that WAS line related and was
> resolved in early Jan by the carrier techs). Unfortunately he's on
> residential class service at the moment (which I am trying to persuade him
> to correct) so the level of support we're getting from the Tier 1 folks
> isn't ideal.
>
> He's scheduling another tech dispatch with them now, just to be safe.
>
>
> It's hitting TCP and UDP both, which is just manifesting in "slowness" on
> TCP of course. It's most relevant over UDP as he is a professional streamer
> and the most prominent symptom is frame drops on that, and I've confirmed
> it is affecting his connection in general, the issue is not specific to
> that service. I had him grab a packet loss test using devicetests.com
> (which looks to be based on WebRTC for the test) and we managed to grab
> results of it actively happening here:
> https://urldefense.com/v3/__https://dast-files.s3.us-east-2.amazonaws.com/packets.jpg__;!!PIZeeW5wscynRQ!78RScPexz65Gc0_sIwuwdK43Y9sa-rcED6XtN-khol5rNm3Sl80znvDY-x1vXl_u4w$
>
> He's replaced the modem and router both in the last 3 months, along with
> the cables.
>
> It's very intermittent, bursts of packet loss over a few minutes, then
> fine for some period of time (minutes to hours).
>
>
> He's informed me that a colleague of his located about 4 hours away on the
> same ISP is experiencing similar issues, but that individual is not a
> client of mine so I don't have anything concrete from that endpoint
> currently.
>
>
> I'm happy to keep discussing/troubleshooting, but I would like to avoid
> spamming the rest of the list (even -discuss), so feel free to email me
> directly.
>
>
> -----Original Message-----
>
> From: Jay R. Ashworth <j...@baylink.com>
>
> Sent: Saturday, February 19, 2022 7:18 PM
>
> To: Scott Buettner <dasterintem...@outlook.com>
>
> Cc: outages-discussion@outages.org
>
> Subject: Re: [Outages-discussion] Mediacom intermittent packet loss
>
>
> ----- Original Message -----
>
> From: "Scott Buettner" <dasterintem...@outlook.com>
>
> I hate to ask since this isn't really the forum, but I'm sort of out of
> ideas:
>
> Would anyone from MediacomCable be able to reach out to me offlist?
>
> I'm not gonna call it an outage, but I have a client on their service
>
> who is having crippling intermittent upload packet loss (~85%) for
>
> most of this month, calls from him to phone support have not resulted
>
> in a resolution and it's seriously affecting his home business.
>
>
> Thanks in advance if anyone can assist, and sorry to bother everyone
> otherwise.
>
> --Samantha
>
> The cable carrier has confirmed there's not a low-signal problem on the
> link, and other first-level stuff like that?  Do they have their own
> router, have they plugged directly into the cablemodem for test (after a
> powercycle)?
>
>
> What protocol isn't working, does other stuff not work too?
>
>
> You're right, this is usually out-of-scope for Outages, but at least you
> posted it on -discuss.  :-)
>
>
> Cheers,
>
> -- jra
>
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
>
> https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!78RScPexz65Gc0_sIwuwdK43Y9sa-rcED6XtN-khol5rNm3Sl80znvDY-x10eDxyeQ$
>
> _______________________________________________
> 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/20220221/d2ca3dfb/attachment-0001.htm>

------------------------------

Message: 2
Date: Tue, 22 Feb 2022 17:53:01 +0000 (UTC)
From: "Jay R. Ashworth" <j...@baylink.com>
To: Outages <outa...@outages.org>
Cc: OUTAGES Discussion List <outages-discussion@outages.org>
Subject: [Outages-discussion] SLACK Outage
Message-ID: <25089303.5397.1645552381976.javamail.zim...@baylink.com>
Content-Type: text/plain; charset=utf-8

Confirmed in many places, and also here; please move further discussion
and reports to the -discuss list.

Cheers,
- jr '<admin/>' a

----- Original Message -----
> From: "Paul Ferguson via Outages" <outa...@outages.org>
> To: "Outages ML" <outa...@outages.org>
> Sent: Tuesday, February 22, 2022 9:49:27 AM
> Subject: [outages] Slack?

> Apparently there's a Slack outage, any details or RFO?
> 
> Downdetector also suggest AWS and github, as well...
> 
> Cheers,
> 
> - ferg
> 
> --
> Paul Ferguson
> Tacoma, WA  USA
> Illegitimi non carborundum.
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages

-- 
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: 3
Date: Wed, 2 Mar 2022 07:46:17 -0800
From: outages <virendra.r...@outages.org>
To: Bill Woodcock <wo...@pch.net>
Cc: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] rt.com
Message-ID: <b059d85d-1791-4d92-b5de-63c45a67d...@outages.org>
Content-Type: text/plain; charset=utf-8

I believe this is related to an aggressive DDOS attack by the ?IT army?.

?
regards,
/vrode

> On Mar 2, 2022, at 01:50, Bill Woodcock via Outages <outa...@outages.org> 
> wrote:
> 
> ?I?m curious about the blocking status of RT.com, the Russian state media 
> organ.
> 
> Using my own connection, I can reach it without difficulty.
> 
> It?s sitting behind DDoS-Guard, a (now) Russian bulletproof hoster which was, 
> ironically, a Ukrainian company: https://en.wikipedia.org/wiki/DDoS-Guard
> 
> But many of the common ?is it reachable? sites show it completely down:
> 
> https://semonto.com/tools/website-reachability-check.html?test=2a4bc50397731140d76f168f3ff457949f4
> 
> https://www.uptrends.com/tools/uptime?toolRequestGuid=3c1bd632-7ec7-4420-823d-199fadcb315d
> 
> Does anyone have any insight into what mechanisms are being used to block RT?
> 
>                                -Bill
> 
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages


------------------------------

Message: 4
Date: Wed, 2 Mar 2022 16:51:23 +0100
From: Bill Woodcock <wo...@pch.net>
To: outages <virendra.r...@outages.org>
Cc: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] rt.com
Message-ID: <c5873638-2eea-4737-81dc-3a60ae35f...@pch.net>
Content-Type: text/plain; charset="utf-8"



> On Mar 2, 2022, at 4:46 PM, outages <virendra.r...@outages.org> wrote:
> 
> I believe this is related to an aggressive DDOS attack by the ?IT army?.

The other explanation I?ve been getting from people is that the Russians are 
aggressively IP-geo-blocking from their side, to damp down DDoS, which makes 
them unavailable to most probes, but they don?t block PCH because they want 
access to our servers.

                                -Bill

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: 
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220302/791348f6/attachment-0001.sig>

------------------------------

Message: 5
Date: Wed, 2 Mar 2022 17:32:06 +0000
From: Paul M - outages <paul+outa...@mansfield.co.uk>
To: outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] [Preemptive Strike]
        Ukraine requests Internet Death Penalty for Russia
Message-ID:
        <cagwpyocm0jr9gwohvgrrvtqbfpbl5raut-zhtql2pnvk7h8...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Wed, 2 Mar 2022 at 17:04, Jay R. Ashworth via Outages
<outa...@outages.org> wrote:
> https://www.zdnet.com/article/ukraine-asks-for-russia-to-be-kicked-off-the-internet

there's good reason to believe that many Russians rely on the internet
to find out what's going on in the world, as all state media is
controlled. Just as in the west, younger people rely more on the
internet for information, and older people use the TV.

If they are blocked from the internet, the people will only receive
state propaganda, and will know nothing of the war against the Ukraine
etc. IMNSHO, the best way to prevent tyrants is to have educated citizens.

Therefore I would urge people to push back against an internet death
sentence against .RU


------------------------------

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 1
**************************************************

Reply via email to