> On Jan 23, 2016, at 1:50 PM, Max Tulyev wrote:
>
> People do prefix filtering based on *DB may think twice...
Ideally you would have your own local mirror or similar.
Since there is the near realtime mirroring that occurs, other servers get the
data within 5-30 minutes.
This means you can
>> How come? What situations would you run into that are so urgent
>> about updating prefix lists that the task can’t be put off
>> for a few hours?
> Those of you who have cron jobs doing an automatic pull can be quite
> surprised by scenarios like this.
doing it from cron, smart. installing re
On Sat, 23 Jan 2016 14:02:52 -0500, Daniel Corbe said:
> How come? What situations would you run into that are so urgent about
> updating
> prefix lists that the task canât be put off for a few hours?
Those of you who have cron jobs doing an automatic pull can be quite surprised
by scenarios l
On Sat, Jan 23, 2016 at 12:42:07AM -0500, Larry J. Blunk wrote:
> Service for the RADb whois protocol has now been restored. We were
> experiencing extensive DDOS activity directed at the whois service
> host(s).
The whois.radb.net IPv4 address changed earlier today, the new IP is
129.250.120.86.
How come? What situations would you run into that are so urgent about updating
prefix lists that the task can’t be put off for a few hours?
> On Jan 23, 2016, at 1:50 PM, Max Tulyev wrote:
>
> People do prefix filtering based on *DB may think twice...
>
> On 23.01.16 07:42, Larry J. Blunk wr
People do prefix filtering based on *DB may think twice...
On 23.01.16 07:42, Larry J. Blunk wrote:
>
>Service for the RADb whois protocol has now been restored. We were
> experiencing
> extensive DDOS activity directed at the whois service host(s).
>
> Regards,
>Larry Blunk
>Meri
NTT also seemed to suffer, I wonder if it's the same issue there...
Rubens
On Sat, Jan 23, 2016 at 3:42 AM, Larry J. Blunk wrote:
>
>Service for the RADb whois protocol has now been restored. We were
> experiencing
> extensive DDOS activity directed at the whois service host(s).
>
> Reg
Service for the RADb whois protocol has now been restored. We were
experiencing
extensive DDOS activity directed at the whois service host(s).
Regards,
Larry Blunk
Merit
Same here, could not contact when I tried earlier today
On Fri 22 Jan 2016 at 23:44 Stephen Fulton wrote:
> Same here, whois.radb.net still appears down as of this message.
>
> -- Stephen
>
>
> On 2016-01-22 5:27 PM, Brian Rak wrote:
> > whois.radb.net seems to have been down since sometime last
Brian Rak wrote:
> whois.radb.net seems to have been down since sometime last night, has
> anyone else seen problems with this?
since at least 2016-01-21, 20:30 UTC. It would be great if someone from
RADB could give an update on what's happening because this downtime is
causing operational proble
Same here, whois.radb.net still appears down as of this message.
-- Stephen
On 2016-01-22 5:27 PM, Brian Rak wrote:
whois.radb.net seems to have been down since sometime last night, has
anyone else seen problems with this?
It seems the web interface still works, but that's not very useful for
whois.radb.net seems to have been down since sometime last night, has
anyone else seen problems with this?
It seems the web interface still works, but that's not very useful for
scripts.
12 matches
Mail list logo