Is distro watch down? - Ubuntu

This is a discussion on Is distro watch down? - Ubuntu ; The time is now 2236 ADT and I am trying to reach www.distrowatch.com . I receive the following message: The connection to the server was reset while the page was loading. Is anyone else aware of a problem or is ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: Is distro watch down?

  1. Is distro watch down?

    The time is now 2236 ADT and I am trying to reach www.distrowatch.com.
    I receive the following message:

    The connection to the server was reset while the page was loading.

    Is anyone else aware of a problem or is it on my end? I can reach other
    sites with no problems.

    I receive a similar message with Opera. The above was with Firefox.


    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG and Supernews now on Ubuntu, Vista and XP
    http://www.grc.com/stevegibson.htm

  2. Re: Is distro watch down?

    Pseudo Silk Kimono wrote:
    > The time is now 2236 ADT and I am trying to reach www.distrowatch.com.
    > I receive the following message:


    Initiating server query ...
    Looking up IP address for domain: distrowatch.com
    The IP address for the domain is: 63.208.196.110
    Connecting to the server on standard HTTP port: 80
    [Connected] Requesting the server's default page.
    Error retrieving page from server: 10054


    --
    Mike Easter


  3. Re: Is distro watch down?

    Pseudo Silk Kimono wrote:
    > The time is now 2236 ADT and I am trying to reach www.distrowatch.com.
    > I receive the following message:
    >
    > The connection to the server was reset while the page was loading.
    >
    > Is anyone else aware of a problem or is it on my end? I can reach other
    > sites with no problems.
    >
    > I receive a similar message with Opera. The above was with Firefox.
    >
    >

    Looks like it:

    The connection has timed out
    The server at www.distrowatch.com is taking too long to respond.
    ping distrowatch.com
    PING distrowatch.com (10.0.1.128) 56(84) bytes of data.


    --

    Xubunt6

    "Xubuntu 6 just installed ..."

  4. Re: Is distro watch down?

    xubunt6 :
    > Pseudo Silk Kimono wrote:
    > > The time is now 2236 ADT and I am trying to reach www.distrowatch.com.
    > > I receive the following message:

    >
    > The connection has timed out
    > The server at www.distrowatch.com is taking too long to respond.
    > ping distrowatch.com
    > PING distrowatch.com (10.0.1.128) 56(84) bytes of data.


    (0) heretic /home/keeling_ ping -c 1 distrowatch.com
    PING distrowatch.com (66.180.174.35) 56(84) bytes of data.
    64 bytes from ded135-fbsd-174-35.netsonic.net (66.180.174.35): icmp_seq=1 ttl=53 time=52.9 ms

    --- distrowatch.com ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 52.943/52.943/52.943/0.000 ms


    --
    Any technology distinguishable from magic is insufficiently advanced.
    (*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
    - - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.

  5. Re: Is distro watch down?

    Mike Easter wrote:
    > Pseudo Silk Kimono wrote:
    >> The time is now 2236 ADT and I am trying to reach
    >> www.distrowatch.com. I receive the following message:

    >
    > Initiating server query ...
    > Looking up IP address for domain: distrowatch.com
    > The IP address for the domain is: 63.208.196.110
    > Connecting to the server on standard HTTP port: 80
    > [Connected] Requesting the server's default page.
    > Error retrieving page from server: 10054


    Initiating server query ...
    Looking up IP address for domain: distrowatch.com
    The IP address for the domain is: 66.180.174.35
    Connecting to the server on standard HTTP port: 80
    No response was received from the machine and port at that IP. The
    machine may be offline or the connection port may be stealthed.
    Query complete.

    Ping distrowatch.com (66.180.174.35) ...
    1 Addr:66.180.174.35, RTT: 99ms, TTL: 49

    Reported at digg
    http://digg.com/linux_unix/DistroWat...ve_DDoS_attack

    DistroWatch hit by a massive DDoS attack
    The site won't be updated until the problem is dealt with, but at least
    you can access the existing information. Sorry for the trouble :-(

    Here is a full list of up-to-date DistroWatch mirrors:

    USA: http://distrowatch.serve-you.net/
    Ukraine: http://distrowatch.lafox.net/
    Czech Republic: http://distrowatch.cz/
    Romania: http://dw.rohost.com/
    Austria: http://distrowatch.gds.tuwien.ac.at/

    --
    Mike Easter


  6. Re: Is distro watch down?

    On 2007-09-16, s. keeling wrote:
    > xubunt6 :
    >> Pseudo Silk Kimono wrote:
    >> > The time is now 2236 ADT and I am trying to reach www.distrowatch.com.
    >> > I receive the following message:

    >>
    >> The connection has timed out
    >> The server at www.distrowatch.com is taking too long to respond.
    >> ping distrowatch.com
    >> PING distrowatch.com (10.0.1.128) 56(84) bytes of data.

    >
    > (0) heretic /home/keeling_ ping -c 1 distrowatch.com
    > PING distrowatch.com (66.180.174.35) 56(84) bytes of data.
    > 64 bytes from ded135-fbsd-174-35.netsonic.net (66.180.174.35): icmp_seq=1 ttl=53 time=52.9 ms
    >
    > --- distrowatch.com ping statistics ---
    > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
    > rtt min/avg/max/mdev = 52.943/52.943/52.943/0.000 ms
    >
    >


    Pinging may work, but connecting via a browser times out, at least for
    me.

    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG and Supernews now on Ubuntu, Vista and XP
    http://www.grc.com/stevegibson.htm

  7. Re: Is distro watch down?

    Pseudo Silk Kimono wrote:
    > s. keeling


    >> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
    >> rtt min/avg/max/mdev = 52.943/52.943/52.943/0.000 ms


    > Pinging may work, but connecting via a browser times out, at least for
    > me.


    Pinging is not a very good way to test a website/webserver for several
    reasons, two of the most important of which are:

    -1- echoing an icmp (or udp) ping is not the same thing as 'being
    there' and answering a port 80 tcp; so an IP can echo a ping but not
    have a port 80 visible or a webserver answering it

    -2- having a webserver answering and providing pages is not the same
    thing as getting and echoing pings; so you may be able to get webpages
    from a server you can't get a ping echo from.

    and -3- tracert and traceroute suffer from the same kinds of problems as
    pinging, unless you are using a port 80 traceroute on a webserver which
    is answering port 80 calls.

    www.microsoft.com answers calls on port 80, but it doesn't echo pings or
    tracert calls.

    Steve Gibson's IDServe is a useful tool to use for website and other
    such issues.

    --
    Mike Easter


  8. Re: Is distro watch down?

    Mike Easter wrote:

    > Steve Gibson's IDServe is a useful tool to use for website and other
    > such issues.


    Oops. I forgot where I was. IDServe is a Win app :-/

    --
    Mike Easter

+ Reply to Thread