Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?



  • Yesterday and today I have had super slow loading on the Office 365 admin portal. Today, I have seen Outlook throw a security cert warning, twice, and some websites are also showing SSL error pages.

    I have Google DNS setup as some forwarders and use their IPs as a gauge for WAN connectivity, as it is easy to remember their IPs. I started a ping -t to 8.8.8.8, 8.8.4.4 and 4.2.2.2 and normally, I will get a 4ms average on all 3. Today, I am getting 23-25 on 8.8.8.8 and 8.8.4.4 with several request timed outs sprinkled in (at the same time as one another). 4.2.2.2 is very stable and averaging 4ms.

    I can't seem to find much info on down detector. It seems that there are some external network issues, somewhere. I will be calling my ISP, but wanted to see if anyone else was having issues also.

    Edit: I am in Southern California



  • @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    Yesterday and today I have had super slow loading on the Office 365 admin portal. Today, I have seen Outlook throw a security cert warning, twice, and some websites are also showing SSL error pages.

    I have Google DNS setup as some forwarders and use their IPs as a gauge for WAN connectivity, as it is easy to remember their IPs. I started a ping -t to 8.8.8.8, 8.8.4.4 and 4.2.2.2 and normally, I will get a 4ms average on all 3. Today, I am getting 23-25 on 8.8.8.8 and 8.8.4.4 with several request timed outs sprinkled in (at the same time as one another). 4.2.2.2 is very stable and averaging 4ms.

    I can't seem to find much info on down detector. It seems that there are some external network issues, somewhere. I will be calling my ISP, but wanted to see if anyone else was having issues also.

    Edit: I am in Southern California

    Have you tried to use 1.1.1.1 from CloudFlare?



  • @dbeato said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    Yesterday and today I have had super slow loading on the Office 365 admin portal. Today, I have seen Outlook throw a security cert warning, twice, and some websites are also showing SSL error pages.

    I have Google DNS setup as some forwarders and use their IPs as a gauge for WAN connectivity, as it is easy to remember their IPs. I started a ping -t to 8.8.8.8, 8.8.4.4 and 4.2.2.2 and normally, I will get a 4ms average on all 3. Today, I am getting 23-25 on 8.8.8.8 and 8.8.4.4 with several request timed outs sprinkled in (at the same time as one another). 4.2.2.2 is very stable and averaging 4ms.

    I can't seem to find much info on down detector. It seems that there are some external network issues, somewhere. I will be calling my ISP, but wanted to see if anyone else was having issues also.

    Edit: I am in Southern California

    Have you tried to use 1.1.1.1 from CloudFlare?

    Thanks, I am pinging now and getting 60+ ms.



  • @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @dbeato said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    Yesterday and today I have had super slow loading on the Office 365 admin portal. Today, I have seen Outlook throw a security cert warning, twice, and some websites are also showing SSL error pages.

    I have Google DNS setup as some forwarders and use their IPs as a gauge for WAN connectivity, as it is easy to remember their IPs. I started a ping -t to 8.8.8.8, 8.8.4.4 and 4.2.2.2 and normally, I will get a 4ms average on all 3. Today, I am getting 23-25 on 8.8.8.8 and 8.8.4.4 with several request timed outs sprinkled in (at the same time as one another). 4.2.2.2 is very stable and averaging 4ms.

    I can't seem to find much info on down detector. It seems that there are some external network issues, somewhere. I will be calling my ISP, but wanted to see if anyone else was having issues also.

    Edit: I am in Southern California

    Have you tried to use 1.1.1.1 from CloudFlare?

    Thanks, I am pinging now and getting 60+ ms.

    This is what I see
    0_1527704018412_2018-05-30_1413.png



  • @dbeato I am now getting an average of 4ms on 1.1.1.1. Still high 20s for Google DNS.



  • @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    m now getting an average of 4ms on 1.1.1.1. Still high 20s for Google DNS.

    Mine is the same, and I have a 500 over 500 Pipe (Which doesn't matter)
    0_1527704229574_2018-05-30_1417.png



  • @dbeato I wonder if that is average for you (historically). I am just commenting on the response times, as that is what I have seen and it is quite a bit different, but only seems to affect certain parts of the internet.



  • @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @dbeato said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    Yesterday and today I have had super slow loading on the Office 365 admin portal. Today, I have seen Outlook throw a security cert warning, twice, and some websites are also showing SSL error pages.

    I have Google DNS setup as some forwarders and use their IPs as a gauge for WAN connectivity, as it is easy to remember their IPs. I started a ping -t to 8.8.8.8, 8.8.4.4 and 4.2.2.2 and normally, I will get a 4ms average on all 3. Today, I am getting 23-25 on 8.8.8.8 and 8.8.4.4 with several request timed outs sprinkled in (at the same time as one another). 4.2.2.2 is very stable and averaging 4ms.

    I can't seem to find much info on down detector. It seems that there are some external network issues, somewhere. I will be calling my ISP, but wanted to see if anyone else was having issues also.

    Edit: I am in Southern California

    Have you tried to use 1.1.1.1 from CloudFlare?

    Thanks, I am pinging now and getting 60+ ms.

    Under 2ms.

    0_1527704721190_Screenshot from 2018-05-30 13-25-10.png



  • @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @dbeato I am now getting an average of 4ms on 1.1.1.1. Still high 20s for Google DNS.

    Google DNS is a lot higher for me, too.

    0_1527704761924_Screenshot from 2018-05-30 13-25-45.png



  • @scottalanmiller said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @wrx7m said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    @dbeato I am now getting an average of 4ms on 1.1.1.1. Still high 20s for Google DNS.

    Google DNS is a lot higher for me, too.

    0_1527704761924_Screenshot from 2018-05-30 13-25-45.png

    8 is a lot higher than <2, but nice compared to 27-28 and time outs. 😐



  • @wrx7m yeah, very different.



  • Looks like it has resolved on its own. 3ms and 4ms for all IPs mentioned above.



  • For future reference, doing a traceroute and noting what the typical path is for your traffic can help you when it slows down. Then you can rerun the trace and see if the path is different. If a node goes down or has issues you may be rerouted on the larger internet. This doesn't work as well as it did in the past as we move into virtualized networks and things appear and disappear on demand, but it may work for you. I would usually choose a target logically closer than a public DNS.



  • @kelly said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

    For future reference, doing a traceroute and noting what the typical path is for your traffic can help you when it slows down. Then you can rerun the trace and see if the path is different. If a node goes down or has issues you may be rerouted on the larger internet. This doesn't work as well as it did in the past as we move into virtualized networks and things appear and disappear on demand, but it may work for you. I would usually choose a target logically closer than a public DNS.

    Yeah, I did a tracert to see if there was any obvious issue at the various hops, but it came back with reasonable results at first.