Wilders Website slow / offline?

Discussion in 'General Topics' started by tVirus, Jan 17, 2012.

Thread Status:
Not open for further replies.
  1. tVirus

    tVirus Registered Member

    Joined:
    Jan 8, 2012
    Posts:
    14
    Location:
    UK
    I am getting a lot of "Error 103" while trying to load this site. Only 1/20 attempts actually loads. Anyone else getting these problems?
     
  2. nikanthpromod

    nikanthpromod Registered Member

    Joined:
    Oct 9, 2009
    Posts:
    1,369
    Location:
    India
  3. funkydude

    funkydude Registered Member

    Joined:
    Apr 5, 2004
    Posts:
    6,655
    No, have you tried the https version to see if it's any different? If it is, it's probably client/ISP related.
     
  4. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    3,444
  5. tVirus

    tVirus Registered Member

    Joined:
    Jan 8, 2012
    Posts:
    14
    Location:
    UK
    Yes, the https is also affected.

    It looks like a routing issue...

    Code:
    traceroute to 66.227.46.190 (66.227.46.190), 30 hops max, 38 byte packets
     1  alan5 (193.62.127.129)  0.921 ms  1.784 ms  0.612 ms
     2  gw-fw (193.63.74.131)  0.387 ms  0.333 ms  0.323 ms
     3  c-pop (193.63.74.226)  1.045 ms  1.423 ms  0.849 ms
     4  193.62.116.18 (193.62.116.18)  1.237 ms  1.204 ms  1.190 ms
     5  so-1-2-0.leed-sbr1.ja.net (146.97.42.169)  2.408 ms  2.390 ms  2.371 ms
     6  as3.lond-sbr1.ja.net (146.97.33.98)  6.744 ms  7.006 ms  6.726 ms
     7  ae13.lond-sbr4.ja.net (146.97.33.134)  121.191 ms  19.330 ms  7.228 ms
     8  ae0.lond-gw-ixp4.ja.net (146.97.35.182)  7.217 ms  7.269 ms  7.247 ms
     9  peer1.ldn1.flagtel.com (195.66.224.146)  7.722 ms  7.430 ms  7.405 ms
    10  so-1-0-0.0.pjr02.ldn001.flagtel.com (85.95.25.9)  7.848 ms  7.873 ms  7.920 ms
    11  so-1-0-0.0.pjr01.nyc007.flagtel.com (85.95.25.2)  86.365 ms  86.378 ms  86.365 ms
    12  62.216.147.186 (62.216.147.186)  86.389 ms  86.350 ms  86.383 ms
    13  209.213.202.42 (209.213.202.42)  86.540 ms  86.590 ms  87.273 ms
    14  so-1-2-0.phl004jp02.yipes.com (209.213.202.2)  88.868 ms  115.046 ms  88.910 ms
    15  ge-1-3-0.phl004jp02.yipes.com (66.54.175.133)  88.807 ms  88.948 ms  88.811 ms
    16  66.227.69.99 (66.227.69.99)  91.179 ms  91.102 ms  90.848 ms
    17  * * *
    18  * * *
    19  * *
    
    Code:
    Pinging wilderssecurity.com [66.227.46.190] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Reply from 66.227.46.190: bytes=32 time=105ms TTL=52
    Reply from 66.227.46.190: bytes=32 time=106ms TTL=52
    
    Ping statistics for 66.227.46.190:
        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 105ms, Maximum = 106ms, Average = 105ms
    
    I've tried a traceroute from Germany and that seems fine.
     
  6. BrandiCandi

    BrandiCandi Guest

    Maybe this is OT, but I just typed in -https://www.wilderssecurity. com and this is what I got:

    wilders.png

    Either way, that is just the epitome of irony.
     
  7. JRViejo

    JRViejo Global Moderator

    Joined:
    Jul 9, 2008
    Posts:
    16,942
    Location:
    U.S.A.
    No irony. You can read about it here: Wilders is now https (ssl)?
     
  8. BrandiCandi

    BrandiCandi Guest

  9. Searching_ _ _

    Searching_ _ _ Registered Member

    Joined:
    Jan 2, 2008
    Posts:
    1,988
    Location:
    iAnywhere
    @ tVirus
    Have you tried Layer Four Traceroute?
     
Thread Status:
Not open for further replies.