summaryrefslogtreecommitdiff
path: root/d3/e0606afe1915f5d8f7bde3b50a30bf94e0abaf
blob: 456efa43421c8bc0ac1228f10ddc8a1b542ce14d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1WSnY6-0001Md-2q
	for bitcoin-development@lists.sourceforge.net;
	Wed, 26 Mar 2014 13:07:18 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.52 as permitted sender)
	client-ip=209.85.219.52; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f52.google.com; 
Received: from mail-oa0-f52.google.com ([209.85.219.52])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WSnY3-0004ut-Ry
	for bitcoin-development@lists.sourceforge.net;
	Wed, 26 Mar 2014 13:07:17 +0000
Received: by mail-oa0-f52.google.com with SMTP id l6so2480551oag.11
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 26 Mar 2014 06:07:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.96.225 with SMTP id dv1mr505260oeb.81.1395839230512; Wed,
	26 Mar 2014 06:07:10 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Wed, 26 Mar 2014 06:07:10 -0700 (PDT)
Date: Wed, 26 Mar 2014 14:07:10 +0100
X-Google-Sender-Auth: CpQuAcMb4GPMJmPtY3pDdjHe8D8
Message-ID: <CANEZrP2HuZc_5E0o5T6DUOvmFr8qmYrhPC9S-VAhJWmA=CbtDA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Addy Yeow <ayeowch@gmail.com>
Content-Type: multipart/alternative; boundary=089e01176c8d7f95e804f58225d5
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WSnY3-0004ut-Ry
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Sudden temporary drop in reachable nodes?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 26 Mar 2014 13:07:18 -0000

--089e01176c8d7f95e804f58225d5
Content-Type: text/plain; charset=UTF-8

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?

--089e01176c8d7f95e804f58225d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey Addy,<div><br></div><div>I am seeing a big drop in rea=
chable nodes on=C2=A0<a href=3D"http://getaddr.bitnodes.io/dashboard/">http=
://getaddr.bitnodes.io/dashboard/</a> starting from about March 25th 7:20pm=
 and coming back 9:35pm. Is this a glitch in the monitoring system or did s=
ome real network event happen then?</div>
</div>

--089e01176c8d7f95e804f58225d5--