Readit NewsDeleted Comment
"the AI that generates the key points may miss context from the webpage and make mistakes" You don't say...
video: https://www.youtube.com/watch?v=L0RUI5kHzEQ
slides: https://storage.googleapis.com/site-media-prod/meetings/NANO...
Edit: yes, I fully agree that traceroute is flawed, it's only ever going to give you an incomplete or even misleading piece of the picture and you shouldn't take what you see as gospel. That said, it has its uses especially for networks that you control and to let you know where to maybe start digging - which is all that any tool does.
Deleted Comment
MTR runs continuously, gathering real-time stats that reveal both packet loss and latency trends over time. MTR provides minimum, average, and maximum response times, plus the standard deviation. This is especially useful for troubleshooting intermittent issues or spotting latency spikes.
Of course, MTR isn’t perfect and still faces some of the same challenges as traceroute, like dealing with ICMP rate-limiting, load-balanced paths, or certain network setups that obscure hops. But overall, it provides a richer, more nuanced view, making it a preferred tool for network diagnostics and troubleshooting.
> The example given is that a handful of users running MTR (do not get me started on this bastard program) can actually hit this rate limit. This is an outstanding example because I have seen something similar in practice.
> Consider what that would look like, and how common it would be: If you have a NOC full of people who think they know what they're doing, but don't, that only enhances the probability that everyone is trying to troubleshoot on their own instead of doing a screenshare and coordinating their efforts - thus, you have six guys running MTR to the same IP. ╔═════════════╦════════════════╦══════════╦════════╦════════╦══════════╦═════════╗
║ Location ║ Provider ║ Protocol ║ Ping ║ Jitter ║ Down ║ Up ║
╠═════════════╬════════════════╬══════════╬════════╬════════╬══════════╬═════════╣
║ Chicago ║ Sharktech ║ IPv4 ║ 60 ms ║ 15 ms ║ 408 Mbps ║ 23 Mbps ║
║ Atlanta ║ Cloudiver ║ IPv6 ║ 67 ms ║ 8 ms ║ 311 Mbps ║ 23 Mbps ║
║ Amsterdam ║ "Rust backend" ║ IPv4 ║ 169 ms ║ 260 ms ║ 68 Mbps ║ 20 Mbps ║
║ Nuremberg ║ Hetzner ║ IPv6 ║ 155 ms ║ 125 ms ║ 132 Mbps ║ 20 Mbps ║
║ Los Angeles ║ Sharktech ║ IPv4 ║ 86 ms ║ 15 ms ║ 373 Mbps ║ 21 Mbps ║
║ Serbia ║ SOX ║ IPv6 ║ 188 ms ║ 29 ms ║ 173 Mbps ║ 17 Mbps ║
║ Tokyo ║ A573 ║ IPv4 ║ 183 ms ║ 72 ms ║ 156 Mbps ║ 22 Mbps ║
╚═════════════╩════════════════╩══════════╩════════╩════════╩══════════╩═════════╝
- easy peasy: lemon
- easy but needs careful handling: kiwi
- regular but boring: red delicious
- regular, who wouldn't want to take one of these?: mango
- large task, risk of splash damage if mishandled: watermelon
- tough to crack, needs time or a hammer: coconut
- technically we'll do this, but not really our job: tomato
Edit: I am sad that emojis aren't allowed in comments, though it's understandable.
Deleted Comment
Isn’t just living and thinking preparing for questions like this? They’re not that hard.
[0] - https://en.wikipedia.org/wiki/Situation,_task,_action,_resul...