This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] any clue rtt unreachable packet loss 100% com234.476.249
- Previous message (by thread): [atlas] any clue rtt unreachable packet loss 100% com234.476.249
- Next message (by thread): [atlas] any clue rtt unreachable packet loss 100% com234.476.249
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Tue Jun 25 12:00:07 CEST 2019
On Mon, Jun 24, 2019 at 09:35:32AM +0200, Dave . <gboonie at gmail.com> wrote a message of 872 lines which said: > Your destination is not responding to ICMP (ping/traceroute). This > is not an Atlas issue. And, for the services who wrongly block ICMP echo, there is still hope, Atlas probes can run traceroute with UDP or TCP, which is cool. A good example: <https://labs.ripe.net/Members/wilhelm/measuring-your-web-server-reachability-with-tcp-ping>
- Previous message (by thread): [atlas] any clue rtt unreachable packet loss 100% com234.476.249
- Next message (by thread): [atlas] any clue rtt unreachable packet loss 100% com234.476.249
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]