[188488] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Cogent Communications

daemon@ATHENA.MIT.EDU (Todd Crane)
Sat Mar 26 02:19:21 2016

X-Original-To: nanog@nanog.org
From: Todd Crane <todd.crane@n5tech.com>
In-Reply-To: <56F6155B.8060202@unlimitednet.us>
Date: Fri, 25 Mar 2016 23:15:25 -0700
To: Brandon Vincent <Brandon.Vincent@asu.edu>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


--Apple-Mail=_A85F5612-D6F2-40FB-B46E-5760A1E62A45
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

As a Cogent customer, I say =E2=80=98good luck=E2=80=99

Last time I called them on a Friday night, it was because they =
announcing (not originating but bad nevertheless) the IPv6 default =
route. The NOC =E2=80=9Cengineer=E2=80=9D I spoke with adamantly =
insisted that there was nothing wrong with this. After about a half hour =
I gave up. The next morning, another tech, wanted an error message or a =
route as an example. It wasn=E2=80=99t until Monday morning that they =
blocked the route.

All I know is that when our contract is up, I can assure you, we won=E2=80=
=99t make the same mistake twice.


> On Mar 25, 2016, at 9:51 PM, Jason Canady <jason@unlimitednet.us> =
wrote:
>=20
> As a Cogent customer, I'm sure I can get you in touch with someone. =
Have you tried emailing support@cogentco.com ?  If not, email me off =
list and I'll find someone you can speak to.
>=20
> - Jason
>=20
> On 3/24/16 4:20 AM, Brandon Vincent wrote:
>> Does anyone have a NOC/SOC contact for Cogent? I found a improperly
>> secured router on the Internet and I'd like to report it.
>>=20
>> Thank you,
>> Brandon Vincent
>=20


--Apple-Mail=_A85F5612-D6F2-40FB-B46E-5760A1E62A45
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJW9ij+AAoJEJnIJbSiHxpVC8IH+wW2s/Z7+XuiZrJdPbaAlxGe
nEmYDkTZHXCIifCylSlyhL1yXzdGnQVR6aLOyTdafe0cSCDkmLB3tYL5S66m5pXt
Blvf3oewgDqMuYx4Lr1/FruPqDpbvydvPt7l+fccYfH3SSJ1yP4MuQ9wMy5caIm/
ugKmN+33CwK55nsbbIL6pTp/HU2Yd8D4mVPXPZfCAoAxIkLJADE6+P0aOCmyhVIo
6xd9MouU0SN4JXGWuuEZy7lmBioLwV2iAfuo7UwXW0ZoSK4hg7mfN20LgyD9wwoc
fqwrL04yf6MS/dj0G0blW4RSrJIpzIzECJlTLWs6p1GNFgNV1iDx66COHaw7Ye8=
=pCKp
-----END PGP SIGNATURE-----

--Apple-Mail=_A85F5612-D6F2-40FB-B46E-5760A1E62A45--

home help back first fref pref prev next nref lref last post