From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jeremy Kerr <jk@ozlabs.org>,
patchwork@lists.ozlabs.org, netdev <netdev@vger.kernel.org>
Subject: Re: ozlabs.org down?
Date: Thu, 23 Aug 2018 09:18:39 +1000 [thread overview]
Message-ID: <20180823091839.5301b109@canb.auug.org.au> (raw)
In-Reply-To: <d5cc926d-7efe-d13e-c510-0383c86e5f46@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
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. :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-23 2:45 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 [this message]
2018-09-03 20:22 ` Richard Weinberger
2018-09-03 20:43 ` David Miller
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=20180823091839.5301b109@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrew.donnellan@au1.ibm.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jk@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork@lists.ozlabs.org \
--cc=rdunlap@infradead.org \
/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