But:
Your probe 26656 has been disconnected from the RIPE Atlas
infrastructure since 2017-08-16 08:58:54 UTC
What happened between 08:58:54 UTC and 09:30:00 +0000?
--
With Best Regards,
Marat Khalili
On 17/08/17 14:17, Carsten Schiefner wrote:
Hi Marat,
On 17.08.2017 13:02, Marat Khalili wrote:
smells a bit as if greylisting would have been deployed for 'rqc.ru'.
You may be right, but why? It all happens still well within RIPE:
nope - the devil, as always, is in the detail:
Received: from worker1.atlas.ripe.net ([193.0.19.216])
by mahimahi.ripe.net with esmtps
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.89)
(envelope-from <[email protected]>)
id 1dhueG-0001AI-Sl
for [email protected]; Wed, 16 Aug 2017 11:30:02 +0200
11:30:02 +0200 is 09:30:02 +0000 (aka. UTC)
Received: from [127.0.0.1] (helo=worker1.atlas.ripe.net)
by worker1.atlas.ripe.net with esmtp (Exim 4.89)
(envelope-from <[email protected]>)
id 1dhueG-0003zF-Qf
for [email protected]; Wed, 16 Aug 2017 09:30:00 +0000
09:30:00 +0000 is 11:30:00 +0200
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Probe 26656 is disconnected (RQC Ural bld.)
From: RIPE Atlas (no reply) <[email protected]>
To: [email protected]
Reply-To: RIPE Atlas (no reply) <[email protected]>
Date: Wed, 16 Aug 2017 09:30:00 -0000
- so it took at least that very message "only" two seconds to hop from
one NCC host to another NCC host: no "significant" delay here.
Best,
-C.
