<h3>2019.04 1-7 report (week 14)</h3>
<ul>
<li>gaps between fees onion pages : ~non-existent, <strong>but abnormal timeout pattern at work</strong></li>
<li>gaps between prices onion pages : ~non-existent, <strong>but abnormal timeout pattern at work</strong></li>
<li>fees values : min = 36 s/b (68 occurrences), mean = 138.88 s/b, max = 1000 s/b (302 occurrences). Tremendous increase (+272%).</li>
</ul>
<p>Bisq numbers for the week : 94 BTC/370 trades (-32% BTC, +2% trades)</p>
<p>Exceptions :</p>
<table>
<thead>
<tr>
<th>Dates</th>
<th>cto</th>
<th>rto</th>
<th>herr</th>
<th>undef</th>
<th>sum</th>
</tr>
</thead>
<tbody>
<tr>
<td>1</td>
<td>13</td>
<td>0</td>
<td>0</td>
<td>5</td>
<td><strong>18</strong></td>
</tr>
<tr>
<td>2</td>
<td>5</td>
<td>1</td>
<td>0</td>
<td>5</td>
<td><strong>11</strong></td>
</tr>
<tr>
<td>3</td>
<td>2</td>
<td>0</td>
<td>0</td>
<td>4</td>
<td><strong>6</strong></td>
</tr>
<tr>
<td>4</td>
<td>90</td>
<td>0</td>
<td>0</td>
<td>3</td>
<td><strong>93</strong></td>
</tr>
<tr>
<td>5</td>
<td>39</td>
<td>0</td>
<td>0</td>
<td>4</td>
<td><strong>43</strong></td>
</tr>
<tr>
<td>6</td>
<td>62</td>
<td>0</td>
<td>0</td>
<td>2</td>
<td><strong>64</strong></td>
</tr>
<tr>
<td>7</td>
<td>35</td>
<td>0</td>
<td>0</td>
<td>2</td>
<td><strong>37</strong></td>
</tr>
<tr>
<td><strong>sum</strong></td>
<td><strong>246</strong></td>
<td><strong>1</strong></td>
<td><strong>0</strong></td>
<td><strong>25</strong></td>
<td><strong>272</strong></td>
</tr>
</tbody>
</table>
<ul>
<li>
<p>total pings par week = 288 pings per day x 7 days x 5 onions = 10080 pings</p>
</li>
<li>
<p>272 exceptions / 10080 pings = 2.7%<br>
This number of exceptions is by itself not very high. But in fact, since april 4th,<br>
there is a (strange) timeout pattern which is present, which concerns simultaneously all nodes but doesn't however seem related to connection issues from my side. (I observed the pattern this morning, while my internet connection was working well).<br>
The pattern is a quarter of an hour timeout. Occurs every day from 09:30 to 09:45, 21:30 to 21:45,<br>
but also at other moments. I counted 10 occurences this past week.<br>
See <a href="https://github.com/HarryMacfinned/bisq-monitor/blob/master/bisqFees-2019Q2.txt">https://github.com/HarryMacfinned/bisq-monitor/blob/master/bisqFees-2019Q2.txt</a><br>
It's first time I notice this pattern. I assume it's something coming from the provider side. During those quarter of hours, prices and fees are badly delivered.</p>
</li>
<li>
<p>246 cto / 272 exceptions = 90% (cto = connection timeouts)</p>
</li>
</ul>
<p>Bisq Tor metrics : <a href="https://monitor.bisq.network/" rel="nofollow">https://monitor.bisq.network/</a><br>
Global Tor metrics : <a href="https://metrics.torproject.org/torperf-failures.html" rel="nofollow">https://metrics.torproject.org/torperf-failures.html</a></p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/roles/issues/10#issuecomment-480750072">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtsAc39iPLWyt70M7Mqe78VM4Gw4Rks5vewd8gaJpZM4PL2hy">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtgv3pkcsfgrGyK9pU14bdjdrykgrks5vewd8gaJpZM4PL2hy.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/roles","title":"bisq-network/roles","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/roles"}},"updates":{"snippets":[{"icon":"PERSON","message":"@HarryMacfinned in #10: ### 2019.04 1-7 report (week 14)\r\n\r\n- gaps between fees onion pages : ~non-existent, **but abnormal timeout pattern at work**\r\n- gaps between prices onion pages : ~non-existent, **but abnormal timeout pattern at work**\r\n- fees values : min = 36 s/b (68 occurrences), mean = 138.88 s/b, max = 1000 s/b (302 occurrences). Tremendous increase (+272%).\r\n\r\nBisq numbers for the week : 94 BTC/370 trades (-32% BTC, +2% trades)\r\n\r\nExceptions :\r\n\r\nDates | cto | rto | herr | undef | sum\r\n------|-----|-----|------|-------|-----\r\n1 | 13 | 0 | 0 | 5 | **18**\r\n2 |  5 | 1 | 0 | 5 | **11**\r\n3 |  2 | 0 | 0 | 4 | **6**\r\n4 | 90 | 0 | 0 | 3 | **93**\r\n5 | 39 | 0 | 0 | 4 | **43**\r\n6 | 62 | 0 | 0 | 2 | **64**\r\n7 | 35 | 0 | 0 | 2 | **37**\r\n**sum**  | **246** | **1** | **0** | **25** | **272**\r\n\r\n- total pings par week = 288 pings per day x 7 days x 5 onions = 10080 pings\r\n- 272 exceptions / 10080 pings = 2.7%\r\nThis number of exceptions is by itself not very high. But in fact, since april 4th,\r\nthere is a (strange) timeout pattern which is present, which concerns simultaneously all nodes but doesn't however seem related to connection issues from my side. (I observed the pattern this morning, while my internet connection was working well).\r\nThe pattern is a quarter of an hour timeout. Occurs every day from 09:30 to 09:45, 21:30 to 21:45, \r\nbut also at other moments. I counted 10 occurences this past week.\r\nSee https://github.com/HarryMacfinned/bisq-monitor/blob/master/bisqFees-2019Q2.txt\r\nIt's first time I notice this pattern. I assume it's something coming from the provider side. During those quarter of hours, prices and fees are badly delivered.\r\n\r\n- 246 cto / 272 exceptions = 90% (cto = connection timeouts)\r\n\r\nBisq Tor metrics : https://monitor.bisq.network/\r\nGlobal Tor metrics : https://metrics.torproject.org/torperf-failures.html\r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/roles/issues/10#issuecomment-480750072"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/roles/issues/10#issuecomment-480750072",
"url": "https://github.com/bisq-network/roles/issues/10#issuecomment-480750072",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>