[j-nsp] Internet monitoring in case of general issues

[Mark Tinka]

On 14/Mar/20 15:24, james list wrote:

> Many times we recognize issues on internet, customer asking why additional
> delays are experienced, why it takes so long to access services, why "this
> afternoon is slow", we notice fresh bgp updates, etc etc...
>
> Everybody should know internet is cheap but unrealiable, customers many
> times would like to save money with an ipsec vpn but then ask for
> penalities if the service is not reachable, there is ddos opportunity etc
> etc
>
> The question: once you notice issues on internet and your upstreams are
> fine, what instrument or service or commands or web site do you use to try
> to find out where is the problem and who is experiencing the problem (ie a
> tier1 carrier)?

It's helpful if you know some people in the industry for very obscure
faults far beyond your network. Or at least, someone who knows the
person you need to find.

Beyond checking your own network, checking your direct peers, checking
your direct transit providers, and using the regular tools (ping,
traceroute, remote looking glasses, e.t.c.), if a problem is beyond your
usual boundaries and you need to get that looked at, being on the right
mailing list or knowing the right people will be one of your biggest tools.

I know I've helped a lot of people running networks in places I've never
heard of, and vice versa, because we've met on a mailing list, at beer
session after a conference, or something in between.

So next time you're a peering forum or similar conference, don't skip
the beer session :-).

Mark.