From: Addy Yeow <ayeowch@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Sudden temporary drop in reachable nodes?
Date: Thu, 27 Mar 2014 07:10:56 +1100 [thread overview]
Message-ID: <CAA3bHnzvOj7yjgLJ_fsZN1f1Mjp+QTE_=iaC=O_V1KTii79Y3w@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2HuZc_5E0o5T6DUOvmFr8qmYrhPC9S-VAhJWmA=CbtDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Hi Mike,
That was because I had to restart the crawler for update. This disconnects
the crawler from all reachable nodes temporarily and it will take about 15
minutes (3 snapshots) before the crawler stabilize again. I will look into
annotating these drops with a note.
Cheers,
Addy
On Thu, Mar 27, 2014 at 12:07 AM, Mike Hearn <mike@plan99•net> wrote:
> Hey Addy,
>
> I am seeing a big drop in reachable nodes on
> http://getaddr.bitnodes.io/dashboard/ starting from about March 25th
> 7:20pm and coming back 9:35pm. Is this a glitch in the monitoring system or
> did some real network event happen then?
>
[-- Attachment #2: Type: text/html, Size: 1073 bytes --]
prev parent reply other threads:[~2014-03-26 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 13:07 Mike Hearn
2014-03-26 20:10 ` Addy Yeow [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA3bHnzvOj7yjgLJ_fsZN1f1Mjp+QTE_=iaC=O_V1KTii79Y3w@mail.gmail.com' \
--to=ayeowch@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox