Hi there I just tried to use the RIPE WHOIS but it looks like it's currently down: on terminal:
patrick@patrickhome:~$ whois 185.117.xx.0 connect: Connection refused
web whois:
Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /search/query.html.
Reason: Error reading from remote server
Anyone else? Regards Patrick
Hello Patrick, There is indeed a problem with the RIPE whois service, and my colleagues are working on it. I'm not part of the team that looks after this service, and I don't know what the problem is, but please be assured that my colleagues are working on fixing it. Regards, Anand Buddhdev RIPE NCC On 26/11/2016 22:12, Patrick Velder wrote:
Hi there
I just tried to use the RIPE WHOIS but it looks like it's currently down:
on terminal:
patrick@patrickhome:~$ whois 185.117.xx.0 connect: Connection refused
web whois:
Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /search/query.html.
Reason: Error reading from remote server
Anyone else?
Regards Patrick
Dear working group, The RIPE Whois service suffered an outage on 26 November from around 20:45 until 23:30 UTC. The outage was caused by high memory usage that affected all nodes in the cluster. We have had to recalibrate the memory allocations on each node and restart each of them. As we were doing this the service became intermittently available from around 22:00 UTC. By 23:30 UTC the service was stable again. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group
On 26 Nov 2016, at 22:21, Anand Buddhdev <anandb@ripe.net> wrote:
Hello Patrick,
There is indeed a problem with the RIPE whois service, and my colleagues are working on it. I'm not part of the team that looks after this service, and I don't know what the problem is, but please be assured that my colleagues are working on fixing it.
Regards, Anand Buddhdev RIPE NCC
On 26/11/2016 22:12, Patrick Velder wrote:
Hi there
I just tried to use the RIPE WHOIS but it looks like it's currently down:
on terminal:
patrick@patrickhome:~$ whois 185.117.xx.0 connect: Connection refused
web whois:
Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /search/query.html.
Reason: Error reading from remote server
Anyone else?
Regards Patrick
Hi Tim Can you give a bit more info on this please? Why the sudden increase in memory usage? Are you also saying all whois instances are virtual and running on a single server so a memory problem on that server took down all whois instances? What happened with the Stockholm server? I thought that was supposed to be a fail over in case all Amsterdam servers went down? Cheers Denis On 27 Nov 2016 9:56 a.m., "Tim Bruijnzeels" <tim@ripe.net> wrote:
Dear working group,
The RIPE Whois service suffered an outage on 26 November from around 20:45 until 23:30 UTC.
The outage was caused by high memory usage that affected all nodes in the cluster. We have had to recalibrate the memory allocations on each node and restart each of them. As we were doing this the service became intermittently available from around 22:00 UTC. By 23:30 UTC the service was stable again.
Kind regards,
Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group
On 26 Nov 2016, at 22:21, Anand Buddhdev <anandb@ripe.net> wrote:
Hello Patrick,
There is indeed a problem with the RIPE whois service, and my colleagues are working on it. I'm not part of the team that looks after this service, and I don't know what the problem is, but please be assured that my colleagues are working on fixing it.
Regards, Anand Buddhdev RIPE NCC
On 26/11/2016 22:12, Patrick Velder wrote:
Hi there
I just tried to use the RIPE WHOIS but it looks like it's currently down:
on terminal:
patrick@patrickhome:~$ whois 185.117.xx.0 connect: Connection refused
web whois:
Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /search/query.html.
Reason: Error reading from remote server
Anyone else?
Regards Patrick
participants (4)
-
Anand Buddhdev -
den is -
Patrick Velder -
Tim Bruijnzeels