[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #25144 [Metrics/Statistics]: op-us onionperf instance spends much of its time at 100% timeout failure: why?



#25144: op-us onionperf instance spends much of its time at 100% timeout failure:
why?
--------------------------------+------------------------------
 Reporter:  arma                |          Owner:  metrics-team
     Type:  defect              |         Status:  new
 Priority:  Medium              |      Milestone:
Component:  Metrics/Statistics  |        Version:
 Severity:  Normal              |     Resolution:
 Keywords:                      |  Actual Points:
Parent ID:                      |         Points:
 Reviewer:                      |        Sponsor:
--------------------------------+------------------------------

Comment (by cypherpunks):

 op-us is on a streak of timeouts again that started on April 19, 2018
 through the latest data point, a running total of 21 days and going.

 https://metrics.torproject.org/torperf-
 failures.html?start=2018-04-12&end=2018-05-12&source=op-
 us&server=public&filesize=50kb

 op-hk and op-nl are experiencing spikes at the same time but not
 constantly like op-us is.

 Days before that started, the number of bridges fell quickly on April 15
 and 16:
 - https://metrics.torproject.org/bridges-
 ipv6.html?start=2018-04-12&end=2018-04-19
 -
 https://metrics.torproject.org/networksize.html?start=2018-04-01&end=2018-05-01
 The loss of bridges might be explained by Google and Amazon stopping
 domain fronting on April 13 (#25804) and announcing it the week of April
 23 (https://signal.org/blog/looking-back-on-the-front/ ) respectively.
 The working idea is that their decision is a result of a Russian court
 banning Telegram messenger on April 13 and the collateral damage from the
 ensuing cat-and-mouse game between Telegram servers and Roskomnadzor, the
 Russian internet censorship body, blocking IP subnets.

 However, the sudden loss of bridges might not be related to the timeouts
 of op-us starting April 19.  The wiki:doc/MetricsTimeline hasn't been
 updated with clues either.

 According to #21653 and wiki:org/operations/services/onionperf, op-us is
 in Washington, DC at https://op-us.onionperf.torproject.net/ and
 https://199.119.112.144, Allied Telecom Group, LLC, Radio Free Asia, not
 at Google, Amazon, or Azure.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25144#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs