nanog mailing list archives
Re: Purchased IPv4 Woes
From: Pete Baldwin <pete () tccmail ca>
Date: Sun, 12 Mar 2017 10:27:52 -0400
We used giglinx. There was a third party that was validating the blocks, and they/we caught a lot of issues with the first block for offer.
This was the second block offered, and it looked decent, but I never personally checked the /16 parent. I was only looking at the /18. The reason I made this post is to try and catch the things I couldn't see. We don't appear to be on any lists (RBLs, senderbase look good), but obviously we are still in peoples filtering rules. The big one was Spamhaus DROP but that was removed before we purchased the block.
The previous owner looked fine too, it was actually the owner before the last that seemed to have been the cause of a lot of the bad rep, but again that was cleaned up before we ever even made the request to buy.
----- Pete Baldwin Tuckersmith Communications (P) 519-565-2400 (C) 519-441-7383 On 03/11/2017 11:27 PM, Bryan Holloway wrote:
Indeed.Let this be a lesson: when purchasing blocks, one MUST do their due diligence. Check the RBLs, senderbase, previous owner reputation, etc. before buying.Caveat emptor. On 3/11/17 3:13 PM, Martin Hannigan wrote:Which broker did you use fot the transaction?Did you get a discount for knowingly accepting a dirty block or is this asurprise? Are folks asking for warranties on acquired addresses these days? Cheers, -M< Best, -M< On Fri, Mar 10, 2017 at 12:11 Pete Baldwin <pete () tccmail ca> wrote:Hi All, Hopefully this is not taken in bad taste. Our organizationpurchased some IP space last year (163.182.192.0/18 to be specific), andit appears that this block must have been used for less-than-admirable purposes in the past.We have been trying to clean up the reputation where possible, and we donot appear to be on any blacklists, but we do appear to be blocked from a lot of networks across the US/Canada. I am noticing a lot of nameservers blocking our requests, many web servers, gaming servers, mail etc.This is a transition block for us to move towards v6 everywhere, but wehave many systems that will need to rely on this block of space for sometime to come. We are a small rural co-op ISP in Ontario, and I am just writing this email as an extra plea so that if you happen to run a network that has this entire range on your naughty list, we would appreciate you giving it another chance. I can be contacted on or off list, thanks. -- ----- Pete Baldwin Tuckersmith Communications (P) 519-565-2400 (C) 519-441-7383
Current thread:
- Purchased IPv4 Woes Pete Baldwin (Mar 10)
- Re: Purchased IPv4 Woes Laurent Dumont (Mar 10)
- Re: Purchased IPv4 Woes Mike Hale (Mar 10)
- Re: Purchased IPv4 Woes Pete Baldwin (Mar 12)
- Re: Purchased IPv4 Woes Pete Baldwin (Mar 12)
- Re: Purchased IPv4 Woes Mike Hale (Mar 10)
- Re: Purchased IPv4 Woes Martin Hannigan (Mar 11)
- Re: Purchased IPv4 Woes Bryan Holloway (Mar 11)
- Re: Purchased IPv4 Woes Bob Evans (Mar 11)
- Re: Purchased IPv4 Woes Pete Baldwin (Mar 12)
- Re: Purchased IPv4 Woes Bryan Holloway (Mar 11)
- Re: Purchased IPv4 Woes Justin Wilson (Mar 12)
- RE: Purchased IPv4 Woes Chuck Church (Mar 12)
- RE: Purchased IPv4 Woes Clayton Zekelman (Mar 12)
- Re: Purchased IPv4 Woes Stephen Frost (Mar 12)
- Re: Purchased IPv4 Woes valdis . kletnieks (Mar 12)
- Re: Purchased IPv4 Woes Baldur Norddahl (Mar 12)
- Re: Purchased IPv4 Woes Chris Knipe (Mar 12)
- Re: Purchased IPv4 Woes Chris Knipe (Mar 12)
- Re: Purchased IPv4 Woes valdis . kletnieks (Mar 12)
- Re: Purchased IPv4 Woes Chris Knipe (Mar 12)
- RE: Purchased IPv4 Woes Chuck Church (Mar 12)
- Re: Purchased IPv4 Woes Laurent Dumont (Mar 10)