Re: Beta Starlink with a slight tree obstruction vs degraded DOCSIS3 last mile

[Josh Luthman <josh () imaginenetworksllc com>]

Have you thought about doing a TCP test?  Maybe an HTTP check to a
website?  That would be better than ICMP, I think, since it would be more
user like.

Josh Luthman
24/7 Help Desk: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373


On Tue, Jun 29, 2021 at 9:02 PM Eric Kuhnke <eric.kuhnke () gmail com> wrote:

> The local cable last mile operator broke something locally, or something
> degraded (water ingress, bad connectors, who knows) and can't get their act
> together sufficiently to dispatch a field tech and fix it.
>
> On Mon, Jun 28, 2021, 11:03 AM Josh Luthman <josh () imaginenetworksllc com>
> wrote:
>
> > What happened on June 20/21?  Looks like someone broke something on your
> > cable link or perhaps an ICMP rate limiting was introduced.
> >
> > Josh Luthman
> > 24/7 Help Desk: 937-552-2340
> > Direct: 937-552-2343
> > 1100 Wayne St
> > Suite 1337
> > Troy, OH 45373
> >
> >
> > On Mon, Jun 28, 2021 at 10:45 AM Matt Hoppes <
> > mattlists () rivervalleyinternet net> wrote:
> >
> > > I don't know how you can be embarrassed when you have a pretty solid
> > > 30ms ping constantly, and Starlink has jitter all over the place and
> > > spikes as high as 280ms.
> > >
> > > I'll take the DOCSIS3 system....
> > >
> > > On 6/25/21 8:49 PM, Eric Kuhnke wrote:
> > > > I thought I would post an interesting comparison between a degraded
> > > > DOCSIS3 link, of a carrier that shall remain nameless to avoid
> > > > embarrassing anybody, and a starlink CPE with a slight 1/12th tree
> > > > obstruction in a portion of its view.
> > > >
> > > > First two screenshots are the docsis3, to its gateway and to a very
> > > > reliable hosted asterisk system in Seattle.
> > > >
> > > > Second two screenshots are starlink, also to its gateway and to the
> > > same
> > > > destination.
> > > >
> > > > https://imgur.com/a/OQ5wyDr