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

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)

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

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

Re: [outages] DNSimple outage

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

Re: [outages] Outages google DNS

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

Re: [outages] Comcast DNS broken?

: 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

[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

Re: [outages] Comcast DNS broken?

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

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

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.

Re: [outages] Akamai Cert Issues today

rom 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 >>> >>> *Subjec

Re: [outages] Akamai Cert Issues today

-- >> *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 br

[outages] Skype outage

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

Re: [outages] Amazon S3 down

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

Re: [outages] Twitter down

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,

Re: [outages] Dyn outage continuing

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 <

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

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

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

>> 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

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

> (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