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
Interesting at my 9-5 we use NTT exclusively for SIP traffic and it has
been flawless. If there are any tests that you want me to run over NTT via
their pop at 111 8th let me know.
On Thu, May 9, 2019 at 6:35 AM Chuck Church wrote:
> Are you sure the problem isn’t NTT? My buddy’s WISP peers
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 when Spirit
stopped peering with NTT yesterday. Path is through Telia now
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
6 matches
Mail list logo
