Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Sajal Kayan via Outages 
> (Sometimes, RFC 1918 resolvers actually forward to Google Public DNS or
another public resolver.)

My point about it being general outage referred to the fact that many users
could not get answer from route53, even if they directly contacted aws
without involvement of Google.

DNS during the outage:
https://pulse.turbobytes.com/results/5adf25e4ecbe40692e003abb/
DNS now: https://pulse.turbobytes.com/results/5adf2a6becbe40692e003aee/

MTR during the outage:
https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad2/
MTR now: https://pulse.turbobytes.com/results/5adf2a60ecbe40692e003aec/

> 205.251.192.0
> 205.251.193.0
> 205.251.195.0
> 205.251.197.0
> 205.251.199.0

instagram.com simply had the unfortunate misfortune of having all their
assigned nameservers in the block Joseph mentioned, and perhaps Google
using HE upstream. The domain I included in the results above was lucky to
have 2 nameservers (205.251.194.143 and 205.251.196.84) not included in the
above list.



On Tue, Apr 24, 2018 at 8:04 PM Stephane Bortzmeyer via Outages <
outages@outages.org> wrote:

> On Tue, Apr 24, 2018 at 02:49:17PM +0200,
>  Stephane Bortzmeyer  wrote
>  a message of 39 lines which said:
>
> > > Feels like a general outage, not specific to 8.8.8.8
> >
> > I tend to disagree. See with 25 RIPE Atlas probes:
>
> > With the default resolver (sometimes Google Public DNS, sometimes not):
>
> If you look at the resolvers which SERVFAIL:
>
> % blaeu-resolve -r 25 --displayresolvers -4 instagram.com
> ...
> [ERROR: SERVFAIL] : 3 occurrences (resolvers ['10.0.0.194',
> '192.168.12.254', '8.8.4.4'])
> Test #12294305 done at 2018-04-24T12:50:42Z
>
> (Sometimes, RFC 1918 resolvers actually forward to Google Public DNS
> or another public resolver.)
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Sajal Kayan via Outages 
>> Feels like a general outage, not specific to 8.8.8.8

> I tend to disagree. See with 25 RIPE Atlas probes:

I see your point. It appears different route53 zones are behaving
differently. for example from my local network, instagram.com doesn't
resolve, but my own r53 hosted domains do.




On Tue, Apr 24, 2018 at 7:49 PM Stephane Bortzmeyer 
wrote:

> On Tue, Apr 24, 2018 at 12:45:06PM +,
>  Sajal Kayan  wrote
>  a message of 146 lines which said:
>
> > Feels like a general outage, not specific to 8.8.8.8
>
> I tend to disagree. See with 25 RIPE Atlas probes:
>
> With Google Public DNS :
>
> % blaeu-resolve -r 25 --nameserver 8.8.8.8 instagram.com
> Nameserver 8.8.8.8
> [ERROR: SERVFAIL] : 14 occurrences
> [TIMEOUT(S)] : 9 occurrences
> Test #12294276 done at 2018-04-24T12:46:17Z
>
> With the default resolver (sometimes Google Public DNS, sometimes not):
>
> % blaeu-resolve -r 25  instagram.com
> [2406:da00:ff00::3436:8e23 2406:da00:ff00::3446:721e
> 2406:da00:ff00::3446:eeb7 2406:da00:ff00::34cc:e891
> 2406:da00:ff00::36ad:4581 2406:da00:ff00::36d0:7332
> 2406:da00:ff00::36d0:7907 2406:da00:ff00::36d1:1123] : 1 occurrences
> [2406:da00:ff00::22e1:dd34 2406:da00:ff00::22e3:8da6
> 2406:da00:ff00::3414:dcb1 2406:da00:ff00::3415:5ced
> 2406:da00:ff00::3416:705d 2406:da00:ff00::3416:79b3
> 2406:da00:ff00::3416:a694 2406:da00:ff00::3448:914f] : 1 occurrences
> [2406:da00:ff00::22c2:3b71 2406:da00:ff00::22c4:6777
> 2406:da00:ff00::22c7:3507 2406:da00:ff00::22e0:b7a
> 2406:da00:ff00::22e1:dd34 2406:da00:ff00::22e3:8da6
> 2406:da00:ff00::34c8:f395 2406:da00:ff00::369c:f239] : 1 occurrences
> [2406:da00:ff00::22c0:9c50 2406:da00:ff00::22c1:9fa1
> 2406:da00:ff00::22c7:bdda 2406:da00:ff00::22e2:135a
> 2406:da00:ff00::342c:f9cd 2406:da00:ff00::34cb:8741
> 2406:da00:ff00::36ac:1f08 2406:da00:ff00::36ec:6f50] : 1 occurrences
> [2406:da00:ff00::22c2:3b71 2406:da00:ff00::22c4:6777
> 2406:da00:ff00::3416:a694 2406:da00:ff00::3448:914f
> 2406:da00:ff00::3449:ae77 2406:da00:ff00::3457:418e
> 2406:da00:ff00::34c8:f395 2406:da00:ff00::369c:f239] : 1 occurrences
> [ERROR: SERVFAIL] : 2 occurrences
> [2406:da00:ff00::22c4:8be5 2406:da00:ff00::22c4:926f
> 2406:da00:ff00::3446:eeb7 2406:da00:ff00::34cc:e891
> 2406:da00:ff00::36ad:4581 2406:da00:ff00::36d0:7332
> 2406:da00:ff00::36d0:7907 2406:da00:ff00::36d1:1123] : 1 occurrences
> [2406:da00:ff00::22c0:dc59 2406:da00:ff00::3406:4b91
> 2406:da00:ff00::3407:2ad0 2406:da00:ff00::34c8:2550
> 2406:da00:ff00::34cc:59e0 2406:da00:ff00::34ce:a080
> 2406:da00:ff00::3656:36bf 2406:da00:ff00::36d1:7380] : 1 occurrences
> [TIMEOUT(S)] : 3 occurrences
> [2406:da00:ff00::22c0:9c50 2406:da00:ff00::22c1:9fa1
> 2406:da00:ff00::22c7:bdda 2406:da00:ff00::22e2:135a
> 2406:da00:ff00::22e9:ffc5 2406:da00:ff00::23aa:5823
> 2406:da00:ff00::3404:8bc6 2406:da00:ff00::3416:3580] : 2 occurrences
> [2406:da00:ff00::22c2:3b71 2406:da00:ff00::22c4:6777
> 2406:da00:ff00::22c7:3507 2406:da00:ff00::22e0:b7a
> 2406:da00:ff00::22e1:dd34 2406:da00:ff00::3457:418e
> 2406:da00:ff00::34c8:f395 2406:da00:ff00::369c:f239] : 2 occurrences
> [2406:da00:ff00::22c2:3b71 2406:da00:ff00::22c4:6777
> 2406:da00:ff00::22c7:3507 2406:da00:ff00::3448:914f
> 2406:da00:ff00::3449:ae77 2406:da00:ff00::3457:418e
> 2406:da00:ff00::34c8:f395 2406:da00:ff00::369c:f239] : 2 occurrences
> [2406:da00:ff00::22c0:dc59 2406:da00:ff00::22c4:9e11
> 2406:da00:ff00::22c6:38da 2406:da00:ff00::22e5:803
> 2406:da00:ff00::3405:1c5f 2406:da00:ff00::3406:4b91
> 2406:da00:ff00::3407:2ad0 2406:da00:ff00::34c8:2550] : 1 occurrences
> [2406:da00:ff00::22c0:dc59 2406:da00:ff00::22c4:9e11
> 2406:da00:ff00::22c6:38da 2406:da00:ff00::22e5:803
> 2406:da00:ff00::3405:1c5f 2406:da00:ff00::3406:4b91
> 2406:da00:ff00::3407:2ad0 2406:da00:ff00::36d1:7380] : 1 occurrences
> [2406:da00:ff00::3416:705d 2406:da00:ff00::3416:79b3
> 2406:da00:ff00::3416:a694 2406:da00:ff00::3448:914f
> 2406:da00:ff00::3449:ae77 2406:da00:ff00::3457:418e
> 2406:da00:ff00::34c8:f395 2406:da00:ff00::369c:f239] : 1 occurrences
> [2406:da00:ff00::22c2:3b71 2406:da00:ff00::3416:79b3
> 2406:da00:ff00::3416:a694 2406:da00:ff00::3448:914f
> 2406:da00:ff00::3449:ae77 2406:da00:ff00::3457:418e
> 2406:da00:ff00::34c8:f395 2406:da00:ff00::369c:f239] : 1 occurrences
> [2406:da00:ff00::22c4:9e11 2406:da00:ff00::22c6:38da
> 2406:da00:ff00::22e5:803 2406:da00:ff00::3405:1c5f
> 2406:da00:ff00::3406:4b91 2406:da00:ff00::3407:2ad0
> 2406:da00:ff00::34c8:2550 2406:da00:ff00::34cc:59e0] : 1 occurrences
> [2406:da00:ff00::22c4:8be5 2406:da00:ff00::22c4:926f
> 2406:da00:ff00::22c5:780c 2406:da00:ff00::22c6:25e5
> 2406:da00:ff00::22cf:2a5 2406:da00:ff00::22e0:b113
> 2406:da00:ff00::2399:f729 2406:da00:ff00::342c:68f1] : 1 occurrences
> [2406:da00:ff00::2399:f729 2406:da00:ff00::342c:68f1
> 2406:da00:ff00::3436:8e23 2406:da00:ff00::3446:721e
> 2406:da00:ff00::3446:eeb7 2406:da00:ff00::34cc:e891
> 2406:da00:ff00::36ad:4581 2406:da00:ff00::36d0:7332] : 1 occurrences
> Test

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Sajal Kayan via Outages 
https://pulse.turbobytes.com/results/5adf25e4ecbe40692e003abb/

2 out of 4 nameservers for one of my domains hosted on route53 fail
consistently from some locations, directly querying route53.

Feels like a general outage, not specific to 8.8.8.8


On Tue, Apr 24, 2018 at 7:38 PM Russell Zen via Outages 
wrote:

> Confirmed Route53 affected on AWS status dashboard.
>
> Get Outlook for Android 
>
> --
> *From:* Outages  on behalf of Stephane
> Bortzmeyer via Outages 
> *Sent:* Tuesday, April 24, 2018 5:22:49 AM
>
> *To:* outages@outages.org
> *Subject:* Re: [outages] Google 8.8.8.8 Resolution of Route53 domains
> On Tue, Apr 24, 2018 at 02:01:09PM +0200,
>  Stephane Bortzmeyer via Outages  wrote
>  a message of 11 lines which said:
>
> > Can you provide a few names?
>
> meetup.com instagram.com
>
> Seen by the RIPE Atlas probes:
>
> % blaeu-resolve -r 100 -q A  --nameserver 8.8.8.8 instagram.com
> Nameserver 8.8.8.8
> [ERROR: SERVFAIL] : 54 occurrences
> [52.44.104.241 52.54.142.35 52.70.114.30 52.70.238.183 54.173.69.129
> 54.208.115.50 54.208.121.7 54.209.17.35] : 1 occurrences
> [8.7.198.45] : 1 occurrences
> [TIMEOUT(S)] : 44 occurrences
> Test #12293792 done at 2018-04-24T12:12:03Z
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Amazon S3 down

2017-02-28 Thread Sajal Kayan via Outages 
TCP connect to us-east-1 endpoints fail from everywhere for everyone,
including from an EC2 instance in same region. Not related to location of
user or the bucket/key being accessed.
 https://pulse.turbobytes.com/results/58b5caafecbe402e2100c0bb/

"increased error rates" = 100% error rates.

On Wed, Mar 1, 2017 at 1:58 AM Carlos Alvarez via Outages <
outages@outages.org> wrote:

> A German IT site is claiming it's a DDOS but didn't provide evidence.
> Some others are claiming they get sporadic S3 access.
>
>
> On Tue, Feb 28, 2017 at 11:07 AM, Anthony Hook 
> wrote:
>
> https://status.aws.amazon.com/
>
> Looks like: We are investigating increased error rates for Amazon S3
> requests in the US-EAST-1 Region.
>
>
> --Anthony Hook
>
> On Tue, Feb 28, 2017 at 12:04 PM Carlos Alvarez via Outages <
> outages@outages.org> wrote:
>
> We are unable to reach it from Cox cable, Highwinds, or Cogent from the
> Phoenix area.  Also several of the outage testing sites say it's down.
>
>
> --
> Carlos Alvarez
> 602-368-6403 <(602)%20368-6403>
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
>
>
> --
> Carlos Alvarez
> 602-368-6403 <(602)%20368-6403>
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Twitter down

2016-11-06 Thread Sajal Kayan via Outages 
Its starting to come back
Now: https://pulse.turbobytes.com/results/58201b18ecbe404c24005f0a/
Few minutes ago :
https://pulse.turbobytes.com/results/582019e9ecbe404c24005f01/

On Mon, Nov 7, 2016 at 1:13 PM Mark Tinka via Outages 
wrote:

> Saw the same from here in Jo'burg, but it just came back a few seconds
> ago...
>
>
> Mark.
>
>
> On 7/Nov/16 08:06, Robbie Trencheny via Outages wrote:
>
> Confirmed from Oakland, CA via Comcast home.
>
> On Sunday, November 6, 2016, Terry Hardie via Outages 
> wrote:
>
> Looks like their networks are not announced anymore. From 4 providers,
> we don't see any network matching 104.244.42.1, 104.244.42.65,
> 104.244.42.129 or 104.244.42.193 (A records for twitter.com)
>
> Wonder what happened to them...
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
>
> --
> Robbie Trencheny (@robbie )
> 925-884-3728
> robbie.io
>
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Dyn outage continuing

2016-10-21 Thread Sajal Kayan via Outages 
It appears most of the world cant reach Dyn :
https://pulse.turbobytes.com/results/580a5178ecbe402e2201a74c/
But for the most part, its resolving thru Google DNS/OpenDNS :
https://pulse.turbobytes.com/results/580a51ceecbe402e2201a74e/


On Sat, Oct 22, 2016 at 12:31 AM Andrew Bunde via Outages <
outages@outages.org> wrote:

> Don’t forget https://bit.namecoin.info/
>
>
>
>
>
> *From:* Outages [mailto:outages-boun...@outages.org] *On Behalf Of *Jason
> Antman via Outages
> *Sent:* Friday, October 21, 2016 1:25 PM
> *Cc:* outages@outages.org
>
>
> *Subject:* Re: [outages] Dyn outage continuing
>
>
>
> This is just a horribly painful example of why we/they should all follow
> the route of NetFlix (
> http://techblog.netflix.com/2013/05/denominating-multi-region-sites.html
> ) and use multiple DNS providers. Denominator (
> https://github.com/Netflix/denominator ) the tool NetFlix uses for this
> and open-sourced, currently supports managing (mirrored) DNS records across
> AWS Route53, RackSpace CloudDNS, DynECT and UltraDNS.
>
>
>
> -Jason
>
>
>
> On Fri, Oct 21, 2016 at 1:09 PM, Patrick W. Gilmore via Outages <
> outages@outages.org> wrote:
>
> It is a shame in that PagerDuty is affected.
>
>
>
> However, Dyn is far, far better positioned to withstand attacks than a
> company like PagerDuty could possibly be on their own. So I think PagerDuty
> did the right thing in using Dyn.
>
>
>
> Remember, Twitter, Pingdom, github, and lots of other people use Dyn. And
> this is the first major outage I have heard of their service.
>
>
>
> Let’s all be clear that Dyn has to be in the top 10 DNS infrastructures on
> the planet. Possibly the largest that sells DNS as a service. This is a
> serious attack, and the entire community should help track this miscreant
> down, then crush them like a bug.
>
>
>
> --
>
> TTFN,
>
> patrick
>
>
>
> On Oct 21, 2016, at 1:00 PM, Terry Hardie via Outages 
> wrote:
>
>
>
> It's a shame services like PagerDuty use Dyn. Now they're down too...
>
> On Fri, Oct 21, 2016 at 9:57 AM, Justin Krejci via Outages
>  wrote:
>
> Previously it was not affecting upper midwest for me, traces went to
> Chicago.
>
> Now traces to twitter DNS servers in Chicago are failing.
>
>
> 
> From: Neil Hanlon via Outages [outages@outages.org]
> Sent: Friday, October 21, 2016 11:16 AM
> To: Terry Hardie; outages@outages.org
> Subject: Re: [outages] Dyn outage continuing
>
> The attacks appear to be continuing again. We are experiencing issues in
> Europe/Asia.
>
> On Fri, Oct 21, 2016 at 12:13 PM Terry Hardie via Outages
>  wrote:
>
>
> Even though their page says the outage is resolved, I'm still getting
> DNS failures (return SERVFAIL, not no answer) to their anycast
> networks from California:
>
> $ dig @ns2.p34.dynect.net video.twimg.com
>
> ; <<>> DiG 9.3.2 <<>> @ns2.p34.dynect.net video.twimg.com
> ; (1 server found)
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 170
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;video.twimg.com.   IN  A
>
> ;; Query time: 3103 msec
> ;; SERVER: 204.13.250.34#53(204.13.250.34)
> ;; WHEN: Fri Oct 21 17:11:36 2016
> ;; MSG SIZE  rcvd: 33
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
> --
>
> KAYAK
>
> Neil Hanlon
>
> Devops Engineer
>
>
> +1 978 902 8171
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
>
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] feedly.com outage - can't be reached from Southeast Asia - CloudFlare issue?

2015-10-12 Thread Sajal Kayan via Outages 
I am not seeing issues (from Thailand), probably its passed.

FYI: https://www.cloudflarestatus.com/

Oct 12, 2015
Scheduled Network Maintenance in Singapore

Completed - The scheduled maintenance has been completed.
Oct 12, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will
provide updates as necessary.
Oct 12, 19:00 UTC
Scheduled - We’re performing scheduled network maintenance in Singapore.
Oct 12, 17:51 UTC


On Tue, Oct 13, 2015 at 4:26 AM Roland Dobbins via Outages <
outages@outages.org> wrote:

> On 13 Oct 2015, at 4:23, Roland Dobbins wrote:
>
> > Same thing for Reddit:
>
> And for CloudFlare itself:
>
> -
>
> Error 1001 Ray ID: 2345ddc460a630f0 • 2015-10-12 21:24:30 UTC
> DNS resolution error
> What happened?
>
> You've requested a page on a website (www.cloudflare.com) that is on the
> CloudFlare network. CloudFlare is currently unable to resolve your
> requested domain (www.cloudflare.com). There are two potential causes of
> this:
>
>  Most likely: if the owner just signed up for CloudFlare it can take
> a few minutes for the website's information to be distributed to our
> global network.
>  Less likely: something is wrong with this site's configuration.
> Usually this happens when accounts have been signed up with a partner
> organization (e.g., a hosting provider) and the provider's DNS fails.
>
> CloudFlare Ray ID: 2345ddc460a630f0 • Your IP: 202.176.81.112 •
> Performance & security by CloudFlare
>
> ---
> Roland Dobbins 
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Akamai Cert Issues today

2015-09-30 Thread Sajal Kayan via Outages 
https://news.ycombinator.com/item?id=6872318

www.irs.gov was never on https . The error is bad user experience, but its
common for all CDNs who listen on 443 regardless if customer has ssl
activated or not.

-Sajal

On Thu, Oct 1, 2015 at 5:14 AM Sajal Kayan <saja...@gmail.com> wrote:

> Question: was www.irs.gov ever on https ?
>
> On Thu, Oct 1, 2015 at 5:05 AM Sajal Kayan <saja...@gmail.com> wrote:
>
>> Agree with Chris Swingler
>>
>> https://cincinnati.com/ Gives NET::ERR_CERT_COMMON_NAME_INVALID . That
>> does not appear to be chain issues. Its because cincinnati.com is not in
>> the common name or in the SAN.
>>
>> The certificate provided is valid only for
>>
>> CN : a248.e.akamai.net
>> SAN:-
>> DNS Name: a248.e.akamai.net
>> DNS Name: *.akamaihd.net
>> DNS Name: *.akamaihd-staging.net
>> DNS Name: *.akamaized.net
>> DNS Name: *.akamaized-staging.net
>>
>> Looks like someone messed up DNS config, or forgot to add some SANs.
>>
>> https://pulse.turbobytes.com/results/560c5bb9ecbe400bf8001bc6/
>>
>> -Sajal
>>
>> On Thu, Oct 1, 2015 at 5:00 AM Jim Witherell <jawither...@yahoo.com>
>> wrote:
>>
>>> Another item: go to sslshopper.com and click "ssl checker" and type in
>>> www.Cincinnati.com or www. and see that the chain is broken.
>>>
>>> Sent from Yahoo Mail on Android
>>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>>> --
>>> *From*:"Jeff Walter" <jwal...@weebly.com>
>>> *Date*:Wed, Sep 30, 2015 at 5:55 PM
>>>
>>> *Subject*:Re: [outages] Akamai Cert Issues today
>>>
>>> It's not a problem with the CN or the SANs on the certificate. The issue
>>> is a broken trust path. My guess would be they're using a new root CA that
>>> doesn't have good coverage yet.
>>>
>>> On Wed, Sep 30, 2015 at 2:52 PM, Sajal Kayan via Outages <
>>> outages@outages.org> wrote:
>>>
>>>> Certificate validates for me (on chrome)
>>>> And also https://pulse.turbobytes.com/results/560c589decbe400bf8001bbf/ .
>>>> Tested from multiple points. The tool does TLS validations.
>>>> Unrelated: That endpoint seems to be blackholed from china...
>>>>
>>>> What common name do you see in the cert given to you? I see "
>>>> a248.e.akamai.net" which is valid.
>>>>
>>>> -Sajal
>>>>
>>>> On Thu, Oct 1, 2015 at 4:16 AM Jim Witherell via Outages <
>>>> outages@outages.org> wrote:
>>>>
>>>>> e noticed SSL warnings based around Akamai's "*a248.e.akamai.net
>>>>> <http://a248.e.akamai.net>*" certificate today.
>>>>> NET::ERR_CERT_COMMON_NAME_INVALID is the most common error we're seeing.
>>>>> Can anyone comment on what may be going on? Looks like the cert was 
>>>>> renewed
>>>>> or issued on 8/27/2015. Wonder why we are noticing the errors from
>>>>> multiple points on the internet now?
>>>>>
>>>>> Jim Witherell
>>>>>
>>>>> Cincinnati OH
>>>>> ___
>>>>> Outages mailing list
>>>>> Outages@outages.org
>>>>> https://puck.nether.net/mailman/listinfo/outages
>>>>>
>>>>>
>>>> ___
>>>> Outages mailing list
>>>> Outages@outages.org
>>>> https://puck.nether.net/mailman/listinfo/outages
>>>>
>>>>
>>>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Akamai Cert Issues today

2015-09-30 Thread Sajal Kayan via Outages 
Question: was www.irs.gov ever on https ?

On Thu, Oct 1, 2015 at 5:05 AM Sajal Kayan <saja...@gmail.com> wrote:

> Agree with Chris Swingler
>
> https://cincinnati.com/ Gives NET::ERR_CERT_COMMON_NAME_INVALID . That
> does not appear to be chain issues. Its because cincinnati.com is not in
> the common name or in the SAN.
>
> The certificate provided is valid only for
>
> CN : a248.e.akamai.net
> SAN:-
> DNS Name: a248.e.akamai.net
> DNS Name: *.akamaihd.net
> DNS Name: *.akamaihd-staging.net
> DNS Name: *.akamaized.net
> DNS Name: *.akamaized-staging.net
>
> Looks like someone messed up DNS config, or forgot to add some SANs.
>
> https://pulse.turbobytes.com/results/560c5bb9ecbe400bf8001bc6/
>
> -Sajal
>
> On Thu, Oct 1, 2015 at 5:00 AM Jim Witherell <jawither...@yahoo.com>
> wrote:
>
>> Another item: go to sslshopper.com and click "ssl checker" and type in
>> www.Cincinnati.com or www. and see that the chain is broken.
>>
>> Sent from Yahoo Mail on Android
>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>> --
>> *From*:"Jeff Walter" <jwal...@weebly.com>
>> *Date*:Wed, Sep 30, 2015 at 5:55 PM
>>
>> *Subject*:Re: [outages] Akamai Cert Issues today
>>
>> It's not a problem with the CN or the SANs on the certificate. The issue
>> is a broken trust path. My guess would be they're using a new root CA that
>> doesn't have good coverage yet.
>>
>> On Wed, Sep 30, 2015 at 2:52 PM, Sajal Kayan via Outages <
>> outages@outages.org> wrote:
>>
>>> Certificate validates for me (on chrome)
>>> And also https://pulse.turbobytes.com/results/560c589decbe400bf8001bbf/ .
>>> Tested from multiple points. The tool does TLS validations.
>>> Unrelated: That endpoint seems to be blackholed from china...
>>>
>>> What common name do you see in the cert given to you? I see "
>>> a248.e.akamai.net" which is valid.
>>>
>>> -Sajal
>>>
>>> On Thu, Oct 1, 2015 at 4:16 AM Jim Witherell via Outages <
>>> outages@outages.org> wrote:
>>>
>>>> e noticed SSL warnings based around Akamai's "*a248.e.akamai.net
>>>> <http://a248.e.akamai.net>*" certificate today.
>>>> NET::ERR_CERT_COMMON_NAME_INVALID is the most common error we're seeing.
>>>> Can anyone comment on what may be going on? Looks like the cert was renewed
>>>> or issued on 8/27/2015. Wonder why we are noticing the errors from
>>>> multiple points on the internet now?
>>>>
>>>> Jim Witherell
>>>>
>>>> Cincinnati OH
>>>> ___
>>>> Outages mailing list
>>>> Outages@outages.org
>>>> https://puck.nether.net/mailman/listinfo/outages
>>>>
>>>>
>>> ___
>>> Outages mailing list
>>> Outages@outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
>>>
>>>
>>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Skype outage

2015-09-21 Thread Sajal Kayan via Outages 
http://memeburn.com/2015/09/skype-working-on-a-fix-as-communication-service-faces-worldwide-outage/

Status shows as offline, but messaging apparently works. Calls dont.
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Comcast DNS broken?

2015-06-05 Thread Sajal Kayan via Outages 
http://arstechnica.com/business/2015/06/comcast-issuing-5-credits-after-internet-outage-caused-by-dns-failure/

What happened

A piece of hardware in our backbone network failed yesterday morning.
Hardware issues of this sort are fairly commonplace and redundancy in our
network addressed any immediate concern.

Most backbone networks, including Comcast’s, are designed to heal
themselves and route traffic along alternate paths much like a detour would
route automobile traffic around a street closed for construction.

One type of traffic that gets automatically rerouted is Domain Name System
(DNS) traffic. Unfortunately, some of that traffic shifted in an unexpected
way and overloaded local DNS server capacity causing many customers to
experience service interruptions.

What we are doing about it

Since the incident, we have been working non-stop to fully understand the
problem and bring additional DNS capacity online in the affected areas, so
we can prevent it from happening again.


On Tue, Jun 2, 2015 at 11:00 AM Sajal Kayan saja...@gmail.com wrote:

 Seems to work now only occasionally dropping queries...

 On Mon, Jun 1, 2015 at 8:12 PM, Frank Bulk frnk...@iname.com wrote:

 I don’t see anything on dns.comcast.net.



 I will forward to my Comcast contacts.



 Frank



 *From:* Outages [mailto:outages-boun...@outages.org] *On Behalf Of *Sajal
 Kayan via Outages
 *Sent:* Monday, June 01, 2015 10:06 PM
 *To:* OUTAGES Mailing List
 *Subject:* [outages] Comcast DNS broken?



 Hi,



 Comcast DNS servers (75.75.75.75, 75.75.76.76) seem to be down. Web pages
 were suck at dns resolution phase, switching to Google DNS solved the
 problem immediately.



 Tested from San Francisco.



 sajal@sajal-lappy:~$ mtr --report 75.75.75.75

 Start: Mon Jun  1 20:03:02 2015

 HOST: sajal-lappy Loss%   Snt   Last   Avg  Best  Wrst
 StDev

   1.|-- 10.0.1.1   0.0%101.2   3.1   1.0   5.9
 1.2

   2.|-- 50.174.142.1   0.0%10   15.9  20.7  14.6  49.7
  10.4

   3.|-- te-0-7-0-5-sur03.sffolsom  0.0%10   16.9  24.1  16.4  54.6
  11.6

   4.|-- be-209-ar01.santaclara.ca  0.0%10   18.2  33.4  17.0 146.1
  39.9

   5.|-- he-0-14-0-0-ar01.sfsutro.  0.0%10   22.4  26.9  20.0  42.9
 6.8

   6.|-- te-9-4-ur01-d.sanjose.ca.  0.0%10   22.9  23.1  20.6  28.4
 2.0

   7.|-- te-8-2-ur01-d.sanjose.ca.  0.0%10   21.5  23.4  20.6  29.2
 3.1

   8.|-- cdns01.comcast.net 0.0%10   32.2  47.3  20.5  89.7
  29.0

 sajal@sajal-lappy:~$ dig google.com @75.75.75.75



 ;  DiG 9.9.5-3ubuntu0.2-Ubuntu  google.com @75.75.75.75

 ;; global options: +cmd

 ;; connection timed out; no servers could be reached

 sajal@sajal-lappy:~$





 https://pulse.turbobytes.com/results/556d1b32ecbe4023ebab/ - Using
 our tool we see timeout from Seattle and Mountain View. Is this a national
 level outage or something?



 -Sajal



___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Comcast DNS broken?

2015-06-01 Thread Sajal Kayan via Outages 
Hi,

Comcast DNS servers (75.75.75.75, 75.75.76.76) seem to be down. Web pages
were suck at dns resolution phase, switching to Google DNS solved the
problem immediately.

Tested from San Francisco.

sajal@sajal-lappy:~$ mtr --report 75.75.75.75
Start: Mon Jun  1 20:03:02 2015
HOST: sajal-lappy Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.0.1.1   0.0%101.2   3.1   1.0   5.9   1.2
  2.|-- 50.174.142.1   0.0%10   15.9  20.7  14.6  49.7  10.4
  3.|-- te-0-7-0-5-sur03.sffolsom  0.0%10   16.9  24.1  16.4  54.6  11.6
  4.|-- be-209-ar01.santaclara.ca  0.0%10   18.2  33.4  17.0 146.1  39.9
  5.|-- he-0-14-0-0-ar01.sfsutro.  0.0%10   22.4  26.9  20.0  42.9   6.8
  6.|-- te-9-4-ur01-d.sanjose.ca.  0.0%10   22.9  23.1  20.6  28.4   2.0
  7.|-- te-8-2-ur01-d.sanjose.ca.  0.0%10   21.5  23.4  20.6  29.2   3.1
  8.|-- cdns01.comcast.net 0.0%10   32.2  47.3  20.5  89.7  29.0
sajal@sajal-lappy:~$ dig google.com @75.75.75.75

;  DiG 9.9.5-3ubuntu0.2-Ubuntu  google.com @75.75.75.75
;; global options: +cmd
;; connection timed out; no servers could be reached
sajal@sajal-lappy:~$


https://pulse.turbobytes.com/results/556d1b32ecbe4023ebab/ - Using our
tool we see timeout from Seattle and Mountain View. Is this a national
level outage or something?

-Sajal
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Comcast DNS broken?

2015-06-01 Thread Sajal Kayan via Outages 
Seems to work now only occasionally dropping queries...

On Mon, Jun 1, 2015 at 8:12 PM, Frank Bulk frnk...@iname.com wrote:

 I don’t see anything on dns.comcast.net.



 I will forward to my Comcast contacts.



 Frank



 *From:* Outages [mailto:outages-boun...@outages.org] *On Behalf Of *Sajal
 Kayan via Outages
 *Sent:* Monday, June 01, 2015 10:06 PM
 *To:* OUTAGES Mailing List
 *Subject:* [outages] Comcast DNS broken?



 Hi,



 Comcast DNS servers (75.75.75.75, 75.75.76.76) seem to be down. Web pages
 were suck at dns resolution phase, switching to Google DNS solved the
 problem immediately.



 Tested from San Francisco.



 sajal@sajal-lappy:~$ mtr --report 75.75.75.75

 Start: Mon Jun  1 20:03:02 2015

 HOST: sajal-lappy Loss%   Snt   Last   Avg  Best  Wrst
 StDev

   1.|-- 10.0.1.1   0.0%101.2   3.1   1.0   5.9
 1.2

   2.|-- 50.174.142.1   0.0%10   15.9  20.7  14.6  49.7
  10.4

   3.|-- te-0-7-0-5-sur03.sffolsom  0.0%10   16.9  24.1  16.4  54.6
  11.6

   4.|-- be-209-ar01.santaclara.ca  0.0%10   18.2  33.4  17.0 146.1
  39.9

   5.|-- he-0-14-0-0-ar01.sfsutro.  0.0%10   22.4  26.9  20.0  42.9
 6.8

   6.|-- te-9-4-ur01-d.sanjose.ca.  0.0%10   22.9  23.1  20.6  28.4
 2.0

   7.|-- te-8-2-ur01-d.sanjose.ca.  0.0%10   21.5  23.4  20.6  29.2
 3.1

   8.|-- cdns01.comcast.net 0.0%10   32.2  47.3  20.5  89.7
  29.0

 sajal@sajal-lappy:~$ dig google.com @75.75.75.75



 ;  DiG 9.9.5-3ubuntu0.2-Ubuntu  google.com @75.75.75.75

 ;; global options: +cmd

 ;; connection timed out; no servers could be reached

 sajal@sajal-lappy:~$





 https://pulse.turbobytes.com/results/556d1b32ecbe4023ebab/ - Using
 our tool we see timeout from Seattle and Mountain View. Is this a national
 level outage or something?



 -Sajal

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Outages google DNS

2015-02-10 Thread Sajal Kayan via Outages 
There are indications of a broken fiber cable connection, causing a
massive network issue in the Amsterdam area. -
https://twitter.com/StatusPltfrmIQ/status/565078428442198016

A dutch person told me he cant access many government sites and some news
sites. An example site he cant access is http://www.rijksoverheid.nl




On Tue, Feb 10, 2015 at 5:04 PM, Nicholas Schmidt via Outages 
outages@outages.org wrote:

 I too have been registering failures when attempting to use Googles public
 resolvers at 8.8.8.8 via the AMSIX exchange. This began at roughly 0200
 GMT.

 We have not attempted via transit or alternative Google DNS resolvers.

 -Nick


 On 2/10/15, 4:37 PM, Aditya Patawari via Outages outages@outages.org
 wrote:

 I am seeing intermittent issue from EU, specifically from Amsterdam.
 US and Asian datacenters are fine for me.
 curl: (6) Could not resolve host: www.XYZ.com
 
 Regards,
 Aditya Patawari
 http://blog.adityapatawari.com/
 India
 
 
 On Tue, Feb 10, 2015 at 2:41 PM, dikshie via Outages
 outages@outages.org wrote:
 
 
  On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages
  outages@outages.org wrote:
 
  Hi all,
 
 
 
  Is anybody else having issues with the Google DNS public servers?  From
  the Amsterdam region (specifically using the Amsterdam Internet
 Exchange or
  other peering platforms) Google DNS is unresponsive. Several other
 providers
  here see the same results.
 
 
 
 
 
 
 
 
  no problem in Japan.
 
 
  ;  DiG 9.8.3-P1  @8.8.8.8 ox.ac.uk NS
 
  ; (1 server found)
 
  ;; global options: +cmd
 
  ;; Got answer:
 
  ;; -HEADER- opcode: QUERY, status: NOERROR, id: 12558
 
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
 
 
  ;; QUESTION SECTION:
 
  ;ox.ac.uk. IN NS
 
 
  ;; ANSWER SECTION:
 
  ox.ac.uk. 21419 IN NS ns2.ja.net.
 
  ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
 
  ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
 
  ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
 
 
  ;; Query time: 43 msec
 
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
 
  ;; WHEN: Tue Feb 10 18:09:43 2015
 
  ;; MSG SIZE  rcvd: 107
 
 
 
  ;  DiG 9.8.3-P1  @8.8.4.4 ox.ac.uk NS
 
  ; (1 server found)
 
  ;; global options: +cmd
 
  ;; Got answer:
 
  ;; -HEADER- opcode: QUERY, status: NOERROR, id: 25190
 
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
 
 
  ;; QUESTION SECTION:
 
  ;ox.ac.uk. IN NS
 
 
  ;; ANSWER SECTION:
 
  ox.ac.uk. 21599 IN NS ns2.ja.net.
 
  ox.ac.uk. 21599 IN NS dns0.ox.ac.uk.
 
  ox.ac.uk. 21599 IN NS dns2.ox.ac.uk.
 
  ox.ac.uk. 21599 IN NS dns1.ox.ac.uk.
 
 
  ;; Query time: 301 msec
 
  ;; SERVER: 8.8.4.4#53(8.8.4.4)
 
  ;; WHEN: Tue Feb 10 18:09:43 2015
 
  ;; MSG SIZE  rcvd: 107
 
 
 
  ;  DiG 9.8.3-P1  @2001:4860:4860:: ox.ac.uk NS
 
  ; (1 server found)
 
  ;; global options: +cmd
 
  ;; Got answer:
 
  ;; -HEADER- opcode: QUERY, status: NOERROR, id: 34841
 
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
 
 
  ;; QUESTION SECTION:
 
  ;ox.ac.uk. IN NS
 
 
  ;; ANSWER SECTION:
 
  ox.ac.uk. 5821 IN NS dns1.ox.ac.uk.
 
  ox.ac.uk. 5821 IN NS dns0.ox.ac.uk.
 
  ox.ac.uk. 5821 IN NS dns2.ox.ac.uk.
 
  ox.ac.uk. 5821 IN NS ns2.ja.net.
 
 
  ;; Query time: 67 msec
 
  ;; SERVER: 2001:4860:4860::#53(2001:4860:4860::)
 
  ;; WHEN: Tue Feb 10 18:09:43 2015
 
  ;; MSG SIZE  rcvd: 107
 
 
 
  ;  DiG 9.8.3-P1  @2001:4860:4860::8844 ox.ac.uk NS
 
  ; (1 server found)
 
  ;; global options: +cmd
 
  ;; Got answer:
 
  ;; -HEADER- opcode: QUERY, status: NOERROR, id: 36150
 
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
 
 
  ;; QUESTION SECTION:
 
  ;ox.ac.uk. IN NS
 
 
  ;; ANSWER SECTION:
 
  ox.ac.uk. 21419 IN NS ns2.ja.net.
 
  ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
 
  ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
 
  ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
 
 
  ;; Query time: 72 msec
 
  ;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
 
  ;; WHEN: Tue Feb 10 18:09:43 2015
 
  ;; MSG SIZE  rcvd: 107
 
 
  traceroute from 192.168.0.9 to 8.8.8.8
 
   1  192.168.0.1  0.691 ms [mtu: 1500]
 
   2  121.106.107.1  2.943 ms [mtu: 1500]
 
   3  125.48.119.34  1.452 ms [mtu: 1500]
 
   4  118.152.208.134  2.283 ms [mtu: 1500]
 
   5  118.152.210.45  3.166 ms [mtu: 1500]
 
   6  106.162.175.153  3.487 ms [mtu: 1500]
 
   7  59.128.5.86  2.968 ms [mtu: 1500]
 
   8  72.14.204.58  48.487 ms [mtu: 1500]
 
   9  72.14.237.70  48.530 ms [mtu: 1500]
 
  10  66.249.95.109  3.489 ms [mtu: 1500]
 
  11  8.8.8.8  6.759 ms [mtu: 1500]
 
  traceroute from 192.168.0.9 to 8.8.4.4
 
   1  192.168.0.1  0.648 ms [mtu: 1500]
 
   2  121.106.107.1  1.987 ms [mtu: 1500]
 
   3  125.48.119.34  2.616 ms [mtu: 1500]
 
   4  118.152.208.134  1.720 ms [mtu: 1500]
 
   5  111.86.159.109  3.594 ms [mtu: 1500]
 
   6  106.162.175.161  3.249 ms [mtu: 1500]
 
   7  59.128.5.94  2.328 ms [mtu: 1500]
 
   8  72.14.204.58  45.635 ms [mtu: 1500]
 
   9  72.14.236.215  3.090 ms [mtu: 1500]
 
  10  72.14.239.165  3.717 ms [mtu: 1500]
 
  11  8.8.4.4

Re: [outages] DNSimple outage

2014-12-01 Thread Sajal Kayan via Outages 
More updates on their status page
http://dnsimplestatus.com/incidents/v0x4h75gxf7x

On Tue, Dec 2, 2014 at 3:14 AM, Grant Ridder via Outages 
outages@outages.org wrote:

 They are reporting a DDoS attack via their Twitter

 Sent from my iPhone

  On Dec 1, 2014, at 12:08 PM, Stephane Bortzmeyer bortzme...@nic.fr
 wrote:
 
  On Mon, Dec 01, 2014 at 11:30:42AM -0800,
  Grant Ridder via Outages outages@outages.org wrote
  a message of 38 lines which said:
 
  We are seeing a system-wide DNS outage. Investigating now.
  https://twitter.com/dnsimple/status/539499331670511616
 
  All DNS servers down:
 
  % check-soa -i -ns ns1.dnsimple.com. ns2.dnsimple.com. ns3.dnsimple.com.
 ns4.dnsimple.com. dnsimple.com.
  ns1.dnsimple.com.
 2620:111:8000::53: ERROR: Timeout
 198.241.10.53: ERROR: Timeout
  ns2.dnsimple.com.
 2620:111:8001::53: ERROR: Timeout
 198.241.11.53: ERROR: Timeout
  ns3.dnsimple.com.
 2620:111:8002::53: ERROR: Timeout
 50.31.242.53: ERROR: Timeout
  ns4.dnsimple.com.
 2620:111:8003::53: ERROR: Timeout
 50.31.243.53: ERROR: Timeout

 ___
 Outages mailing list
 Outages@outages.org
 https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Google Public DNS is down in south-east asia

2014-10-13 Thread Sajal Kayan via Outages 
Google Public DNS just stopped working for me (and many others locally).

xxx@xxx:~# dig google.com @8.8.8.8

;  DiG 9.8.4-rpz2+rl005.12-P1  google.com @8.8.8.8
;; global options: +cmd
;; connection timed out; no servers could be reached
xxx@xxx:~#

Traces from few locations.

True ADSL (Thailand)

xxx@xxx:~# mtr --report 8.8.8.8
HOST: xxx Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.1.10.0%10   30.5  17.4   0.8  57.5  22.5
  2.|-- ???   100.0100.0   0.0   0.0   0.0   0.0
  3.|-- 10.169.212.9   0.0%10   23.3  24.0  23.3  25.0   0.6
  4.|-- 10.100.50.67   0.0%10   24.0  24.3  23.7  25.1   0.5
  5.|-- 58.97.121.81   0.0%10   25.4  25.1  24.5  25.6   0.4
  6.|-- 61.91.213.177  0.0%10   24.6  25.0  24.6  25.6   0.3
  7.|-- 61.91.213.36   0.0%10   26.1  25.9  25.4  26.4   0.3
  8.|-- 61.91.213.130  0.0%10   25.5  26.0  25.1  27.3   0.6
  9.|-- 113.21.242.53  0.0%10   27.0  26.5  25.1  28.2   1.0
 10.|-- 72.14.210.155  0.0%10   49.1  52.2  48.1  80.4   9.9
 11.|-- 209.85.242.244 0.0%10   54.6  53.6  50.0  60.9   4.1
 12.|-- 72.14.239.201  0.0%10   85.6  85.7  80.2 100.8   6.5
 13.|-- 209.85.250.11  0.0%10  107.2 107.7 106.7 109.7   0.9
* 14.|-- 209.85.243.21  0.0%10  109.6 110.4 109.5 111.3
0.6*
 15.|-- ???   100.0100.0   0.0   0.0   0.0   0.0
xxx@xxx:~#


Digital Ocean (Singapore)

xxx@xxx:~# mtr --report 8.8.8.8
Start: Mon Oct 13 07:18:28 2014
HOST: xxx  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- a.b.c.d0.0%100.6   1.6   0.5   6.0   2.1
  2.|-- 103.253.144.2410.0%100.4   0.5   0.4   0.6   0.0
  3.|-- 103.16.102.64  0.0%101.8   2.0   1.7   3.4   0.3
  4.|-- 66.249.95.122  0.0%102.1   2.1   2.0   2.3   0.0
  5.|-- 209.85.241.149 0.0%10   54.5  56.1  54.3  61.8   2.5
*  6.|-- 72.14.237.179  0.0%10   58.0  58.1  57.9  59.2
0.0*
  7.|-- ???   100.0100.0   0.0   0.0   0.0   0.0
xxx@xxx:~#


EC2 (Singapore)

xxx@xxx:~$ mtr --report 8.8.8.8
HOST: xxxLoss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ip-10-a-b-2.ap-southea  0.0%100.6   0.6   0.3   1.5   0.4
  2.|-- ip-10-1-16-0.ap-southeast  0.0%106.1   1.6   0.5   6.1   1.8
  3.|-- 100.64.12.131  0.0%10   17.8   3.8   1.0  17.8   5.7
  4.|-- ec2-175-41-128-232.ap-sou  0.0%100.8   0.6   0.5   0.9   0.1
  5.|-- 203.83.223.230 0.0%100.6   1.0   0.4   2.3   0.7
  6.|-- 203.83.223.14  0.0%101.5   1.6   1.4   2.4   0.3
  7.|-- 203.83.223.57  0.0%101.7   1.8   1.5   2.4   0.2
  8.|-- 198.32.141.140 0.0%101.5   1.7   1.4   3.2   0.5
  9.|-- 66.249.95.122  0.0%102.9   5.4   2.2  14.7   4.8
 10.|-- 209.85.241.149 0.0%10   54.2  57.7  54.0  76.5   7.6
 11.|-- 209.85.243.23  0.0%10   57.9  60.1  57.7  79.4   6.8
 12.|-- 72.14.238.80.0%10   58.9  59.3  58.8  62.5   1.1
* 13.|-- 72.14.237.179  0.0%10   63.0  65.3  62.8  79.2
5.4*
 14.|-- ???   100.0100.0   0.0   0.0   0.0   0.0
xxx@xxx:~$
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google Public DNS is down in south-east asia

2014-10-13 Thread Sajal Kayan via Outages 
Works fine now as of 11:29 UTC.
The first i noticed any issues was at ~11:12 UTC (i was offline before
then).
Someone else indicated that the outage lasted ~33 minutes.

On Mon, Oct 13, 2014 at 6:25 PM, Sajal Kayan saja...@gmail.com wrote:

 Google Public DNS just stopped working for me (and many others locally).

 xxx@xxx:~# dig google.com @8.8.8.8

 ;  DiG 9.8.4-rpz2+rl005.12-P1  google.com @8.8.8.8
 ;; global options: +cmd
 ;; connection timed out; no servers could be reached
 xxx@xxx:~#

 Traces from few locations.

 True ADSL (Thailand)

 xxx@xxx:~# mtr --report 8.8.8.8
 HOST: xxx Loss%   Snt   Last   Avg  Best  Wrst
 StDev
   1.|-- 192.168.1.10.0%10   30.5  17.4   0.8  57.5
  22.5
   2.|-- ???   100.0100.0   0.0   0.0   0.0
 0.0
   3.|-- 10.169.212.9   0.0%10   23.3  24.0  23.3  25.0
 0.6
   4.|-- 10.100.50.67   0.0%10   24.0  24.3  23.7  25.1
 0.5
   5.|-- 58.97.121.81   0.0%10   25.4  25.1  24.5  25.6
 0.4
   6.|-- 61.91.213.177  0.0%10   24.6  25.0  24.6  25.6
 0.3
   7.|-- 61.91.213.36   0.0%10   26.1  25.9  25.4  26.4
 0.3
   8.|-- 61.91.213.130  0.0%10   25.5  26.0  25.1  27.3
 0.6
   9.|-- 113.21.242.53  0.0%10   27.0  26.5  25.1  28.2
 1.0
  10.|-- 72.14.210.155  0.0%10   49.1  52.2  48.1  80.4
 9.9
  11.|-- 209.85.242.244 0.0%10   54.6  53.6  50.0  60.9
 4.1
  12.|-- 72.14.239.201  0.0%10   85.6  85.7  80.2 100.8
 6.5
  13.|-- 209.85.250.11  0.0%10  107.2 107.7 106.7 109.7
 0.9
 * 14.|-- 209.85.243.21  0.0%10  109.6 110.4 109.5 111.3
 0.6*
  15.|-- ???   100.0100.0   0.0   0.0   0.0
 0.0
 xxx@xxx:~#


 Digital Ocean (Singapore)

 xxx@xxx:~# mtr --report 8.8.8.8
 Start: Mon Oct 13 07:18:28 2014
 HOST: xxx  Loss%   Snt   Last   Avg  Best  Wrst StDev
   1.|-- a.b.c.d0.0%100.6   1.6   0.5   6.0   2.1
   2.|-- 103.253.144.2410.0%100.4   0.5   0.4   0.6
 0.0
   3.|-- 103.16.102.64  0.0%101.8   2.0   1.7   3.4
 0.3
   4.|-- 66.249.95.122  0.0%102.1   2.1   2.0   2.3
 0.0
   5.|-- 209.85.241.149 0.0%10   54.5  56.1  54.3  61.8
 2.5
 *  6.|-- 72.14.237.179  0.0%10   58.0  58.1  57.9  59.2
 0.0*
   7.|-- ???   100.0100.0   0.0   0.0   0.0
 0.0
 xxx@xxx:~#


 EC2 (Singapore)

 xxx@xxx:~$ mtr --report 8.8.8.8
 HOST: xxxLoss%   Snt   Last   Avg  Best  Wrst StDev
   1.|-- ip-10-a-b-2.ap-southea  0.0%100.6   0.6   0.3   1.5   0.4
   2.|-- ip-10-1-16-0.ap-southeast  0.0%106.1   1.6   0.5   6.1
 1.8
   3.|-- 100.64.12.131  0.0%10   17.8   3.8   1.0  17.8
 5.7
   4.|-- ec2-175-41-128-232.ap-sou  0.0%100.8   0.6   0.5   0.9
 0.1
   5.|-- 203.83.223.230 0.0%100.6   1.0   0.4   2.3
 0.7
   6.|-- 203.83.223.14  0.0%101.5   1.6   1.4   2.4
 0.3
   7.|-- 203.83.223.57  0.0%101.7   1.8   1.5   2.4
 0.2
   8.|-- 198.32.141.140 0.0%101.5   1.7   1.4   3.2
 0.5
   9.|-- 66.249.95.122  0.0%102.9   5.4   2.2  14.7
 4.8
  10.|-- 209.85.241.149 0.0%10   54.2  57.7  54.0  76.5
 7.6
  11.|-- 209.85.243.23  0.0%10   57.9  60.1  57.7  79.4
 6.8
  12.|-- 72.14.238.80.0%10   58.9  59.3  58.8  62.5
 1.1
 * 13.|-- 72.14.237.179  0.0%10   63.0  65.3  62.8  79.2
 5.4*
  14.|-- ???   100.0100.0   0.0   0.0   0.0
 0.0
 xxx@xxx:~$

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages