On Mon, Mar 16, 2015 at 10:02 AM, Jay Ashworth via Outages
outages@outages.org wrote:
How many eyeball networks are actually set up to execute that request
without requiring manual Tier 3 intervention? Any?
While they aren't technically eyeball networks, applying a cache flush at
these two
Can you give more details about the size (and type) of the attack? I'm
curious whether you think massive means 5Gbps, 50Gbps, or 500Gbps?
Damian
2015-06-09 4:14 GMT-07:00 Dushyanth Harinath via Outages
outages@outages.org:
Hello,
Our DC's null routed all our DNS server IPs due to a massive
https://www.reddit.com/r/verizon/comments/3bv0rx/verizon_fios_routing_problem_in_nynj/
User there reports this from Verizon:
An outage has been detected that impacts your ability to access the
Internet, send and receive email, streaming video services, including FiOS
Video On Demand. Estimated
On Thu, Apr 21, 2016 at 11:30 AM, chris via Outages
wrote:
> Anyone aware of any known outages/issues for FIOS? Have a handful of
> customers in northern NJ with business FIOS with 50%+ packet loss on all
> verizon hops. We have checked these customers and theres no
Also, for issues connecting to anything that's anycasted (8.8.8.8) or might
be served from a CDN (Google, Cloudflare, etc) please indicate your
location (and ISP) and provide a traceroute to the affected resource
(ideally a traceroute to tcp port 80 if you're complaining about a website).
Damian
This appears to be a problem on the Level3 network in the DFW region, which
is why only some of you see it. (Those who don't see it are in other
regions, peering with Google directly, or using other transit providers.)
For those seeing issues, I suggest escalating to Level3, perhaps after
trying
On Wed, May 30, 2018 at 11:25 AM James Sharp via Outages <
outages@outages.org> wrote:
> > On May 30, 2018, at 11:10 AM, Warren Kumari wrote:
> > On Wed, May 30, 2018 at 1:12 PM James Sharp via Outages <
> outages@outages.org> wrote:
> >
> >> 8.8.8.8 and 4.2.2.2 are returning SERVFAIL from our
On Tue, Oct 22, 2019 at 12:32 PM Scott Weeks via Outages <
outages@outages.org> wrote:
> https://status.aws.amazon.com/
>
> Intermittent DNS Resolution Errors - We are investigating reports
> of occasional DNS resolution errors with Route 53 and our external
> DNS providers. We are actively
They updated with:
"""
Update 5:20pm. Everybody is safe.
Fire destroyed SBG2. A part of SBG1 is destroyed. Firefighters are
protecting SBG3. no impact SBG4.
"""
and then:
"""
Update 7:20am
Fire is over. Firefighters continue to cool the buildings with the water.
We don’t have the access to the
It clearly *is* from 2010:
https://engineering.fb.com/2010/09/23/uncategorized/more-details-on-today-s-o
Damian
On Tue, Mar 5, 2024 at 11:13 AM Jay R. Ashworth via Outages <
outages@outages.org> wrote:
> Well, it seems equivocal whether that's about *this* outage
> rather than an earlier one --
10 matches
Mail list logo