Is anyone else seeing issues with Level3's DNS servers? We got an alert
our mail servers were down but mail is flowing normally, if slowly. Trying
to resolve our domain names against Google's 8.8.8.8 and OpenDNS's
208.67.222.222 servers seems fine but 4.2.2.2 and 4.2.2.1 is spotty at best,
Solid for me in the UK
dig @4.2.2.2 www.google.com +short
173.194.40.177
173.194.40.179
173.194.40.176
173.194.40.178
173.194.40.180
dig @4.2.2.2 www.amazon.com +short
205.251.242.54
On 03/09/14 16:03, Dann Schuler via Outages wrote:
Is anyone else seeing issues with Level3's DNS servers?
On 09/03/14 11:03 -0400, Dann Schuler via Outages wrote:
Is anyone else seeing issues with Level3's DNS servers? We got an alert
our mail servers were down but mail is flowing normally, if slowly. Trying
to resolve our domain names against Google's 8.8.8.8 and OpenDNS's
208.67.222.222 servers
Not sure about L3, but I have confirmation that GoDaddy Premium DNS
services are all down at the moment. I spoke with a rep and he informed me
that they don't have an estimate on return to service yet but that they
have all hands on deck working on this.
*Sean E. Smith*
Director of Network
Pinging and resolving for me in Dayton.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Sep 3, 2014 11:18 AM, Dann Schuler via Outages outages@outages.org
wrote:
Is anyone else seeing issues with Level3’s DNS servers? We got an alert
our mail
A few of our client domains just suddenly started failing to resolve. As it
turns out, those domains are ones whose name service is handled via
GoDaddy. There's a thread on Reddit that suggests that this is pretty
widespread, but the exact scope isn't known yet, and GD has not announced
the issue.
I'm seeing issues with domains using domaincontrol.com nameservers. Some
nameservers are answering queries.
dig [ommited] @pdns01.domaincontrol.com.
[ommited] IN A
;; ANSWER SECTION:
[ommited]3600IN A 66.209.212.92
;; AUTHORITY SECTION:
[ommited]. 3600
We have several sites with DNS at the GD Premium DNS service, all services
appeared to have returned to normal about ten minutes ago.
*Sean E. Smith*
Director of Network Operations at Simpleview
T 520.575.1151 x131
www.simpleviewinc.com
On Wed, Sep 3, 2014 at 8:12 AM, Mike Phipps via Outages
We’ve had major packet loss and routing issues with Cox at 9:48AM CST this
morning in the Dallas area. Possibly unrelated but time correlates.
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Sean Smith via
Outages
Sent: Wednesday, September 03, 2014 10:16 AM
To: Dann Schuler
On Wed, Sep 3, 2014 at 12:12 PM, Mike Phipps via Outages
outages@outages.org wrote:
A few of our client domains just suddenly started failing to resolve. As
it turns out, those domains are ones whose name service is handled via
GoDaddy. There's a thread on Reddit that suggests that this is
The CL edge point at 199.44.253.1 started dropping large amounts of traffic
at around 11:40 EST. It seems to have smoothed out for now, but it dropped
all of our tunnels for about 15 minutes.
Wed Sep 3 11:49:22 2014
Keys: Help Display mode Restart statistics Order of fields quit
Now getting this
[image: Inline image 1]
On Wed, Sep 3, 2014 at 12:43 PM, Luke Rockwell
luke.rockw...@alumni.berkeley.edu wrote:
tracert facebook.com
Tracing route to facebook.com [173.252.110.27]
over a maximum of 30 hops:
11 ms1 ms1 ms
21 ms1 ms1 ms
tracert facebook.com
Tracing route to facebook.com [173.252.110.27]
over a maximum of 30 hops:
11 ms1 ms1 ms
21 ms1 ms1 ms
3 1 ms1 ms1 ms
4 1 ms 1 ms 1 ms dc-sfo-agg-1--ucb-10ge.cenic.net
[137.164.50.16]
5 4 ms 2 ms 3 ms
Same for Washington DC, Atlanta, GA and Tallahassee, FL on all local
incumbent, CLEC and MSO networks.
On Wed, Sep 3, 2014 at 3:44 PM, Luke Rockwell via Outages
outages@outages.org wrote:
Now getting this
[image: Inline image 1]
On Wed, Sep 3, 2014 at 12:43 PM, Luke Rockwell
Our HTTPv6 monitoring showed “Connection refused” from 2:39 to 2:56 pm Central.
Frank
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Luke Rockwell
via Outages
Sent: Wednesday, September 03, 2014 2:45 PM
To: Outages@outages.org
Subject: Re: [outages] Facebook down
Now
Get back to work :)
I'm getting the same 'Sorry, something went wrong' error too from NJ, and
mobile is not working from ATT.
-James
On Wed, Sep 3, 2014 at 3:44 PM, Luke Rockwell via Outages
outages@outages.org wrote:
Now getting this
[image: Inline image 1]
On Wed, Sep 3, 2014 at
It was only down for me in Denver on Comcast for a few minutes. It has been
back up for me for around 20 minutes. I'm connecting via v6.
On Wed, Sep 3, 2014 at 1:54 PM, James Cornman via Outages
outages@outages.org wrote:
Get back to work :)
I'm getting the same 'Sorry, something went
No issue here
1.*** 0.0% 35.0 118.7 5.0
232.5 160.9
2. *** 0.0% 26.0 6.0
6.0 6.1 0.0
3. sanjbprj01-ae0.0.rd.sj.cox.net
0.0% 2 39.8
- Original Message -
From: Luke Rockwell via Outages outages@outages.org
Subject: [outages] Facebook down
tracert facebook.com
Tracing route to facebook.com [173.252.110.27]
over a maximum of 30 hops:
Facebook was being observed not to be able to refresh web UI newsfeeds here
Here in Brazil (Ceará State) normal. We have some trouble at 03:00 p.m
today. But this was solve in few minutes via Global Village Telecom.
On Wed, Sep 3, 2014 at 5:21 PM, John Neiberger via Outages
outages@outages.org wrote:
It was only down for me in Denver on Comcast for a few minutes. It
back from getting food and it is now online.
On Wed, Sep 3, 2014 at 1:14 PM, Cal Leeming [iops.io] c...@iops.io wrote:
Same from here, dies at the edge nodes;
traceroute to facebook.com (173.252.110.27), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 1.003 ms 0.746 ms 0.672
21 matches
Mail list logo
