Re: Microsoft / Outlook.com contact???
On 2015-10-15 01:58, Robert Glover wrote: On 10/13/2015 10:49 PM, Michael J Wise wrote: Unfortunately, that's not going to work if the refusal reason was FBLW15 (or TBLW15). You're not dealing with an issue on the Outlook/Hotmail side of the house. If you had provided the last two octets, I might have been able to give some advice earlier, but alas, everyone seems loathe to actually say which IP is having issues. IP in question: 65.111.224.51 Not trying to hide anything, but seeing the posts with obfuscated IPs has rubbed off on me I suppose (for better or for worse. I appreciate if you can help us out here. -Bobby Hi Robert, I just experienced the same problem. It took 10 days before I got delisted without explanation. My IP is clean, never blacklisted, SPF+DKIM+DMARC, present in DNSWL.org, etc. Note that I had no issues for sending emails to @outlook.com. I only had issues (#FBLW15) when sending emails to Office365/ExchangeOnline users (i.e. @dowcorning.com in this case). Best Regards, Arnaud.
Re: Colt outages?
On 08 Sep 2009, at 16:41, Eric Brunner-Williams wrote: Anyone have news on this? I understand Colt has fixed London and are working on Dublin, Bruxelles and Geneva... but that's all I have. The only "interesting" news and comments I found about this outage were on TheRegister.co.uk website: http://www.theregister.co.uk/2009/09/08/colt_telecom_outage/ http://www.theregister.co.uk/2009/09/08/colt_telecom_outage/comments/
Re: community real-time BGP hijack notification service
Andy Davidson wrote: > > On 12 Sep 2008, at 13:49, Nathan Ward wrote: > >> On 12/09/2008, at 10:42 PM, Gadi Evron wrote: >>> Hi, WatchMy.Net is a new community service to alert you when your prefix >>> has been hijacked, in real-time. >> I just had a quick play with this, as I've been considering hacking >> together something similar. > > Everyone with any interest in this topic should look at the MyASN > service from the RIPE NCC (which I use and think is brilliant). > > http://www.ris.ripe.net/myasn.html > I think that most of us (me included) are already using it but the problem is that they don't have BGP collectors everywhere in the world. This is in fact a generic issue for BGP monitoring. So the more we get the best it is and that's why I'll be using Gadi's BGP monitoring tool (and any other that might come) in parallel with the one provided by the RIPE. Note that MyASN will soon be replaced by IS Alarms which is simpler and as efficient as MyASN: http://tinyurl.com/46kfd7 http://ripe.net/is/alarms/ Regards, Arnaud.
Re: community real-time BGP hijack notification service
Hello Gadi, Gadi Evron wrote: > Hi, WatchMy.Net is a new community service to alert you when your prefix > has been hijacked, in real-time. Very good initiative. You can count on me as one of your users. Note that apparently it doesn't seem to be working as expected yet. Indeed I already received two false alerts: 1. Subject: watchmy.net BGP Alert - seeing {91.198.99.0/24, 6450 3737 701 702 43751} Body: Hello, we are seeing 91.198.99.0/24 being advertised with aspath 6450 3737 701 702 43751. We are alerting you because of the rule you set that is watching for prefixes that match or are more specific than 91.198.99.0/24, and are originated with any origin AS other than one of 702,6661,8220 Thanks, watchmy.net's jack-o-meter 2. Subject: watchmy.net BGP Alert - seeing {93.191.216.0/21, 6450 4436 3257 6661 43751} Body: Hello, we are seeing 93.191.216.0/21 being advertised with aspath 6450 4436 3257 6661 43751. We are alerting you because of the rule you set that is watching for prefixes that match or are more specific than 93.191.216.0/21, and are originated with any origin AS other than one of 702,6661,8220 Thanks, watchmy.net's jack-o-meter Is this normal? Regards, APN-RIPE.