Hi all,

So we're monitoring everything possible inside our network but
wondered what others do to check routes that come in to your network
via transit for latency/pl etc.? With the mixture of transit and
public peering, even on our startup network, it's something to think
about the best way. Also, how far out do you monitor? Just to your BGP
peers or some known point after that? It's not good just pinging some
public service as I'm sure they won't like it. I hear Pingdom and
others but not sure.

Thanks,

Gavin.

-- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E [email protected]

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/

Suretec Systems is a limited company registered in Scotland. Registered
number: SC258005. Registered office: 24 Cormack Park, Rothienorman,
Inverurie,
Aberdeenshire, AB51 8GL.

Subject to disclaimer at http://www.suretecgroup.com/disclaimer.html

Do you know we have our own VoIP provider called SureVoIP? See
http://www.surevoip.co.uk

OpenPGP (GPG/PGP) Public Key: 0x8CFBA8E6 - Import from hkp://subkeys.pgp.net
or http://www.suretecgroup.com/0x8CFBA8E6.gpg

Reply via email to