I’ll Just pop in here to echo Randy’s comments - we have great experiences with
NTT across the board and they did reach out and resolve the issue.
-Ben
> On Dec 4, 2019, at 1:26 PM, Randy Bush wrote:
>
>
>>
>>> just to say that they are awesome
>> so, uh, you don't recommend them to your co
>> just to say that they are awesome
> so, uh, you don't recommend them to your competitors then?
no way. my competitors should buy from comcast, he, ...
Randy Bush wrote on 04/12/2019 21:05:
just to say that they are awesome
so, uh, you don't recommend them to your competitors then?
Nick
> This may be a good moment to mention that the excellent people at the
> NTT NOC are always available at n...@ntt.net, or the phone numbers
> listed in PeeringDB. :-)
just to say that they are awesome
Hi all,
We are following up off-list!
This may be a good moment to mention that the excellent people at the NTT
NOC are always available at n...@ntt.net, or the phone numbers listed in
PeeringDB. :-)
Kind regards,
Job
On Tue, Dec 3, 2019 at 23:19 Ben Cannon wrote:
> We’re trying to figure ou
We’re trying to figure out wether this is an isolated or wider incident,
looking like one of our customer’s flows is fragging between NTT and Comcast.
5 ae-0.a02.snjsca04.us.bb.gin.ntt.net (129.250.2.3) 5.571 ms 13.026 ms
9.514 ms
6 ae-0.comcast.snjsca04.us.bb.gin.ntt.net (129.250.66.34)
6 matches
Mail list logo
