It's on status.apache.org so we already know about it. On Tue, Jun 11, 2013 at 07:33:55AM -0400, Karl Wright wrote: > FWIW, JIRA is also down; https://issues.apache.org/jira does not respond, > or takes a very long time. > > Karl > > > On Tue, Jun 11, 2013 at 7:18 AM, Oliver-Rainer Wittmann < > orwittm...@googlemail.com> wrote: > > > Hi, > > > > > > On 11.06.2013 13:16, Oliver-Rainer Wittmann wrote: > > > >> Hi, > >> > >> On 11.06.2013 13:06, Daniel Shahaf wrote: > >> > >>> On Tue, Jun 11, 2013 at 12:42:48PM +0200, Oliver-Rainer Wittmann wrote: > >>> > >>>> Hi, > >>>> > >>>> On 11.06.2013 12:00, RGB ES wrote: > >>>> > >>>>> I'm trying to take some bugs on ES translation (in fact, I just fixed a > >>>>> couple of them), but bugzilla is not responding > >>>>> > >>>>> Error 101 (net::ERR_CONNECTION_RESET) > >>>>> > >>>>> > >>>> I also can not access Bugzilla - https://issues.apache.org/ooo/ > >>>> https://issues.apache.org/ is not accessible, too. > >>>> > >>>> Putting infra@a.o on CC - may be infra knows the reason. > >>>> > >>>> > >>> We knew about this. Did you check status.apache.org? > >>> > >>> > >> After written the post I remember the infrastructure maintance mail. > >> Then I had a look at status.apache.org saw the critical status. > >> A minute or so later the status went back to green. > >> > >> > > Now, the status is back to critical :( > > > > > > Best regards, Oliver. > >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
