185.228.169.9 Request timed out.

Forums › General › Open Discussion › 185.228.169.9 Request timed out.

  • BALTAGY
    May 27, 2020 at 8:40 pm

    Hi,

    Past days 185.228.169.9 ping would give 190ms while 185.228.168.9 is about 50ms

    Now 185.228.169.9 gives Request timed out.

    This happen in Egypt

    Thanks

    Daniel Cid
    May 28, 2020 at 4:35 pm

    Sorry about that. Mind running a traceroute for us?

    traceroute 185.228.169.9
    traceroute 185.228.169.10

    And whats your current ISP?

    BALTAGY
    May 28, 2020 at 5:44 pm

    Tracing route to security-filter-dns2.cleanbrowsing.org [185.228.169.9]
    over a maximum of 30 hops:

    1 3 ms <1 ms <1 ms 192.168.1.1
    2 5 ms 4 ms 5 ms host-41.236.99.193.tedata.net [41.236.99.193]
    3 6 ms 5 ms 5 ms 10.38.83.221
    4 5 ms 5 ms 5 ms 10.38.83.222
    5 8 ms 8 ms 7 ms 10.38.172.85
    6 8 ms 8 ms 8 ms 10.38.89.185
    7 10 ms 11 ms 10 ms 10.36.34.226
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.

    Tracing route to security-filter-dns.cleanbrowsing.org [185.228.168.9]
    over a maximum of 30 hops:

    1 <1 ms 1 ms <1 ms 192.168.1.1
    2 5 ms 5 ms 5 ms host-41.236.99.193.tedata.net [41.236.99.193]
    3 10 ms 5 ms 6 ms 10.38.83.221
    4 5 ms 5 ms 5 ms 10.38.83.222
    5 8 ms 8 ms 7 ms 10.38.172.85
    6 7 ms 7 ms 7 ms 10.37.98.49
    7 10 ms 14 ms 10 ms 10.38.32.213
    8 65 ms 66 ms 73 ms ams-ix.r1.gsa.nl.as43350.com [80.249.210.175]
    9 65 ms 145 ms 72 ms 185.107.116.6
    10 * * * Request timed out.
    11 65 ms 65 ms 65 ms security-filter-dns.cleanbrowsing.org [185.228.168.9]

    Trace complete.

    My ISP is “We” but i did run a VPN to check if it’s ISP problem and same problem with VPN

    Daniel Cid
    June 2, 2020 at 2:09 am

    Really weird that according to your traceroute it is not even leaving your network. I wonder if your ISP has it blocked? :/

    If you can contact them , it would be great. In the mean time it might be better to only use our primary DNS.

    BALTAGY
    June 2, 2020 at 11:52 am

    I just tested from another ISP “Vodafone” and same problem

    BALTAGY
    June 4, 2020 at 10:33 am

    It worked today but the ping is high

    Tracing route to security-filter-dns2.cleanbrowsing.org [185.228.169.9]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 5 ms 6 ms 5 ms host-41.236.99.193.tedata.net [41.236.99.193]
    3 5 ms 5 ms 5 ms 10.38.83.217
    4 7 ms 5 ms 5 ms 10.38.83.218
    5 12 ms 11 ms 12 ms 10.36.34.237
    6 10 ms 10 ms 10 ms 10.38.207.122
    7 10 ms 10 ms 10 ms 10.37.85.101
    8 * * * Request timed out.
    9 63 ms 62 ms 79 ms 100ge16-1.core1.lon2.he.net [72.52.92.213]
    10 134 ms 134 ms 134 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166]
    11 149 ms 148 ms 148 ms 100ge9-1.core2.chi1.he.net [184.105.223.161]
    12 167 ms 167 ms 166 ms 100ge8-2.core1.mci3.he.net [184.105.222.77]
    13 172 ms 172 ms 172 ms 100ge12-1.core1.den1.he.net [184.105.64.49]
    14 183 ms 183 ms 183 ms 100ge11-2.core1.slc1.he.net [72.52.92.42]
    15 184 ms 185 ms 184 ms webnx-inc.10gigabitethernet1-1-9.switch1.slc1.he.net [64.62.243.74]
    16 181 ms 181 ms 181 ms 104-237-48-183.static.webnx.com [104.237.48.183]
    17 183 ms 183 ms 183 ms security-filter-dns2.cleanbrowsing.org [185.228.169.9]