Quantcast
Channel: CenturyLink forum - dslreports.com
Viewing all articles
Browse latest Browse all 4862

Unable to reach amazon.com , irisbylows alarm and others

$
0
0
All of a sudden yesterday i started being unable to load amazon.com (it would only lload a bit of text and nothing more) and my alarm (iris by lows) couldn't reach its server. I had been using CL DNS. First thing i did was to change DNS to something else which made amazon.com load but not my alarm or some other sites. Today the problem persists but now changing DNS does nothing. However i CAN get to amazon again but my alarm still doesnt work. This is a major problem. Doing traceroutes from multiple systems keeps stopping at the same spot: C:\Users\lisst>tracert www.irisbylowes.com Tracing route to irisbylowes.com [13.77.110.211]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms USG-USA [192.168.1.1] 2 6 ms 3 ms 4 ms 75-163-0-254.lsv2.qwest.net [75.163.0.254] 3 3 ms 3 ms 3 ms lsv2-agw1.inet.qwest.net [75.160.224.1] 4 9 ms 9 ms 8 ms phn4-edge-01.inet.qwest.net [67.14.135.30] 5 10 ms 10 ms 10 ms 65.156.60.218 6 10 ms 10 ms 9 ms ae0-0.phx01-96cbe-1b.ntwk.msn.net [104.44.226.229] 7 34 ms 43 ms 34 ms ae2-0.dal-96cbe-1b.ntwk.msn.net [104.44.227.71] 8 66 ms 67 ms 65 ms be-72-0.ibr02.dfw05.ntwk.msn.net [104.44.8.130] 9 64 ms 65 ms 65 ms be-5-0.ibr03.atb.ntwk.msn.net [104.44.4.13] 10 66 ms 64 ms 64 ms be-2-0.ibr02.atb.ntwk.msn.net [104.44.4.40] 11 66 ms 65 ms 65 ms be-6-0.ibr01.cnr01.bn6.ntwk.msn.net [104.44.4.48] 12 63 ms 63 ms 63 ms ae103-0.icr04.bn6.ntwk.msn.net [104.44.10.8] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. When i do a site that DOES work it goes a different way: C:\Users\lisst>tracert www.dslreports.com Tracing route to www.dslreports.com [64.91.255.98]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms USG-USA [192.168.1.1] 2 3 ms 3 ms 3 ms 75-163-0-254.lsv2.qwest.net [75.163.0.254] 3 3 ms 3 ms 3 ms lsv2-agw1.inet.qwest.net [75.160.224.1] 4 3 ms 3 ms 3 ms 75-163-31-254.lsv2.qwest.net [75.163.31.254] 5 * * * Request timed out. 6 46 ms 46 ms 46 ms 4-15-84-142.liquidweb.com [4.15.84.142] 7 52 ms 52 ms 52 ms lw-dc3-core1.rtr.liquidweb.com [69.167.128.26] 8 52 ms 53 ms 53 ms lw-dc3-dist16-po6.rtr.liquidweb.com [69.167.128.95] 9 52 ms 52 ms 51 ms www.dslreports.com [64.91.255.98] Trace complete. or C:\Users\lisst>tracert xs4all.nl Tracing route to xs4all.nl [194.109.6.93]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms USG-USA [192.168.1.1] 2 4 ms 4 ms 3 ms 75-163-0-254.lsv2.qwest.net [75.163.0.254] 3 3 ms 3 ms 3 ms lsv2-agw1.inet.qwest.net [75.160.224.1] 4 70 ms 58 ms 58 ms jfk-brdr-04.inet.qwest.net [67.14.5.26] 5 58 ms 58 ms 58 ms nyk-s1-rou-1021.US.eurorings.net [134.222.249.237] 6 146 ms 155 ms 145 ms rt2-rou-1022.NL.eurorings.net [134.222.48.2] 7 145 ms 144 ms 144 ms asd2-rou-1043.NL.eurorings.net [134.222.48.210] 8 147 ms 147 ms 148 ms 134.222.93.145 9 143 ms 143 ms 144 ms xs4all.nl [194.109.6.93] Trace complete. Is there anything *I* can do or am I going to have to slog up the CS mountain to find someone who isn't an idiot to help me :P

Viewing all articles
Browse latest Browse all 4862

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>