I can't open https://cp.winhost.com/

Discussion in 'General troubleshooting' started by dagarint, Feb 22, 2011.

  1. Last edited by a moderator: Oct 14, 2015
  2. Ray

    Ray

    Last edited by a moderator: Oct 14, 2015
  3. Dear Ray,



    Pinging cp.Winhost.com [216.52.229.21] with 32 bytes of data:

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=193ms TTL=40

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=325ms TTL=40

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=379ms TTL=40

    Reply from 216.52.229.21: bytes=32 time=190ms TTL=40

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=190ms TTL=40

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=425ms TTL=40

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=191ms TTL=40

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=189ms TTL=40

    Reply from 216.52.229.21: bytes=32 time=243ms TTL=40

    Request timed out.

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=192ms TTL=40

    Request timed out.

    Request timed out.

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=191ms TTL=40

    Reply from 216.52.229.21: bytes=32 time=194ms TTL=40

    Reply from 216.52.229.21: bytes=32 time=193ms TTL=40

    Reply from 216.52.229.21: bytes=32 time=190ms TTL=40

    Request timed out.

    Reply from 216.52.229.21: bytes=32 time=245ms TTL=40

    Request timed out.




    ----------------------------

    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\Administrator>tracert cp.Winhost.com

    Tracing route to cp.Winhost.com [216.52.229.21]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 11 ms 12 ms 11 ms 89-212-0-1.gw.t-2.net [89.212.0.1]
    3 11 ms 12 ms 11 ms 84-255-210-177.core.t-2.net [84.255.210.177]
    4 12 ms 12 ms 12 ms 84-255-250-1.core.t-2.net [84.255.250.1]
    5 14 ms 13 ms 13 ms 84-255-250-46.core.t-2.net [84.255.250.46]
    6 16 ms 17 ms 17 ms win-b2-link.telia.net [213.248.104.157]
    7 18 ms 18 ms 51 ms win-bb2-link.telia.net [80.91.246.198]
    8 30 ms 30 ms 30 ms ffm-bb2-link.telia.net [80.91.246.140]
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 40 ms 39 ms * cr2-TE-0-3-0-0.frankfurtft3.savvis.net [204.70.2
    06.157]
    12 186 ms 186 ms 185 ms cr1-bundle-pos1.losangeles.savvis.net [204.70.19
    7.26]
    13 * 187 ms 188 ms hr2-te-1-0-0.elsegundola1.savvis.net [204.70.203
    .89]
    14 185 ms * * hr1-te-1-0-1.elsegundola1.savvis.net [204.70.203
    .69]
    15 * 189 ms * hr2-te-1-0-0.irvine2oc2.savvis.net [204.70.204.1
    93]
    16 190 ms * * hr1-te-1-0-1.irvine2oc2.savvis.net [204.70.204.1
    65]
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 190 ms 190 ms 192 ms 96-31-33-227.hostcollective.com [96.31.33.227]
    20 * 189 ms * cp.Winhost.com [216.52.229.21]
    21 * * * Request timed out.
    22
     
    Last edited by a moderator: Oct 14, 2015
  4. Ray

    Ray

    It looks like there maybe some issue with your ISP's upstream provider.

    8 30 ms 30 ms 30 ms ffm-bb2-link.telia.net [80.91.246.140]
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 40 ms 39 ms * cr2-TE-0-3-0-0.frankfurtft3.savvis.net [204.70.206.157]

    Have you contacted your ISP and verify if their backbone maybe having some issues?
     
  5. Dear Ray,
    thank you for your response.
    The problem was solved by ISP.
    Tomaž
     

Share This Page