...

onionoo is hardly reachable since about 17 hours ago.

Indeed. For some reason Onionoo saw an increase in requests from 700 to 4000 per second 24 hours or so ago.

There's now a third host answering Onionoo requests from a local cache, so that might improve the situation. (Thanks, weasel!)

...

Is this only externally facing or will this also cause onionoo to miss descriptors internally?

The former. If the hourly updater is overloaded, it will simply run less often than once per hour. But it won't miss any data.

...

Any ETA on when this will improve?

It should be better now. If it's still bad after the weekend, we'll make a new plan.

It got better after your email, but now it is back at 4 out of 5 atlas searches running into a backend error message. -- https://mastodon.social/@nusenu https://twitter.com/nusenu_

Is this something that an org such as noisetor could help out with by contributing a public mirror? We'd be more than happy to do so if it'd be useful to the project/community. p On 5/20/17 12:40 PM, nusenu wrote:

Since thecthulhu onionoo mirror is also gone: Is there any other public onionoo instance that one can use?

Did the onionoo requirements for a private instance change since I last asked that question two years ago? (8GB RAM, 250GB disk) https://lists.torproject.org/pipermail/tor-dev/2015-April/008711.html

_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

On 5/22/17 11:26 AM, nusenu wrote:

Patrick O'Doherty:

...

Is this something that an org such as noisetor could help out with by contributing a public mirror? We'd be more than happy to do so if it'd be useful to the project/community.

Since the previous mirror is gone and onionoo.tpo is still struggling an onionoo(+atlas) mirror is certainly helpful from my point of view.

Great. I'll aim to do this in the next day or two and report back to the list when we have a functioning mirror to share.

On 22.05.17 23:11, nusenu wrote:

...

...

Patrick O'Doherty:

...

Is this something that an org such as noisetor could help out with by contributing a public mirror? We'd be more than happy to do so if it'd be useful to the project/community.

Since the previous mirror is gone and onionoo.tpo is still struggling an onionoo(+atlas) mirror is certainly helpful from my point of view.

Great. I'll aim to do this in the next day or two and report back to the list when we have a functioning mirror to share.

great to hear that onionoo gets a mirror (it might take a bit longer than a day since the initial onionoo import of all these CollecTor archives will take its time)

Hi all, we're working on resolving the load issues of the main server and its two caching frontends, which really get hammered since last week for no obvious reason. I hope that we'll have that resolved in the next couple of days. No data will be lost during this time, the service is just hard to reach these days. But if people want to set up mirrors in the meantime to work around the current issues, please feel free to do that. Though I have to admit that we can't provide much support for that. Sorry! All the best, Karsten

On 23.05.17 21:48, nusenu wrote:

...

we're working on resolving the load issues of the main server and its two caching frontends, which really get hammered since last week for no obvious reason.

I wanted to compare atlas weblogs with onionoo data but didn't find any onionoo data on https://webstats.torproject.org/

That's expected. Onionoo uses Varnish as frontend to the Java backend, and webstats.torproject.org only contains sanitized Apache web logs. We don't have anything similar for Onionoo requests. All the best, Karsten