Community Forum

Unable to reach http://www.windstream.com

CableCo10
New Poster

Unable to reach http://www.windstream.com

Windows 10, Chrome and Mozilla Browser return local error message we cannot find the site & we cannot connect to server. Tuesday Feb 23 8 AM to 10 AM so far.  I have not run into any other unreachable sites.

jav6joev
Bronze Problem Solver

Re: Unable to reach http://www.windstream.com


@CableCo10 wrote:

Windows 10, Chrome and Mozilla Browser return local error message we cannot find the site & we cannot connect to server. Tuesday Feb 23 8 AM to 10 AM so far.  I have not run into any other unreachable sites.


I am able to hit the website fine.

 

Joe V
(not a Comcast employee, just another paying customer)
EG
Expert

Re: Unable to reach http://www.windstream.com

That trace is from your end. Doesn't prove anything global. It's just a reference of your results, like mine also is. Routes are different from different geographic locations. Can you browse to the site ?

 

Be curious to see what does a traceroute from the OP's end looks like.

 

My trace from my end does not complete to the destination either yet I can indeed browse to the site just fine;

 

Tracing route to windstream.com [13.65.89.91]
over a maximum of 30 hops:

1 6 ms 1 ms 1 ms 192.168.1.1
2 12 ms 10 ms 10 ms 96.120.73.93
3 10 ms 11 ms 10 ms 24.124.228.65
4 11 ms 15 ms 10 ms 96.108.9.17
5 12 ms 11 ms 12 ms be33-rar01.plainfield.nj.panjde.comcast.net [68.85.63.25]
6 12 ms 12 ms 13 ms be-98-ar03.plainfield.nj.panjde.comcast.net [68.85.35.37]
7 14 ms 21 ms 13 ms be-31113-cs01.newark.nj.ibone.comcast.net [96.110.42.33]
8 14 ms 13 ms 14 ms be-2103-pe03.newark.nj.ibone.comcast.net [96.110.37.66]
9 16 ms 12 ms 15 ms as36040-3-c.11greatoaks.ca.ibone.comcast.net [75.149.231.102]
10 24 ms 23 ms 14 ms ae25-0.ear01.nyc30.ntwk.msn.net [104.44.239.157]
11 57 ms 52 ms 52 ms be-21-0.ibr02.nyc30.ntwk.msn.net [104.44.20.126]
12 51 ms 51 ms 50 ms 104.44.28.55
13 53 ms 50 ms 52 ms be-2-0.ibr02.bn6.ntwk.msn.net [104.44.19.152]
14 50 ms 55 ms 52 ms be-6-0.ibr02.atl30.ntwk.msn.net [104.44.17.233]
15 50 ms 52 ms 51 ms be-3-0.ibr02.sn1.ntwk.msn.net [104.44.19.115]
16 51 ms 49 ms 49 ms ae122-0.icr02.sn1.ntwk.msn.net [104.44.23.68]
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.

 

In my case, they (the destination server) may just be blocking  / not returning ICMP packet-based ping probes.

 

 



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
CableCo10
New Poster

Re: Unable to reach http://www.windstream.com

Thanks Joe, I will compare your Trace Route with mine to see if I can isolate further.

 

Kelly

CableCo10
New Poster

Re: Unable to reach http://www.windstream.com

Thank you EG, I will look at yours and Joe's traceroute comparing to my results to see if I can further isolate.

EG
Expert

Re: Unable to reach http://www.windstream.com

@jav6joev 

 

Why did you edit stuff out of your post after you saw my response Joe ???



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
CableCo10
New Poster

Re: Unable to reach http://www.windstream.com

I found issue,  I have Mozilla VPN Active, Mozilla  VPN implements WireGuard (GNU licensing). Wireguard is applying the block.  I have notified Wireguard to research.

i.e. my tracert would not launch because the DNS support by Wireguard would not support the tracert launch, the response was internet blocked.

EG
Expert

Re: Unable to reach http://www.windstream.com

Glad you got it figured out !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!