Odd, though, that they didn't respond for three days. I've typically had
good luck with that, although admittedly it's been months since I've
opened an e-mail ticket with their NOC. Spam-filter?
On 12/14/16 2:18 PM, Mike Hammett wrote:
I think people are just going to see a traceroute determining packet loss and
not going to read the rest of what happened. Just going to shortcut to an
answer.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest-IX
http://www.midwest-ix.com
----- Original Message -----
From: "Randy" <[email protected]>
To: "Nanog" <[email protected]>
Sent: Wednesday, December 14, 2016 1:16:41 PM
Subject: Cogent NOC
Hi all,
Anyone beyond front line support at cogento on list?
Nanog is the last place I'd look for assistance but it seems support
over at cogentco is not nearly what it used to be.
Example MTR to cogen't own website (support doesn't utilize or
understand MTR at all apparently):
Host Loss% Snt Last Avg Best
Wrst StDev
1. x.x.x.x 0.0% 196 0.5 11.7 0.3
186.8 35.2
2. x.x.x.x 0.0% 196 0.6 10.2 0.4
226.3 36.2
3. 38.88.249.209 0.0% 196 0.9 1.1 0.7
17.7 1.2
4. te0-0-2-3.nr13.b023801-0.iad01.atl 0.0% 196 1.0 1.0 0.8
2.0 0.1
5. te0-0-0-1.rcr22.iad01.atlas.cogent 2.0% 196 2.1 1.9 1.0
3.3 0.4
6. be2961.ccr41.iad02.atlas.cogentco. 2.6% 196 1.8 2.1 1.1
3.8 0.5
7. be2954.rcr21.iad03.atlas.cogentco. 2.6% 196 2.0 2.3 1.2
9.4 0.7
8. be2952.agr11.iad03.atlas.cogentco. 0.5% 196 2.7 2.6 1.5
6.8 0.6
9. cogentco.com 4.1% 196 2.1 2.0 1.0
16.8 1.1
Pretty much the same to anywhere. Packet loss begins at rcr22.iad01
and propagates all the way down the line. Worse during peak hours,
gone late at night.
After three days of no email response for my ticket, I called and after
an hour of my life I want back, front line support cannot reproduce the
loss. Final conclusion: "Your host is dropping packets".
