Re: AWS hosted sites like slack unreachable

[Glenn Kelley <glenn@connectivity.engineer>]

We have seen this in our consulting business with a large number of
smaller ISPs both FISP and WISPS

Often it is due to traffic leaving the network they believe to be an attack.

If you let them know the Network Blocks, ASN, etc in an email to
abuse () amazonaws com they are very responsive.

I would suggest running a simple netflow  and see what might be going
outbound to them as well.  There is a good chance you will see an
outlier or two in the netflow should it be an abuse issue.

I hope that helps
Glenn S. Kelley,
I am a Connectivity.Engineer
Text and Voice Direct:  740-206-9624


a Division of CreatingNet.Works
IMPORTANT: The contents of this email and any attachments are
confidential. They are intended for the named recipient(s) only. If
you have received this email by mistake, please notify Glenn Kelley,
the sender, immediately and do not disclose the contents to anyone or
make copies thereof.

On Thu, Jul 20, 2023 at 5:32 PM Daniel Marks via NANOG <nanog () nanog org> wrote:
> You didn’t specify anything that would be useful to narrow down the issue (i.e. location, asn, error codes, etc) - We 
> had a somewhat similar issue at DET-IX with routes to us-east-1 and us-east-2 seeing a lot of packet loss, but AWS 
> eventually just de-peered the exchange entirely since it was an issue with their equipment.
>
> On Jul 20, 2023, at 5:17 PM, Margi Varia via NANOG <nanog () nanog org> wrote:
>
> Hi Nanog,
>
> We are seeing this weird issue in one part of the network. Customers in one public subnet are not able to reach 
> certain websites suddenly which are hosted in AWS like slack.com, bill.com..
>
> We changed the subnet to new one and issue resolved, after 48 hours, we have the same issue again. We are not AWS 
> customer, so can't call them, but what are our options?
>
> Thanks,
> Margi