menu
Tatoeba
language
Inscriber te Aperir session
language Interlingua
menu
Tatoeba

chevron_right Inscriber te

chevron_right Aperir session

Percurrer

chevron_right Monstrar phrase aleatori

chevron_right Percurrer per lingua

chevron_right Percurrer per lista

chevron_right Percurrer per etiquetta

chevron_right Percurrer audio

Communitate

chevron_right Muro

chevron_right Lista de tote le membros

chevron_right Linguas del membros

chevron_right Parlantes native

search
clear
swap_horiz
search
deniko deniko 31 de decembre 2019 31 de decembre 2019 a 16:48:23 UTC flag Report link Permaligamine

Tatoeba has been very slow the last few days. Also I've been getting "Tatoeba is currently unavailable" message every now and then.

Is it only me?

{{vm.hiddenReplies[33824] ? 'expand_more' : 'expand_less'}} celar responsas monstrar responsas
fjay69 fjay69 31 de decembre 2019 31 de decembre 2019 a 17:12:50 UTC flag Report link Permaligamine

I face this problem too.

AlanF_US AlanF_US 31 de decembre 2019 31 de decembre 2019 a 17:20:44 UTC flag Report link Permaligamine

I see it, too.

Pfirsichbaeumchen Pfirsichbaeumchen 31 de decembre 2019 31 de decembre 2019 a 17:41:06 UTC flag Report link Permaligamine

J’ai le même problème.

Ergulis Ergulis 31 de decembre 2019 31 de decembre 2019 a 17:49:54 UTC flag Report link Permaligamine

I have the same issue.

Elsofie Elsofie 1 de januario 2020 1 de januario 2020 a 01:09:24 UTC flag Report link Permaligamine

I have this problem also the last two days.

ZiriSut ZiriSut 1 de januario 2020 1 de januario 2020 a 10:24:22 UTC flag Report link Permaligamine

Me too, I get the same message these days.

K_hina K_hina 1 de januario 2020 1 de januario 2020 a 11:56:23 UTC flag Report link Permaligamine

I have the same issue too.

marioo marioo 1 de januario 2020 1 de januario 2020 a 15:52:29 UTC flag Report link Permaligamine

Similar here. In addition (and maybe it can provide a clue) when I try to access Tatoeba from Mexico (thanks to VPN) the DNS don't resolve... no access at all. Could there be an issue with the DNS server at the web hosting site?

gillux gillux 1 de januario 2020 1 de januario 2020 a 15:58:09 UTC flag Report link Permaligamine

Tatoeba is facing a DDoS attack. If you’re curious what a DDoS attack is, have a look at https://en.wikipedia.org/wiki/D...service_attack

We are working on it, but there is little we can do about it without blocking legitimate users. We’ll keep you updated.

{{vm.hiddenReplies[33850] ? 'expand_more' : 'expand_less'}} celar responsas monstrar responsas
Ergulis Ergulis 1 de januario 2020, modificate le 1 de januario 2020 1 de januario 2020 a 16:32:03 UTC, modificate le 1 de januario 2020 a 19:21:11 UTC flag Report link Permaligamine

Thanks you very much for informing us. I hope that everything is sorted out soon.

Isn't the DDoS attack a kind of cybercrime?

I fail to understand to whose benefit something like that is, except for satisfying someone's weak mind.

dcsan dcsan 1 de januario 2020 1 de januario 2020 a 17:03:34 UTC flag Report link Permaligamine

perhaps someone else was the target and tatoeba just got caught because they had the wrong IP number... like getting shot in the wrong neighborhood.

{{vm.hiddenReplies[33853] ? 'expand_more' : 'expand_less'}} celar responsas monstrar responsas
deniko deniko 2 de januario 2020 2 de januario 2020 a 09:19:40 UTC flag Report link Permaligamine

Yeah, that's possible, other reasons that come off the top of my head could be the following:

* They're targeting the hosting provider, not tatoeba per se, so they're attacking some of their web sites

* Someone is holding a grudge against Tatoeba.

* Before attacking the real target, it might make sense for the attackers to use some random guinea pigs to test their scripts.

gillux gillux 19 de januario 2020 19 de januario 2020 a 04:53:40 UTC flag Report link Permaligamine

The attack looks finished now. So here is a follow-up.

It was an attack on the application level, sending a lot of forged http requests. The contents of the requests looked like randomly built from a set of real data: a combination of URLs, referers and cookies that looked valid individually, but did not make any sense put together. So after analyzing the traffic, I set up some countermeasures and the attack was contained, so you probably didn’t notice that it lasted for about two weeks. It peaked at 30-40 requests per seconds (or 1500 packets per second), which is rather moderate for a ddos, but apparently enough to partially disturb our service. Interestingly, dev.tatoeba.org and wiki.tatoeba.org were also targeted, but at an unnoticeable rate.

Note that it looks like the countermeasures partially blocked a few legitimate users connecting from China. Sorry about that! It should be okay now.

The meaning of this attack is still unclear. It happened at a time when most western people are on vacation. It was very limited in scale and not so hard to dodge. Also, the zombies were all located in China (which doesn’t necessarily mean the attacker is from China nor operating from China). It is worth noting that Tatoeba is not blocked by the GFW according to greatfire.org. Which makes me think that maybe…

* the attacker wants us to block all users from China
* the attacker wants us to think that the attack is related to China whereas it has nothing to do with it
* the attacker has limited resources (not competent, not rich, not state-sponsored)
* we are part of a bigger attack in which we are not the main target
* the attacker is testing our ability to respond to a ddos attack
* the attacker is just holding a grudge against us

{{vm.hiddenReplies[33997] ? 'expand_more' : 'expand_less'}} celar responsas monstrar responsas
deniko deniko 20 de januario 2020 20 de januario 2020 a 09:04:11 UTC flag Report link Permaligamine

Thanks for keeping us in the loop, gillux, and thanks for having dealt with all that.