@TW Staff - Web connection to Talk Tennis being blocked intermittently (for weeks/months at a time).

Trip

Hall of Fame
@TW Staff - Over the course of the last 12 to 18 months, my attempts to browse Talk Tennis via multiple different devices from my residential Spectrum Cable IP have been getting blocked, seemingly by your webhost, for intermittent periods of time, that seem to come and go in few-week to few-month long windows, with no rhyme or reason as to when they start/stop, with the flip-flop in behavior occurring probably three to four times in total now, since I first noticed the behavior occurring.

During this time period, I've had no other issues accessing any other websites (and I've tested hundreds, if not thousands) from any of my few dozen devices, all with varying OS's and browsers. Talk Tennis has quite literally been the only one with which I've had issues. I've been able to get around the "block" by using a VPN, but that's been a bit annoying to have to use just for Talk Tennis alone, as I'm sure you can imagine.

For your own troubleshooting, here is a traceroute performed today from my residential cable IP to Talk Tennis (hosted at KnownHost, it would appear):

Code:
Tracing route to tt.tennis-warehouse.com [170.249.216.147]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  10.10.10.1
  2    24 ms    11 ms    10 ms  142-254-218-129.inf.spectrum.com [142.254.218.129]
  3    18 ms    65 ms    19 ms  lag-59.hcr01rochnyei.netops.charter.com [24.58.233.113]
  4    14 ms    15 ms    12 ms  lag-63.mcr11rochnyei.netops.charter.com [24.58.46.99]
  5    15 ms    10 ms    10 ms  lag-28.rcr01rochnyei.netops.charter.com [24.58.32.74]
  6    41 ms     *        *     lag-25.chcgildt87w-bcr00.netops.charter.com [66.109.6.116]
  7    26 ms    24 ms    25 ms  lag-0.pr2.chi10.netops.charter.com [66.109.5.225]
  8    27 ms    27 ms    26 ms  eqix.cr2.chi1.unitasglobal.net [208.115.137.64]
  9    26 ms    26 ms    24 ms  ae10.cr4.chi1.us.unitasglobal.net [50.115.90.136]
 10    48 ms    46 ms    45 ms  ae0-31.cr2.atl1.us.unitasglobal.net [50.115.90.127]
 11    45 ms    50 ms    48 ms  inap.cust.cr2.atl1.us.unitasglobal.net [156.146.103.234]
 12    44 ms    46 ms    46 ms  border1.ae1-bbnet1.acs.us.unitasglobal.net [64.94.0.4]
 13    47 ms    46 ms    46 ms  knownhost-3.satedge1.acs.us.unitasglobal.net [64.94.2.46]
 14    47 ms    47 ms    47 ms  64.74.203.42
 15    46 ms    46 ms    45 ms  acs-r2c10-cr4.privatesystems.net [64.74.203.244]
 16    49 ms    45 ms    46 ms  64.74.203.211
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.

Perhaps you can pass this up the chain of support with whomever handles your hosting (XenForo, KnownHost or whomever). If it would help, I'm happy to engage with anyone at TW or elsewhere.

Thank you in advance for your help,
Trip
 
Last edited:

McLovin

Legend
@TW Staff - Over the course of the last 12 to 18 months, my attempts to browse Talk Tennis via multiple different devices from my residential Spectrum Cable IP have been getting blocked, seemingly by your webhost, for intermittent periods of time, that seem to come and go in few-week to few-month long windows, with no rhyme or reason as to when they start/stop, with the flip-flop in behavior occurring probably three to four times in total now, since I first noticed the behavior occurring.

During this time period, I've had no other issues accessing any other websites (and I've tested hundreds, if not thousands) from any of my few dozen devices, all with varying OS's and browsers. Talk Tennis has quite literally been the only one with which I've had issues. I've been able to get around the "block" by using a VPN, but that's been a bit annoying to have to use just for Talk Tennis alone, as I'm sure you can imagine.

For your own troubleshooting, here is a traceroute performed today from my residential cable IP to Talk Tennis (hosted at KnownHost, it would appear):

Code:
Tracing route to tt.tennis-warehouse.com [170.249.216.147]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  10.10.10.1
  2    24 ms    11 ms    10 ms  142-254-218-129.inf.spectrum.com [142.254.218.129]
  3    18 ms    65 ms    19 ms  lag-59.hcr01rochnyei.netops.charter.com [24.58.233.113]
  4    14 ms    15 ms    12 ms  lag-63.mcr11rochnyei.netops.charter.com [24.58.46.99]
  5    15 ms    10 ms    10 ms  lag-28.rcr01rochnyei.netops.charter.com [24.58.32.74]
  6    41 ms     *        *     lag-25.chcgildt87w-bcr00.netops.charter.com [66.109.6.116]
  7    26 ms    24 ms    25 ms  lag-0.pr2.chi10.netops.charter.com [66.109.5.225]
  8    27 ms    27 ms    26 ms  eqix.cr2.chi1.unitasglobal.net [208.115.137.64]
  9    26 ms    26 ms    24 ms  ae10.cr4.chi1.us.unitasglobal.net [50.115.90.136]
 10    48 ms    46 ms    45 ms  ae0-31.cr2.atl1.us.unitasglobal.net [50.115.90.127]
 11    45 ms    50 ms    48 ms  inap.cust.cr2.atl1.us.unitasglobal.net [156.146.103.234]
 12    44 ms    46 ms    46 ms  border1.ae1-bbnet1.acs.us.unitasglobal.net [64.94.0.4]
 13    47 ms    46 ms    46 ms  knownhost-3.satedge1.acs.us.unitasglobal.net [64.94.2.46]
 14    47 ms    47 ms    47 ms  64.74.203.42
 15    46 ms    46 ms    45 ms  acs-r2c10-cr4.privatesystems.net [64.74.203.244]
 16    49 ms    45 ms    46 ms  64.74.203.211
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.

Perhaps you can pass this up the chain of support with whomever handles your hosting (XenForo, KnownHost or whomever). If it would help, I'm happy to engage with anyone at TW or elsewhere.

Thank you in advance for your help,
Trip
Happened to me a couple of years ago. See https://tt.tennis-warehouse.com/ind...ck-my-account-ip-please.732836/#post-16671711
 

mikeler

Moderator
Like @McLovin guessed, the IP on line 2 of what you provided is on the IP blacklist. I recommend following his instructions above and then please report back.
 
Top