Dear Nick,
I sympathize with you plight, network debugging can be quite a test of
character at times.
I am snipping some text as I can't comment on on specific details in
this case, but you do raise two excellent questions which I can maybe
help with.
On Thu, May 09, 2019 at 03:05:43PM +,
lf Of
Job Snijders
Sent: Thursday, May 9, 2019 10:24
To: Chuck Church
Cc: nanog@nanog.org
Subject: Re: Routing issues to AWS environment.
Hi Chuck,
On Thu, May 09, 2019 at 06:34:21AM -0400, Chuck Church wrote:
> Are you sure the problem isn’t NTT? My buddy’s WISP peers with Spirit
> an
Hi Chuck,
On Thu, May 09, 2019 at 06:34:21AM -0400, Chuck Church wrote:
> Are you sure the problem isn’t NTT? My buddy’s WISP peers with Spirit
> and had a boatload of problems with random packet loss affecting
> initially just SIP and RTP (both UDP). Spirit was blaming NTT.
> Problems went away
.
>
>
>
> chuck
>
>
>
> *From:* NANOG *On Behalf Of *Curt Rice
> *Sent:* Wednesday, May 08, 2019 10:56 AM
> *To:* nanog@nanog.org
> *Subject:* Routing issues to AWS environment.
>
>
>
> Hi are there any AWS engineers out there? We are seeing routing problems
>
to their main
SIP trunk provider.
chuck
From: NANOG On Behalf Of Curt Rice
Sent: Wednesday, May 08, 2019 10:56 AM
To: nanog@nanog.org
Subject: Routing issues to AWS environment.
Hi are there any AWS engineers out there? We are seeing routing problems
between NTT and AWS in Ashburn, Va
I was just about to email the group for a related issue.
We are also seeing some funky routing/peering within the AWS network.
We primarily communicate with Verizon Media/Oath - AS10310. Verizon Media has a
presence in Singapore, and its peered locally with AWS AS38895 - we normally
see 8ms
Hi are there any AWS engineers out there? We are seeing routing problems
between NTT and AWS in Ashburn, Va and would like to find out which side is
having the problem.
Thanks,
Curt
7 matches
Mail list logo
