1. Advertising
    y u no do it?

    Advertising (learn more)

    Advertise virtually anything here, with CPM banner ads, CPM email ads and CPC contextual links. You can target relevant areas of the site and show ads based on geographical location of the user if you wish.

    Starts at just $1 per CPM or $0.10 per CPC.

I am having problem with my IP. can't ping or trace... please check from your side..

Discussion in 'Outages' started by solidstate, Oct 7, 2009.

0
  1. #1
    Hi guys,

    could you guys please ping / tracert my site ip from your side. i can't ping/tracert from my end. it happened like 50 mins ago and still not accessable.

    I tried to ping/tracert from Netherlands.

    IP: 208.53.136.42

    let me know from which country you tried to ping/tracert.
     
    solidstate, Oct 7, 2009 IP
  2. DashingHost

    DashingHost Peon

    Messages:
    6
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    I am close to Los Angeles, California and was able to ping it fine. Here are the results:

    Pinging 208.53.136.42 with 32 bytes of data:
    Reply from 208.53.136.42: bytes=32 time=73ms TTL=56
    Reply from 208.53.136.42: bytes=32 time=71ms TTL=56
    Reply from 208.53.136.42: bytes=32 time=70ms TTL=56
    Reply from 208.53.136.42: bytes=32 time=72ms TTL=56

    Ping statistics for 208.53.136.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 73ms, Average = 71ms
     
    DashingHost, Oct 7, 2009 IP
  3. Natashalein

    Natashalein Peon

    Messages:
    83
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Pinging 208.53.136.42 with 32 bytes of data:
    Reply from 208.53.136.42: Bytes=32 time=173ms TTL=57
    Reply from 208.53.136.42: Bytes=32 time=171ms TTL=57
    Reply from 208.53.136.42: Bytes=32 time=172ms TTL=57
    Reply from 208.53.136.42: Bytes=32 time=173ms TTL=57

    Ping statistics for 208.53.136.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 171ms, Maximum = 173ms, Average = 172ms

    Pinged from germany.
     
    Natashalein, Oct 18, 2009 IP
  4. coldgansta

    coldgansta Guest

    Messages:
    1,614
    Likes Received:
    29
    Best Answers:
    0
    Trophy Points:
    0
    #4
    Pinged from uk

    Pinging 208.53.136.42 with 32 bytes of data:
    Reply from 208.53.136.42: bytes=32 time=73ms TTL=56
    Reply from 208.53.136.42: bytes=32 time=71ms TTL=56
    Reply from 208.53.136.42: bytes=32 time=70ms TTL=56
    Reply from 208.53.136.42: bytes=32 time=72ms TTL=56

    Ping statistics for 208.53.136.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

    You may be blocked from the server firewall you should check through a proxy:)
     
    coldgansta, Oct 21, 2009 IP
  5. theapparatus

    theapparatus Peon

    Messages:
    2,925
    Likes Received:
    119
    Best Answers:
    0
    Trophy Points:
    0
    #5
    Traceroute looks fine. Actually pretty good if you ask me.

    You didn;t do anything silly like just install a firewall and forget to leave you access, did you?

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

    C:\Users\drmike>tracert 208.53.136.42

    Tracing route to ns1-s7r9.welcomesearchers.com [208.53.136.42]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 10.4.11.1
    2 3 ms 1 ms 1 ms 10.4.10.9
    3 2 ms 4 ms 3 ms 10.200.0.1
    4 2 ms 1 ms 2 ms WIFIWARP [10.0.5.10]
    5 5 ms 3 ms 5 ms 10.0.201.1
    6 3 ms 8 ms 8 ms [You wish]
    7 19 ms 25 ms 19 ms peer-01-ge-0-0-0-1.asbn.twtelecom.net [64.129.24
    9.10]
    8 23 ms 23 ms 25 ms pos-2-5-0-0-cr01.mclean.va.ibone.comcast.net [68
    .86.86.141]
    9 23 ms 26 ms 27 ms pos-0-10-0-0-cr01.newyork.ny.ibone.comcast.net [
    68.86.85.10]
    10 46 ms 46 ms 46 ms pos-2-7-0-0-cr01.chicago.il.ibone.comcast.net [6
    8.86.86.102]
    11 47 ms 46 ms 46 ms pos-0-0-0-0-pe01.350ecermak.il.ibone.comcast.net
    [68.86.86.34]
    12 49 ms 49 ms 49 ms 66.90.127.205 [66.90.127.205]
    13 45 ms 42 ms 48 ms ns1-s7r9.welcomesearchers.com [208.53.136.42]

    Trace complete.
     
    theapparatus, Oct 21, 2009 IP