On Tue, Oct 11, 2016 at 7:21 PM, David Hubbard
wrote:
> The specific details are netblocks we’re deploying new servers on,
> previously unused, all seem to be on the block list by default.
How fast are you ramping up traffic on new IPs?
Also, what's the netblock? Maybe others can see issues in t
I replied off list. I should be able to help get David in touch with
someone who can help.
On Wed, Oct 12, 2016 at 10:57 AM, Vick Khera wrote:
> On Tue, Oct 11, 2016 at 7:21 PM, David Hubbard
> wrote:
> > The specific details are netblocks we’re deploying new servers on,
> > previously unused,
I recently had issues with ATT (and SBC and Bellsouth). It also involved a
fairly newish IP range we were warming up and when we moved the bulk of the
traffic over things came down like a hammer. I would get the block lifted
and within a few days it'd start all over. I reached out to the ATT
postma
David, Luke is a good person to assist with this. The one suggestion I
would have in addition to whatever guidance he may have, is that you
perhaps do not want to switch IPs when encountering those blocks. You might
actually be causing additional blocking against you.
You might want to centralize
Thanks all, am going to follow up on the info Luke sent and see if I can get
things moving on the AT&T side. We like to have customer emails specific to
their own servers to make it easy to track abuse, but I have a feeling it’s
just an issue of perhaps an old bogon block or needing to warm thi
