Comcast's Outage id number OE118864040
On Wed, Feb 24, 2021 at 11:42 PM Jason Kuehl
wrote:
> From Comcast's own charts. Looks like something did happen over their
> ethernet internet and private ethernet.
>
> [image: image.png]
>
> On Wed, Feb 24, 2021 at 11:37 PM Neil Hanlon wrote:
>
>> Yeah
>From Comcast's own charts. Looks like something did happen over their
ethernet internet and private ethernet.
[image: image.png]
On Wed, Feb 24, 2021 at 11:37 PM Neil Hanlon wrote:
> Yeah, had several test nodes transiting to me fail via Comcast it seems.
>
> On Wed, Feb 24, 2021, 23:31 Jason
Yeah, had several test nodes transiting to me fail via Comcast it seems.
On Wed, Feb 24, 2021, 23:31 Jason Kuehl wrote:
> Anyone else with Comcast have a small outage? About 5-7 minutes?
>
> --
> Sincerely,
>
> Jason W Kuehl
> Cell 920-419-8983
> jason.w.ku...@gmail.com
>
Anyone else with Comcast have a small outage? About 5-7 minutes?
--
Sincerely,
Jason W Kuehl
Cell 920-419-8983
jason.w.ku...@gmail.com
On Wed, 24 Feb 2021 at 09:00, Lars Prehn wrote:
> Does anybody have (somewhat frequent, e.g., monthly) snapshots of the
> various IRR databases lying around? Any snapshot since 2010 would be
> helpful!
For any specific use-case whowas cannot solve? ¯(°_o)/¯
--
Chriztoffer
FCC is proposing a change to who can have access to FCC outage reports.
But first a little history
After the 1990 AT&T Long Distance switching network collapse, there were
lots of investigations. The January 15th outage was the biggest, there
were a few more smaller crashes in 1990 and 19
Well then use one of the encapsulating IPv4AAS mechanisms rather than 464XLAT
(DS-Lite, MAP-E). They don’t involve translating the payload between IPv4 and
IPv6. That said what you are reporting below are implementation bugs. Did you
report them to the vendor? Did you install the fix? Rewrit
In response to the recently passed READI Act, the Federal Communications
Commission agenda for its March meeting includes the following notice of
inquiry:
https://www.fcc.gov/document/fcc-announces-tentative-agenda-march-open-meeting-8
The NDAA21 directs the Commission, within 180 days, to
I think I need to calm this thread down.
I'm a researcher, and my interest is in the truth, not in my opinion.
I've read some facts in this thread that are necessary
as a prerequisite to the publication of the results on Friday.
I do want to ensure that no future reader is misinformed and will d
The conference may be over, but the hours of archived talks, keynotes, and
panel discussions are just waiting to be explored! We've gathered up all
the very best, just for you. Scroll on to learn more!
Details for NANOG 82 — June 14-16, 2021 — are forthcoming. Stay tuned for
more information!
Vie
To the nanog community, I’m sorry to have dragged this conversation out
further. I'm only responding to this because there are a significant number of
open source projects and commercial products that use DPDK, or similar
userspace network environment in their implementations. The statements i
anyone else have the privilege of running 2321 data cells? had a bunch.
unreliable as hell. there was a job running continuously recovering
transactions off of log tapes. one night at 3am, head of apps program
(i was systems) got a call that a tran tape was unmounted with a console
message that
>
> Is this pain you have lived or verified with first hand testing?
>
>>
>> Yep! A lot!
LOL gamers can be pretty much insistent...
(haha.jpg + haha-crying.jpg)
And Specifically on SIP/Voip over the Internet, with deep analysis at all
the parts involved.
The most common issue is incoming Calls t
Hi Douglas,
I’ve done a lot of testing in several countries and customer networks and I’ve
never got a single failure because 464XLAT.
If anything failed, we tested it with a pure IPv4 network and dual-stack
network. They failed as well.
For example, I recall, in a customer deployment
On Wed, Feb 24, 2021 at 5:29 AM Douglas Fischer
wrote:
> P.S.: Forking thread from CGNAT.
>
> Hello Jordi!
>
> Since our last heated talk about transitions methods(Rosario, 2018?), I
> must recognize that the intolerance to other scenarios other than
> dual-stack had reduced(mostly because of imp
I'm not sure if it Covers IRR.
But considering IRR is an extension of Whois...
Arin keeps the service of "whowas"
https://www.arin.net/reference/research/whowas/
I suggest you take a look there.
And also, some IRRs keeps an archive folder on the FTP.
ftp://ftp.radb.net/radb/dbase/archive/
ftp://
P.S.: Forking thread from CGNAT.
Hello Jordi!
Since our last heated talk about transitions methods(Rosario, 2018?), I
must recognize that the intolerance to other scenarios other than
dual-stack had reduced(mostly because of improvements on the applications
in generral). I'm even considering the
I personally did "disable vlan Xyz" instead of "delete vlan Xyz" on
Extreme Network... which proceeded to disable all the ports where the
VLAN was present...
Good thing it was a (local) remote pop and not on the core.
-
Alain Hebertaheb...@pubnix.net
The statement used on the survey "Are you aware that use of DPDK on a
processor core keeps utilization at 100% regardless of packet activity?"
can be easily distorted and badly used.
I sincerely do not agree with the approach of presuming and declaring "DPDK
spent too much power".
Mainly because
Does anybody have (somewhat frequent, e.g., monthly) snapshots of the
various IRR databases lying around? Any snapshot since 2010 would be
helpful!
Best regards,
Lars
20 matches
Mail list logo
