On 2019-01-31 08:15, Mark Andrews wrote:
We actually have a hard time finding zones where all the servers are
broken enough to not work with servers that don’t fallback to plain
DNS on timeout. We can find zones where some of the servers are like
that, but there is usually one or more servers
the cost to Oracle for Akamai to deliver this junk traffic is not zero
and I have a hard time seeing how this issue is isolated to our network.
I'd also be interested to hear from anyone else who has been seeing
traffic spikes from public-yum.oracle.com.
-James Stahr
On 04/22/2016 12:31 PM, Frank Bulk wrote:
Being discussed on outages, too.
Our monitoring system saw access to www.amazon.com and www.cablelabs.com
(over v6) down via HE ... amazon came back up for me via Zayo, but when
www.cablelabs.com came back up, it was on HE. So the same as you.
So I
At 01:33 AM 3/11/2011, Owen DeLong wrote:
On Mar 10, 2011, at 11:22 PM, Dobbins, Roland wrote:
On Mar 11, 2011, at 2:02 PM, Owen DeLong wrote:
Frankly, unless you have parallel links, there isn't a definite
need to even number PtoP links for IPv6.
Every thing you need to do with an
At 04:33 AM 12/2/2010, Harris Hui wrote:
Hi,
Does anyone using ATT seeing the routing issue to Level3? We saw some
issue with the end users using ATT as a service provider having issue to
our upstream provider. Thanks
We saw issues with att last night as well. We called into Level3,
but
At 07:40 AM 11/17/2010, Fredy Kuenzler wrote:
Am 17.11.2010 10:19, schrieb Fredy Kuenzler:
We see a number of session towards downstreams flaps obviously caused by
prefix 120.29.240.0/21, originated by AS45158, transited by AS4739 (see
below).
#sh ip bgp 120.29.240.0
Number of BGP Routes
6 matches
Mail list logo
