Forum Discussion

micahdraws's avatar
micahdraws
New Contributor

Unable to access personal website

I have a personal website at www.micahdraws.com. For a while, I haven't had any problem accessing it on my home network. However, I had Cox cable TV service added to my home on 6/30 and I have not been able to access my website since. I know the site is not down because I can access it fine on my phone's 4G (though not when the phone is connected to my home WiFi). 

I first noticed the problem a few days after the cable was installed. I used the modem reset tool on the Cox website and that seemed to fix the issue. However, I have not been able to access my site for about a week now, and resetting the modem/router does not help anymore, even when I reset all devices and restart them in proper order (modem/router, then computer).

I cannot ping my website. When I run tracert, all requests time out after the 5th hop. I have not noticed an issue with any other website.

I believe there is an issue with my modem/router hardware or my home cable connection. Could the use of a cable splitter be causing a problem for just one website? I have been with this web host for about 10 years and I hope I can resolve this without needing to change hosting providers.

If needed, I can provide the IP address for my site. 

Thank you for any help you can provide.

5 Replies

Replies have been turned off for this discussion
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @micahdraws

    Could you try and to a trace route to your site host and post the results?

  • micahdraws's avatar
    micahdraws
    New Contributor

    Here it is

    Tracing route to micahdraws.com [216.120.237.40]
    over a maximum of 30 hops:

    1 5 ms 1 ms 6 ms 192.168.0.1
    2 28 ms 9 ms 11 ms 10.11.168.1
    3 10 ms 15 ms 10 ms 100.127.40.230
    4 136 ms 67 ms 18 ms 172.22.51.92
    5 77 ms 213 ms 210 ms port-channel201.car2.Richmond1.Level3.net [4.26.
    66.25]
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 49 ms 50 ms 43 ms 8.43.14.162
    11 * * * Request timed out.
    12 * * * Request timed out.
    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.

  • AllenP's avatar
    AllenP
    Valued Contributor

    Looks like you are getting out of Cox's network into level3 communications.  It's getting lost withing level3.  When I tried it, I route thru level3 New York, not Richmond and it works.  Maybe get in touch with your hosting service too, they may be able to straighten out the routing.

    Tracing route to micahdraws.com [216.120.237.40]
    over a maximum of 30 hops:

      1     1 ms    <1 ms    <1 ms  READYSHARE [192.168.10.1]
      2     8 ms     8 ms     8 ms  10.4.120.1
      3    12 ms    12 ms    14 ms  ip98-190-33-34.ri.ri.cox.net [98.190.33.34]
      4    14 ms    22 ms    11 ms  ip98-190-33-34.ri.ri.cox.net [98.190.33.34]
      5    18 ms    17 ms    16 ms  nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
      6    18 ms    17 ms    17 ms  lag-22.ear2.NewYork1.Level3.net [4.35.90.1]
      7    19 ms    21 ms    17 ms  4.69.142.113
      8     *        *        *     Request timed out.
      9    29 ms    26 ms    25 ms  8.43.14.162
     10    22 ms    22 ms    23 ms  reseller16.hrwebservices.net [216.120.237.40]

    Trace complete.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @micahdraws

    I would have to agree with AllenP on this. It looks like your host may be using Level 3 as their provider and your traffic is getting lost somewhere within their network. Opening a ticket with your web host would probably be the best way to get this resolved.

  • micahdraws's avatar
    micahdraws
    New Contributor

    Thank you guys. I'll get in contact with my hosting provider and see if they can clear things up.