Hello,
Could you send me some more details in private about who you spoke with
including email addresses and ticket numbers with our NOC if any?
I'd like to understand what happened here as this is an uncharacteristic
outcome. I know there was planned work in Seattle last night for a software
On 23 March 2016 at 23:39, Paras Jha wrote:
> At a loss as to what to do now, since their NOC isn't receptive. Anyone
> have someone I can contact off-list to get this issue resolved? It's
> especially frustrating because the problem absolutely cannot be resolved on
> our end, even with a no-expor
which route and did you look at their lookingglass during the period of
time when things were/are bad to see what the LG saw?
https://www.us.ntt.net/support/looking-glass/
shouting into the wind doesn't really help, information though could be
helpful.
On Wed, Mar 23, 2016 at 7:39 PM, Paras Jha
Hi all,
I've been trying to get this issue resolved for the entire day now, but NTT
has been pretty unreceptive here.
We're announcing a large prefix for a client across our network, and we
discovered some insanely high latency.
After tracking down the issue, we determined it to be something wro
4 matches
Mail list logo
