Re: ping issues

root@b-ns: ~ # traceroute a.ns.anastrophe.com traceroute to a.ns.anastrophe.com (52.32.92.141), 30 hops max, 60 byte packets  1  216.239.58.214 (216.239.58.214)  37.315 ms 74.125.253.191 (74.125.253.191)  36.234 ms  36.200 ms  2  108.170.242.250 (108.170.242.250)  36.790 ms 108.170.243.9

Re: ping issues

Will do - thanks Martin! On 5/17/18 09:58, mart...@tildeslash.com wrote: Thanks for data. Please can you get yet the ping packet capture (using for example Wireshark) and send it in pcap format to supp...@mmonit.com ? On 17 May 2018, at 18:54, Paul Theodoropoulos

Re: ping issues

Hello, please can you get a network trace of failed ping tests? Best regards, Martin > On 17 May 2018, at 05:45, Paul Theodoropoulos wrote: > > I'm running a little personal project on a shoestring budget - e.g. a couple > of AWS t2.nano instances, so everything needs

Re: ping issues

Thanks for data. Please can you get yet the ping packet capture (using for example Wireshark) and send it in pcap format to supp...@mmonit.com? > On 17 May 2018, at 18:54, Paul Theodoropoulos wrote: > > root@b-ns: ~ # traceroute a.ns.anastrophe.com > traceroute to