I can't access my domains! PLEASE HELP!

Discussion in 'Linux VPS/Dedicated - General' started by daboolz, Mar 12, 2007.

  1. daboolz

    daboolz New Member

    I don't know if I'm the only one experiencing this, but I cannot access all the domains in my account since at least 10 hours ago.

    I can't even open http://support.knownhost.com so I cannot submit a help ticket.

    I can open all other websites, just my domains hosted on knownhost.

    I've attached a tracert report. THIS IS URGENT!!

    I cannot access all my usual emails, so you can contact me through [email protected].
     

    Attached Files:

  2. KH-Paul

    KH-Paul CTO Staff Member

    We're not experiencing any connectivity problems at this time. It appears to be a problem with routing somewhere between PT Telekomunikasi Indonesia and Level3. Here is a reverse traceroute to IP in second hop from you:

    Code:
    # traceroute 125.161.198.1
    traceroute to 125.161.198.1 (125.161.198.1), 30 hops max, 38 byte packets
     1  vz04-tx (65.99.235.204)  0.105 ms  0.034 ms  0.028 ms
     2  206.123.64.37 (206.123.64.37)  0.276 ms  0.239 ms  0.287 ms
     3  border4.g3-2.colo4dallas-3.ext1.dal.pnap.net (216.52.189.9)  0.707 ms  1.049 ms  0.866 ms
     4  core2.tge5-2-bbnet2.ext1.dal.pnap.net (216.52.191.97)  1.069 ms  1.146 ms  1.029 ms
     5  unknown.Level3.net (209.246.152.245)  1.148 ms  1.131 ms  1.105 ms
     6  ae-2-56.bbr2.Dallas1.Level3.net (4.68.122.161)  1.255 ms ae-2-52.bbr2.Dallas1.Level3.net (4.68.122.33)  1.681 ms ae-2-54.bbr2.Dallas1.Level3.net (4.68.122.97)  1.035 ms
     7  ae-0-0.bbr1.LosAngeles1.Level3.net (64.159.1.125)  32.863 ms  32.773 ms  33.913 ms
     8  ge-4-0.ipcolo1.LosAngeles1.Level3.net (4.68.102.10)  33.260 ms  32.749 ms ge-9-0.ipcolo1.LosAngeles1.Level3.net (4.68.102.42)  33.923 ms
     9  204.8.22.105 (204.8.22.105)  33.018 ms  32.827 ms  33.006 ms
    10  219.93.151.201 (219.93.151.201)  190.772 ms  190.704 ms  189.585 ms
    11  219.94.9.18 (219.94.9.18)  194.283 ms  193.639 ms  194.788 ms
    12  202.153.90.138 (202.153.90.138)  256.144 ms  257.052 ms  256.866 ms
    13  61.94.30.237 (61.94.30.237)  256.886 ms  258.223 ms  257.375 ms
    14  * * *
    15  61.94.15.10 (61.94.15.10)  254.937 ms  269.695 ms  269.936 ms
    16  61.94.0.10 (61.94.0.10)  269.760 ms  269.923 ms  270.248 ms
    17  61.94.0.86 (61.94.0.86)  270.630 ms  271.761 ms  270.792 ms
    18  61.94.0.254 (61.94.0.254)  269.741 ms  269.492 ms  269.688 ms
         MPLS Label=1197 CoS=5 TTL=1 S=0
         MPLS Label=1091 CoS=0 TTL=5 S=0
    19  65.subnet125-160-0.speedy.telkom.net.id (125.160.0.65)  263.814 ms  263.807 ms  263.944 ms
         MPLS Label=1091 CoS=5 TTL=1 S=0
    20  66.subnet125-160-0.speedy.telkom.net.id (125.160.0.66)  273.753 ms  275.836 ms  282.158 ms
    
    Your VPS itself is up and running and is reachable from outside, quick test:
    http://www.dnsstuff.com/tools/ping.ch?ip=65.99.238.89

    Regards,
    Paul
     
  3. daboolz

    daboolz New Member

    Hi Paul,

    Please advise how do I fix this problem? From looking at the tracert, it looks like the server stops responding by the time it arrived at colo4dallas
     
  4. KH-Paul

    KH-Paul CTO Staff Member

    Try to submit a ticket to your ISP - they may have network filters or anything like that in place. Ask them to check if they have any filters and/or specific routing rules for the 65.99.238.0/24 network.

    Regards,
    Paul
     
  5. daboolz

    daboolz New Member

    OK thanks, I just checked access from other ISP, looks like it's working... phew.... Thanks...

    I'll take this up with my ISP.
     
  6. fmike

    fmike New Member

    Could the Knownhost Admin change the privilege to post in "Network and Hardware status" section so that only the staff are able to post new threads here?

    FYI, I'm subscribed to this section and I don't wish to receive notification from random members seeking for support.
     
  7. KH-Paul

    KH-Paul CTO Staff Member

    Good point. Done.

    Thread was also moved to "Linux VPS - General".

    Regards,
    Paul
     

Share This Page