There's 69,055 pure /24's allocated or assigned directly from an RIRs. At least
c,d,e, and g root servers only have /24s allocated to them. Major services like
Cloudflare only advertise the /24 without advertising an aggregate.
Unless you're also getting a default from upstream, it sounds like
Oddly enough I *do* see this via Verizon-but-XO:
182.61.200.0/22*[BGP/170] 3d 09:25:39, MED 100, localpref 100
AS path: 2828 4134 23724 38365 I, validation-state:
unverified
On Wed, Jul 20, 2022, at 3:18 PM, holow29 wrote:
>
> To follow up on this:
> I've engaged Veri
The fact that it even has to come to this idea is ridiculous but I wonder about
the success of holding a normal customer account with repeat offending
streaming services so you could report this, by proxy, /as/ a customer.
On Fri, Apr 29, 2022, at 8:38 AM, Josh Luthman wrote:
> >Disney+ appear
You're correct.
This the lab setup and rstp was set to the default, so I only got the commit
check to pass only when I deleted [protocols rstp].
On Fri, Feb 11, 2022, at 8:09 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> Nick Suan via NANOG writes:
>> I was actually interested
I was actually interested to see if the EX series would let me do this, and it
turns out that if STP is enabled on any of the switch interfaces, it won't:
tevruden@core-02# delete interfaces
{master:0}[edit]
tevruden@core-02# commit check
[edit protocols rstp]
'interface'
XSTP : Interf
While I agree that, yes everything SHOULD support TLS, there's a perfectly good
reason for terminating TLS in something like (nginx/caddy/apache/etc): X
number of things supporting TLS on their web interface means X number of ways
of configuring TLS. If I terminate it on nginx, there's only a
I've noticed something similar on two networks, however it appears to be trying
to scan port 80:
13:30:26.387183 IP6 2620:96:a000::5. > 2620:135:5005:71::b0c.80: Flags [S],
seq 2063829402, win 65535, length 0
13:30:26.393445 IP6 2620:96:a000::5. > 2620:135:5006:7::703.80: Flags [S],
seq
The portal account isn't even the be all and end all of fixing this, we're
telling google where our endpoints are explicitly with a geofeed, The portal
says the clients are in the right location and for some reason it's still
decided some of our IPs are on the other side of the world.
On Sat,
Not sure about Telia specifically, but there is apparently a fiber cut between
Dallas and Waxahachie, that took out our wave service to Austin.
Nick
On Wed, May 27, 2020, at 12:41 PM, Aaron Gould wrote:
> In the Texas area, particularly, south central, Austin area….. anyone know of
> any issues
From everywhere I've tried, it connects but loads slowly.
On Jul 21, 2010, at 8:44 AM, Jason Lewis wrote:
> This says it's not just down for me.
> http://downforeveryoneorjustme.com/pch.net
>
> Anyone else?
>
10 matches
Mail list logo
