Visitor

 • 

6 Messages

Wednesday, August 6th, 2025

cant' reach web site

... but can on cell or when connected to a VPN or from an EC2 instance. The site (coffeehouse-talker.net) resolves fine with DNS to 82.221.136.1, but I can't reach it from my home network:

traceroute 82.221.136.1
traceroute to 82.221.136.1 (82.221.136.1), 30 hops max, 60 byte packets
 1  router.Bywater.local (192.168.1.1)  0.298 ms  0.309 ms  0.344 ms
 2  10.61.75.66 (10.61.75.66)  9.067 ms 10.61.75.67 (10.61.75.67)  8.963 ms  8.977 ms
 3  po-313-327-rur201.vancouver.wa.bverton.comcast.net (68.87.217.173)  8.906 ms  8.953 ms po-313-328-rur202.vancouver.wa.bverton.comcast.net (162.151.213.205)  8.883 ms
 4  po-200-xar02.vancouver.wa.bverton.comcast.net (96.216.158.221)  9.013 ms  9.039 ms po-200-xar01.vancouver.wa.bverton.comcast.net (96.216.159.21)  8.936 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *

My hosting provider (the site is my personal web site) swears they're not applying any filtering. I filed a report at https://spa.xfinity.com/report, and they say  "that there is no Advanced Security block related to the reported website."

This looks to me like a routing issue in Comcast's network, but of course there's no way to reach tech support. I've seen a number of other posts in this vein; has anyone figured it out?

Oldest First
Selected Oldest First

Gold Problem Solver

 • 

26.6K Messages

20 days ago

... they say  "that there is no Advanced Security block related to the reported website ...

My trace is similar to yours: it never leaves the Comcast network, and it dies not far from home. This is the signature of a Comcast IP block:

C>tracert -4 coffeehouse-talker.net

Tracing route to coffeehouse-talker.net [82.221.136.1] over a maximum of 30 hops:

  1      2 ms      1 ms      2 ms  router1 [192.168.1.1]
  2    11 ms      9 ms      8 ms  96.120.9.181
  3      9 ms      9 ms    10 ms  po-301-1203-rur01.york.pa.pitt.comcast.net [24.124.216.181]
  4    10 ms    10 ms    10 ms  be-87-rar01.lowerpaxton.pa.pitt.comcast.net [96.110.25.9]
5-30     *             *            *     Request timed out.

You might try giving Customer Security Assurance a call for this: https://spa.xfinity.com/contact-us 

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

(edited)

Visitor

 • 

6 Messages

Gave 'em a call, worked-out about the way one would expect.

Official Employee

 • 

1.2K Messages

Good evening @user_rhthgg. Can you provide some more details about your call to our security team? 

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 a reply as the Accepted Answer.tick

Visitor

 • 

6 Messages

Well, this topic has most of the information. I had a site: coffeehouse-talker.net. Your DNS servers correctly resolved it to 82.221.136.1, but I was unable to actually reach that IP address from my home network. I could reach it when connected to a VPN. I could reach it from an AWS EC2 instance I spun up for testing purposes. A world-wide [ping test](https://www.host-tracker.com/en/ic/2/782d1ccf-f494-410a-932f-522d22e09b5e) showed no problems reaching it. A [blacklist check](https://whatismyipaddress.com/blacklist-check) turns up nothing.

This strongly suggested a problem with my home network. My hosting provider swore that they were not applying any filtering on their end. I filed a report at https://spa.xfinity.com/report, and you told me that "there is no Advanced Security block related to the reported website."

And still, as you can see from the traceroutes above & below, attempts to reach that IP die inside your network.

Your website offers no way to file a request for this kind of tech support. Your call center service reps aren't familiar with this sort of technical minutae.

Happy to provide more details if you're interested. In the meantime I've moved hosting providers.

Official Employee

 • 

1.8K Messages

@user_rhthgg Thank you for providing some details from your call. You mentioned that you moved hosting providers, has that helped any?

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 a reply as the Accepted Answer.tick

Visitor

 • 

6 Messages

Yes, I moved to AWS Lightsail & it's fine.

Expert

 • 

112.8K Messages

20 days ago

@user_rhthgg @BruceW 

FWIW, I am on a different ISP's network and I'm able to browse to the site, and my traceroute completes to the destination server;

Tracing route to coffeehouse-talker.net [82.221.136.1]
over a maximum of 30 hops:

  1     6 ms     3 ms     3 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     8 ms     9 ms  67.59.254.101
  4    17 ms    15 ms    12 ms  67.59.254.244
  5    16 ms    18 ms    14 ms  63.142.20.4
  6    14 ms    14 ms    13 ms  64.15.1.147
  7    15 ms    13 ms    11 ms  ae88.edge2.NewYork6.Level3.net [4.30.181.89]
  8    14 ms    13 ms    12 ms  ae8.cr14-nyc3.ip4.gtt.net [209.120.131.189]
  9    16 ms    15 ms    13 ms  ae7.cr1-nyc2.ip4.gtt.net [89.149.129.218]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   209 ms   102 ms   101 ms  212.221.99.186
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   211 ms   201 ms   203 ms  82.221.168.229
 16     *        *        *     Request timed out.
 17   120 ms   212 ms   199 ms  lettir.orangewebsite.com [82.221.136.1]

Trace complete.

Good luck with it !

forum icon

New to the Community?

Start Here