Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-11-12 Thread Al Iverson
Thanks! I see today that I am now able to submit my two latest ranges for SNDS access -- I, too, was seeing the "too many RIPE lookups" issue. Cheers, Al Iverson On Mon, Nov 12, 2018 at 8:17 AM Benoit Panizzon wrote: > > Hi List > > Finally git positive Feedback from the SNDS Support Team. It loo

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-11-12 Thread Benoit Panizzon
Hi List Finally git positive Feedback from the SNDS Support Team. It looks like, after some escalations, they solved the issue of too many requests to RIPE. (they only had to contact ripe and ask politely for the quota to be risen I suppose). I was now able to 'Request Access' to more than just s

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-16 Thread Benoit Panizzon
Hi Tobias > Do you try to add a Range? I had problems with the same Error a couple of > years ago, until I figured out that they also look up the Network IP, so for > us it helped to add PTR-RR to 192.168.0.0 with a Domain that also belonged to > us... Ok, so the error message regarding the re

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-16 Thread Tobias Herkula
Cyren (Berlin) From: mailop on behalf of Benoit Panizzon Sent: Tuesday, October 16, 2018 11:22:37 AM To: Michael Wise Cc: mailop@mailop.org Subject: Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-16 Thread Benoit Panizzon
Hi Michael Could you please escalate the case? Apparently your techs don't even bother to look at the problem on their side. Message from the SNDS Website while trying to add IP Ranges: "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow" I

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-11 Thread Michael Wise via mailop
2018 2:37 AM To: mailop@mailop.org Subject: Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow" Short update on this... > To unblock, MS wants to send an SMS to our fixed line abuse desk phone

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-11 Thread Benoit Panizzon
Short update on this... > To unblock, MS wants to send an SMS to our fixed line abuse desk phone > number we added when creating the account, this of course is not > working as switzerland has discontinued fixnet SMS services in July of > this year. So we are stuck here. It looks like it was a se

Re: [mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-11 Thread Benoit Panizzon
Hi List Microsoft is getting ridiculous... We use ab...@imp.ch for our SNDS Login. I have been trying to add our IP Ranges multiple times every week now and even attempted to open a case, which was not yet successful (apparently because I left an old case ID in the subject). The result, is that

[mailop] Microsoft SNDS "Sorry, whois.ripe.net will not let us do any more lookups today. Please come back and try again tomorrow"

2018-10-08 Thread Benoit Panizzon
Hi List Since about a week I regularly try to add our IP Ranges to the Microsoft SNDS Service to be able to react more quickly to incidents. Unfortunately Microsoft does not seem to have talked to RIPE to get a large enough request quota. I always get: "Sorry, whois.ripe.net will not let us do a