Yup, Call of Duty update, 68GB on xbox platform.
Tom
On Tue, Feb 11, 2020 at 10:26 PM Aaron Gould wrote:
> Huge! Big as ever. My aanp links are (were) pegged, seriously. I will
> be contacting Akamai about lighting up an additional 10 gig link to my
> local clusters. Started at 12 noon
Huge! Big as ever. My aanp links are (were) pegged, seriously. I will be
contacting Akamai about lighting up an additional 10 gig link to my local
clusters. Started at 12 noon central… still going pretty heavily. Game/update
release ?
-Aaron
From: Tom Deligiannis
> Any word on what the update was for? It caused quite a jump in traffic on our
> network.
On twitter "68 GB" was trending
https://twitter.com/search?q=%2268%20GB%22=trend_click
Kind regards,
Job
Dido
On Feb 11, 2020, at 9:03 PM, Andy Smith
mailto:telephonetoughgu...@gmail.com>> wrote:
Any word on what the update was for? It caused quite a jump in traffic on our
network.
On Tue, Feb 11, 2020, 19:06 Jared Mauch
mailto:ja...@puck.nether.net>> wrote:
Looking good from my perspective.
Any word on what the update was for? It caused quite a jump in traffic on
our network.
On Tue, Feb 11, 2020, 19:06 Jared Mauch wrote:
> Looking good from my perspective. Let me know if we are causing you pain
> and let's see what can be done to improve.
>
> I'm here in SF if you are at nanog.
>
Looking good from my perspective. Let me know if we are causing you pain and
let's see what can be done to improve.
I'm here in SF if you are at nanog.
Sent from my iCar
> On Feb 11, 2020, at 3:42 PM, Tom Deligiannis
> wrote:
>
> There is a major update that has released today, how's
There is a major update that has released today, how's everything looking
for everyone?
Tom
On Thu, Jan 23, 2020 at 10:14 AM Aaron Gould wrote:
> My gosh, what in the word was that coming out of my local Akamai aanp
> servers yesterday !? starting at about 12:00 noon central time lasting
>
Chris Adams wrote on 11/02/2020 17:30:
> Just curious what others do... I always assumed AS path filtering to
> customer (and their downstream customers) AS was a standard best
> practice.
It is.
Then again, there exists every exception to the rule you can think of.
If the exception has not
Anyone that is using blackhole communities should have enough Clue-fu
to adjust announcements along each pathway to have the correct sequence
of ASNs. Passing a route with a different upstream's ASN as the origin,
instead
of their own, is just *asking* for "blackhole leakage", where they
One of our multihomed customers is set up with some type of security
system from another upstream that can announce blackhole routes for
targeted IPs. They have a BGP policy to take those blackhole routes and
add our blackhole community string so that we can drop the traffic (and
we in turn
Large operators have very little to gain from calling out the equipment
suppliers. In my personal experience large operators are already getting custom
code builds based on their exact requirements, which include disabling many of
the “standard” features they don’t use.
Sent from my iPhone
>
Being realistic, as you mentioned, these vendors do not have the right
incentive.
Thats one thing that operators can do and maybe it should be a recurring
theme at NANOG, calling out vendors to put some sanity and logic into how
iACLs and CoPP are handled. They can do a lot if they cared to spend
On Tue, 11 Feb 2020 at 16:09, Ahmed Borno wrote:
> Sorry for the sad tone, i just wish network operators would find a way to
> challenge these vendors and call their less than optimal quality.
It's hard, TINA. We can talk about white label, but in the end of the
day, that box is just as
I remember my conversation with an executive one day, where I was
enlightened on corporate greed.
I asked, why is there no investment in quality code, and I was schooled.
The exec said, one dollar spent on fixing bugs, returns zero dollars but
one dollar spent on nee features brings in 3 dollars
On 2/11/2020 2:04 AM, Saku Ytti wrote:
> On Tue, 11 Feb 2020 at 09:09, Ahmed Borno wrote:
>
>> So yeah iACLs, CoPP and all sorts of basic precautions are needed, but I'm
>> thinking something more needs to be done, specially if these ancient code
>> stacks are being imported into new age
On Tue, 11 Feb 2020 at 09:09, Ahmed Borno wrote:
> So yeah iACLs, CoPP and all sorts of basic precautions are needed, but I'm
> thinking something more needs to be done, specially if these ancient code
> stacks are being imported into new age 'IoT' devices, multiplying the attack
> vector by
16 matches
Mail list logo
