From: David Miller <davem@davemloft.net>
To: richard.weinberger@gmail.com
Cc: sfr@canb.auug.org.au, rdunlap@infradead.org,
andrew.donnellan@au1.ibm.com, jeffrey.t.kirsher@intel.com,
jk@ozlabs.org, patchwork@lists.ozlabs.org,
netdev@vger.kernel.org, miquel.raynal@bootlin.com
Subject: Re: ozlabs.org down?
Date: Mon, 03 Sep 2018 13:43:13 -0700 (PDT) [thread overview]
Message-ID: <20180903.134313.92031482262111093.davem@davemloft.net> (raw)
In-Reply-To: <CAFLxGvzOsW4w+pe2xZo7pkuXpBQpQ=rwpZBiaHORXpkE08-uiw@mail.gmail.com>
From: Richard Weinberger <richard.weinberger@gmail.com>
Date: Mon, 3 Sep 2018 22:22:09 +0200
> On Thu, Aug 23, 2018 at 1:20 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi all,
>>
>> On Wed, 22 Aug 2018 16:12:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>> >
>> > On 08/22/2018 04:04 PM, Andrew Donnellan wrote:
>> > > On 23/08/18 02:12, Jeff Kirsher wrote:
>> > >> It appears the entire site is down, including patchworks. Is this
>> > >> expected? And for how long?
>> > >
>> > > + sfr
>> > >
>> > > It appears up for me right now.
>> > >
>> > > We've had a few dropouts over the last few weeks as a result of the upstream ISP having connectivity issues - it's possible that we've just hit that again.
>> > >
>> >
>> > I checked a few hours ago and it was down, but it's been up for over one hour
>> > now for me.
>>
>> It hasn't actually been down for over 140 days, but our hosting company
>> has been having trouble with the router we are connected to and
>> replaced it a few days ago. I have no idea what happened this morning,
>> I will see if I can find out if these intermittent interruptions are
>> going to continue. :-(
>
> The site seems to be unreachable again. At least here in Europe. :-(
It is unreachable for me as well, and has been since this morning PST
timezone.
next prev parent reply other threads:[~2018-09-04 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 16:12 ozlabs.org down? Jeff Kirsher
2018-08-22 23:04 ` Andrew Donnellan
2018-08-22 23:12 ` Randy Dunlap
2018-08-22 23:18 ` Stephen Rothwell
2018-09-03 20:22 ` Richard Weinberger
2018-09-03 20:43 ` David Miller [this message]
2018-09-03 21:26 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180903.134313.92031482262111093.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew.donnellan@au1.ibm.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jk@ozlabs.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=patchwork@lists.ozlabs.org \
--cc=rdunlap@infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox