Skip to main content
user_s5xcsr
1st Topic
1st Reply

Visitor

 • 

11 Messages

Monday, August 3rd, 2026 12:42 PM

webserver issues

After going round and round with my ISP for a couple of weeks, we have determined that Comcast has some issues resolving web pages. For example:

https://www.newsletterbroadcast.net/login

This page will not resolve on Comcast, but works fine on Verizon.  Need to open a ticket with Comcast, but there is no way to actually communicate with Comcast if you are a retail customer.  Help!

 

Question

 • 

Updated 

46 minutes ago

41

3

0

Oldest First
Selected Oldest First
XfinitySara

Official Employee

 • 

2.8K Messages

8 hours ago

Hello, @user_s5xcsr! Thank you for creating a post within our community forum to get started. I'm sorry to hear about the trouble you've had, and I'd love to see what we can do to help! To start, let's review what you've tried so far. Does this occur on every browser and even when using incognito mode? Have you cleared cache and cookies to see if that improves your experience at all? Is it every device (laptop, desktop PC, tablet, phone, etc.)?

2

0

user_s5xcsr

Visitor

 • 

11 Messages

Yes. I have been through an extensive troubleshooting exercise with Hostway. The page works fine in Verizon, but not on Xfinity.

Like

Reply

8 hours ago

0

XfinityPeterH

Official Employee

 • 

3K Messages

 

user_s5xcsr I just tested that link on AT&T, TDS, Xfinity along with being on a VPN and all gave the same results as you mentioned which leads me to believe it's not just a Comcast related issue but a website issue. 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

7 hours ago

0

user_s5xcsr

Visitor

 • 

11 Messages

7 hours ago

All I know is that the website checks out OK.  The page works on Verizon 5G. Maybe a FL issue? In any event, I am moving to Starlink next week.

7

0

XfinityPeterH

Official Employee

 • 

3K Messages

 

user_s5xcsr You mentioned "issues resolve web pages" and gave one example. Do you have another page we can test? 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

7 hours ago

0

user_s5xcsr

Visitor

 • 

11 Messages

This is the only page with the issues. It is a big pain point for my firm because this newsletter tool has 20k subscribers. I can only access via Verizon 5G on my hotspot. 

https://www.newsletterbroadcast.net/

C:\Users\chris>tracert www.newsletterbroadcast.net/
Unable to resolve target system name www.newsletterbroadcast.net/.

C:\Users\chris>tracert newsletterbroadcast.net/
Unable to resolve target system name newsletterbroadcast.net/.

C:\Users\chris>tracert https://www.newsletterbroadcast.net/
Unable to resolve target system name https://www.newsletterbroadcast.net/.

>

I have spent hours working with Hostway to resolve this issue. They have indicated that it is a web server problem at Comcast.  I apologize but I really cannot spend anymore time on this issue. I am moving to Starlink next week and I will be minimizing my use of Comcast in future.

Please contact [Edit: "Personal information"]

Thank you for your assistance.

[Edit: "Personal information"]

(edited)

Like

Reply

6 hours ago

0

XfinityPeterH

Official Employee

 • 

3K Messages

 

user_s5xcsr Thank you for the additional information. Based on the testing performed, I'm not seeing evidence that this issue is isolated to Comcast. I tested the site from multiple networks, including AT&T, TDS, Xfinity, and through a VPN, and observed the same behavior.

The error shown in the browser indicates that a connection is being attempted but is being closed, which is different from a Comcast DNS resolution issue. Since the behavior appears across multiple providers, the issue is more likely related to the website, hosting environment, routing, or security configuration rather than a Comcast-specific web server problem.

I understand Hostway has been involved. However, because the issue is reproducible across several unrelated networks, there isn't enough evidence at this time to attribute the problem specifically to the Comcast network. The hosting provider would be in the best position to review server logs, firewall policies, access controls, and connection handling for that domain.

We appreciate the time you've spent troubleshooting this issue and sharing your findings with us. While we certainly understand your frustration, we would be saddened to see you leave. If you do decide to move your services away from Comcast, our team would be happy to help review your account and assist with any disconnect requests. Just let us know how you'd like to proceed, and we'll be glad to help.

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

6 hours ago

0

user_s5xcsr

Visitor

 • 

11 Messages

Rgr on the tracert. Tracing route to newsletterbroadcast.net [216.185.130.32]
over a maximum of 30 hops:

  1     8 ms     8 ms     6 ms  10.0.0.1
  2    25 ms    16 ms    16 ms  10.60.29.66
  3    25 ms    16 ms    15 ms  po-305-327-rur201.bonitasprngs.fl.naples.comcast.net [69.139.170.21]
  4    25 ms    14 ms    15 ms  po-2-rur202.bonitasprngs.fl.naples.comcast.net [68.85.59.234]
  5    23 ms    19 ms    19 ms  po-200-xar02.bonitasprngs.fl.naples.comcast.net [68.85.64.221]
  6    26 ms    16 ms    18 ms  ae-47-ar03.bonitasprngs.fl.naples.comcast.net [68.85.59.217]
  7    36 ms     *       34 ms  be-33913-cs21.nota.fl.ibone.comcast.net [96.110.45.81]
  8    27 ms    18 ms    36 ms  be-2112-pe12.nota.fl.ibone.comcast.net [68.86.92.242]
  9    25 ms    19 ms    17 ms  lag-12.ear3.mia2.sp.lumen.tech [4.68.110.85]
 10    27 ms    26 ms    28 ms  ae5.5.bar1.Tampa1.net.lumen.tech [4.69.148.214]
 11    38 ms    21 ms    20 ms  67.29.167.186
 12    38 ms    27 ms    26 ms  s1-5-9-1.tampa.netnation.net [64.41.127.3]
 13    25 ms    23 ms    24 ms  s1-6-1-1.tampa.netnation.net [64.41.127.14]
 14    27 ms    27 ms    26 ms  216.185.130.32

For whatever reason, I cannot get a stable connection to the page on Xfinity. Works fine on Verizon. I am in Estero, FL, in Wildcat Run so it may be a local issue. But to be honest, neither Xfinity nor Hostway are able to provide an answer and I simply cannot spend anymore time on this issue. I will be on Starlink next week and will downgrade Xfinity to TV only. 

Thank you

Like

Reply

2 hours ago

0

XfinityVictor

Official Employee

 • 

2.4K Messages

 

user_s5xcsr I am sorry, you are looking to move to another provider. Unfortunately we are unable to resolve this concern. As much as we hate doing it, we are happy to set up the disconnect if you need assistance. 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please mark as Best Answer.tick

Like

Reply

1 hour ago

0

BruceW

Gold Problem Solver

 • 

27.6K Messages

3 hours ago

@user_s5xcsr posted: "C:\Users\chris>tracert www.newsletterbroadcast.net/"

That didn't work because tracert doesn't understand the trailing slash. When I ran the same command, with and without the slash, I got this:

C:\Misc>tracert www.newsletterbroadcast.net/  [trailing /]
Unable to resolve target system name www.newsletterbroadcast.net/.

C:\Misc>tracert www.newsletterbroadcast.net  [no trailing /]

Tracing route to www.newsletterbroadcast.net [216.185.130.32] over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  router1 [192.168.1.1]
  2    12 ms     9 ms     9 ms  96.120.9.181
  3     9 ms     9 ms     8 ms  po-301-1203-rur01.york.pa.pitt.comcast.net [24.124.216.181]
  4     9 ms     9 ms     9 ms  po-2-rur02.york.pa.pitt.comcast.net [96.110.24.214]
  5    10 ms     9 ms    12 ms  be-87-rar01.lancaster.pa.pitt.comcast.net [96.110.25.65]
  6    18 ms    18 ms    22 ms  be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
  7     *       20 ms    18 ms  ae-7.bar1.Pittsburgh3.Level3.net [4.68.106.85]
  8    55 ms    55 ms    55 ms  ae5.5.bar1.Tampa1.net.lumen.tech [4.69.148.214]
  9    55 ms    55 ms    55 ms  67.29.167.186
 10    56 ms    55 ms    55 ms  s1-5-8-1.tampa.netnation.net [64.41.127.2]
 11    56 ms    55 ms    55 ms  s1-6-2-1.tampa.netnation.net [64.41.127.15]
 12    58 ms    58 ms    59 ms  216.185.130.32

Trace complete.

Browsing the site works using my Comcast/Xfinity internet service: I get a login page.

(edited)

0

forum icon

New to the Community?

Start Here