So if I want to understand, for example, what’s happening on slack, I can move to net tracer and start looking at where have we don’t have slack.com easily accessible or not. And. Probably the first thing that strikes my mind is that some regions in the U.S. do not get such a good connectivity in this case.
I mean, the the, the glue is the short latency. The purple is on average, a higher latency. And the red indicator, I mean the larger. Packet loss you see between vantage points and the platform. So I see some problem on the west coast, for example, for slack. So I’m going to filter on that then, and look at the stations that I’ve got on the west coast monitoring slack.
And the partner I see. I mean the first place is that some places get relatively good connectivity. I mean, you’ve got two vantage points in AWS and GCP is not the most interesting ones, but for example, from Los Angeles, you get 43 milliseconds, some packet loss. But from San Jose — same — you get 143 milliseconds as you see, it looks fairly stable when you look at the seven day view.
So we can look at that data and try to understand what is the difference in the way people access slack from those different places. So what you are going to discover is that the SaaS network is complex. So what you see here is all. The network paths that can be taken by a user to reach slack from those places.
