Greetings, I do not know anything about probes 14203 or 16058. The only probes I am involved with / responsible for are 10555 and 11513. Cheers, Rusty D On Mon, Oct 20, 2014 at 1:16 AM, Phillip Remaker <remaker@gmail.com> wrote:

Thanks for the update!

Can you give me any insight into #14203 and #16058?

16058 is particularly troubling, since it never seems to have come up in the first place. I have it connected and powered up, with no joy. Is there any way to fully reset it?

On Sun, Oct 19, 2014 at 6:49 PM, Rusty Dekema <rdekema@gmail.com> wrote:

...

Good evening,

In case you track these sorts of things, the ~2 week disconnection of this probe was caused by network trouble on my end (combined with an extended vacation), and not by the probe itself or any other part of the RIPE Atlas system.

Cheers, Rusty Dekema

---------- Forwarded message ---------- From: RIPE Atlas <atlas@ripe.net> Date: Sun, Oct 19, 2014 at 9:40 PM Subject: Your RIPE Atlas Probe (ID: 11513) is now connected to our network To: rdekema@gmail.com

Dear RIPE Atlas probe host,

Thank you for participating in RIPE Atlas!

We're just letting you know that your probe (#11513 with description Comcast Business 50/10 (with IPv6 trial).) has re-established its link to our network and we are again receiving data from it. For your own records, it appears that the reconnection took place at 2014-10-20 01:39 UTC.

If you have any questions, please contact us at atlas@ripe.net

Best regards,

RIPE Atlas Team

********** You are receiving this message because you applied for or were given a RIPE Atlas probe. We will only send messages when your probe becomes disconnected for an extended period of time.