# Info about the outage

**URL:** <https://boards.straightdope.com/t/info-about-the-outage/752843>\
**Category:** About This Message Board\
**Created:** [April 22, 2016, 7:36pm UTC](https://boards.straightdope.com/t/info-about-the-outage/752843 "2016-04-22T19:36:10Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![Siam\_Sam](https://avatars.discourse-cdn.com/v4/letter/s/d78d45/32.png) [@Siam\_Sam](https://boards.straightdope.com/u/Siam_Sam)\
**Post date:** [April 23, 2016, 1:21am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/81 "2016-04-23T01:21:05Z")

</div>

> [@Siam\_Sam](#):
>
> I’m not getting logged out or having to log in multiple times, but threads are not marked Read once I read them.

Okay, finally I got logged out and had to log in again. And threads are still all marked Unread.

---

<div class="post-metadata">

**Author:** ![Chronos](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chronos/32/134_2.png) [@Chronos](https://boards.straightdope.com/u/Chronos)\
**Post date:** [April 23, 2016, 1:22am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/82 "2016-04-23T01:22:42Z")

</div>

I’m guessing that the DDoS was itself a whole bunch of failed login attempts.

---

<div class="post-metadata">

**Author:** ![GuanoLad](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/guanolad/32/42_2.png) [@GuanoLad](https://boards.straightdope.com/u/GuanoLad)\
**Post date:** [April 23, 2016, 1:23am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/83 "2016-04-23T01:23:33Z")

</div>

> [@ThelmaLou](#):
>
> Finally found the FB group.

I’m not on Facebook, and apparently the group is private or closed to outside peeks or whatever the hell they call it in that weird dimension it occupies. So a hard-to-search-for group, on a site most here are not members of, which is closed to outsiders, is not the best place to go to for information.

---

<div class="post-metadata">

**Author:** ![MacTech](https://avatars.discourse-cdn.com/v4/letter/m/c0e974/32.png) [@MacTech](https://boards.straightdope.com/u/MacTech)\
**Post date:** [April 23, 2016, 1:25am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/84 "2016-04-23T01:25:08Z")

</div>

> [@Morgenstern](#):
>
> Seal Team 6?

SDMB MIRV ICBM attack on the scumbags, ideally…

---

<div class="post-metadata">

**Author:** ![Siam\_Sam](https://avatars.discourse-cdn.com/v4/letter/s/d78d45/32.png) [@Siam\_Sam](https://boards.straightdope.com/u/Siam_Sam)\
**Post date:** [April 23, 2016, 1:27am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/85 "2016-04-23T01:27:13Z")

</div>

Another problem I just noticed. Multiquoting is no longer allowed.

---

<div class="post-metadata">

**Author:** ![Reeses\_Monkey](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/reeses_monkey/32/2885_2.png) [@Reeses\_Monkey](https://boards.straightdope.com/u/Reeses_Monkey)\
**Post date:** [April 23, 2016, 1:31am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/86 "2016-04-23T01:31:04Z")

</div>

I’m still having to log back in every time I come back.

---

<div class="post-metadata">

**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\
**Post date:** [April 23, 2016, 1:32am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/87 "2016-04-23T01:32:52Z")

</div>

> [@Chronos](#):
>
> I’m guessing that the DDoS was itself a whole bunch of failed login attempts.

You mean like continuously running the user list through a login function without any password? That would explain why so many, myself included, were flagged as having exceeded our failed login tries.

And if the rogue program was running on the server, would explain why the offending IP showed an internal number.

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [April 23, 2016, 1:34am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/88 "2016-04-23T01:34:38Z")

</div>

> [@Siam\_Sam](#):
>
> Another problem I just noticed. Multiquoting is no longer allowed.

Another problem I just noticed … read-before-you-post protocols remain the same as ever … 😉

> [@wolfpup](#):
>
> Another problem I just noticed: the multi-quote function didn’t work the one time I tried it. The multi-quote above was done manually.

Just kidding … this is a very busy thread! 🙂

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [April 23, 2016, 1:34am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/89 "2016-04-23T01:34:47Z")

</div>

I’m also still having trouble with Tapatalk. It often can’t get the contents of the board and kicks me back to the front page (Main). And, even when I’m in, I don’t have any reply or quote buttons.

At first I just assumed it was only sometimes getting in. But the reply thing makes me think that maybe one of the fixes borked Tapatalk.

And, do note, this Tapatalk is used a lot around here.

---

<div class="post-metadata">

**Author:** ![Princhester](https://avatars.discourse-cdn.com/v4/letter/p/3e96dc/32.png) [@Princhester](https://boards.straightdope.com/u/Princhester)\
**Post date:** [April 23, 2016, 1:35am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/90 "2016-04-23T01:35:03Z")

</div>

Well I’m back. I knew you would all be worried about me, but I’m OK. You can relax. Sorry to have caused you concern.

---

<div class="post-metadata">

**Author:** ![snowthx](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/snowthx/32/10660_2.png) [@snowthx](https://boards.straightdope.com/u/snowthx)\
**Post date:** [April 23, 2016, 1:36am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/91 "2016-04-23T01:36:04Z")

</div>

I was not here for the Great Banning. Will this be known as “The Great Outage”?

---

<div class="post-metadata">

**Author:** ![El\_Kabong](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/el_kabong/32/496_2.png) [@El\_Kabong](https://boards.straightdope.com/u/El_Kabong)\
**Post date:** [April 23, 2016, 1:36am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/92 "2016-04-23T01:36:58Z")

</div>

Glad the Board seems to be back on it’s little centipede feet. That was sheer torture.

---

<div class="post-metadata">

**Author:** ![Siam\_Sam](https://avatars.discourse-cdn.com/v4/letter/s/d78d45/32.png) [@Siam\_Sam](https://boards.straightdope.com/u/Siam_Sam)\
**Post date:** [April 23, 2016, 1:40am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/93 "2016-04-23T01:40:23Z")

</div>

> [@wolfpup](#):
>
> Another problem I just noticed … read-before-you-post protocols remain the same as ever … 😉  
> Just kidding … this is a very busy thread! 🙂

:smack:

---

<div class="post-metadata">

**Author:** ![Baron\_Greenback](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/baron_greenback/32/48_2.png) [@Baron\_Greenback](https://boards.straightdope.com/u/Baron_Greenback)\
**Post date:** [April 23, 2016, 1:43am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/94 "2016-04-23T01:43:09Z")

</div>

> [@Musicat](#):
>
> You mean like continuously running the user list through a login function without any password? That would explain why so many, myself included, were flagged as having exceeded our failed login tries.
> 
> And if the rogue program was running on the server, would explain why the offending IP showed an internal number.

Yeah, the “Distributed” part of DDOS not applying here.

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [April 23, 2016, 1:43am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/95 "2016-04-23T01:43:52Z")

</div>

> [@Musicat](#):
>
> You mean like continuously running the user list through a login function without any password? That would explain why so many, myself included, were flagged as having exceeded our failed login tries.
> 
> And if the rogue program was running on the server, would explain why the offending IP showed an internal number.

On, ahem, another board, I read a theory that they might have been spoofing their IP address to avoid being easily caught.

I know I remember one hacker in college who somehow had it say 172.0.0.1 (the address that means “My Computer”) and they couldn’t figure out how they did it. The implication being that it definitely wasn’t actually coming from their computer.

But I’ve never explored the “dark side” (insert wavy text there) of computing.

---

<div class="post-metadata">

**Author:** ![Lumpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lumpy/32/446_2.png) [@Lumpy](https://boards.straightdope.com/u/Lumpy)\
**Post date:** [April 23, 2016, 1:49am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/96 "2016-04-23T01:49:58Z")

</div>

Finally! Great to be back- I was going through “Dope” withdrawl. 😛

---

<div class="post-metadata">

**Author:** ![ElvisL1ves](https://avatars.discourse-cdn.com/v4/letter/e/5daacb/32.png) [@ElvisL1ves](https://boards.straightdope.com/u/ElvisL1ves)\
**Post date:** [April 23, 2016, 1:54am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/97 "2016-04-23T01:54:34Z")

</div>

My legs! I can’t feel my legs!  
Was this attack from the same fools who keep posting all those live streaming video spam posts?

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [April 23, 2016, 2:07am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/98 "2016-04-23T02:07:31Z")

</div>

> [@BigT](#):
>
> On, ahem, another board, I read a theory that they might have been spoofing their IP address to avoid being easily caught.

From what little I know of these matters, I don’t see what’s to be gained by spoofing an address from a reserved internal block. Better to spoof real addresses and create a confusing trail. If this particular 10._._.\* address is a real internal address, the attack may have come from a server hack.

I just hope and assume that law enforcement authorities are involved, as they should be. This is a commercial site and hacking is no joke.

---

<div class="post-metadata">

**Author:** ![BrainGlutton](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@BrainGlutton](https://boards.straightdope.com/u/BrainGlutton)\
**Post date:** [April 23, 2016, 2:10am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/99 "2016-04-23T02:10:57Z")

</div>

> [@ITD12](#):
>
> The SDMB was the target of a distributed denial of service (DDOS) attack on Thursday 4/21.

:eek: Who would do such a thing to the sweet li’l ol’ innocent ol’ Dope?!

---

<div class="post-metadata">

**Author:** ![jayjay](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jayjay/32/6765_2.png) [@jayjay](https://boards.straightdope.com/u/jayjay)\
**Post date:** [April 23, 2016, 2:13am UTC](https://boards.straightdope.com/t/info-about-the-outage/752843/100 "2016-04-23T02:13:17Z")

</div>

Just adding that the auto-logout and having all threads marked unread (except for my UserCP, in which all of those threads are ALWAYS marked unread) are also happening to me.

[Previous page](https://boards.straightdope.com/t/info-about-the-outage/752843.md?page=4)

[Next page](https://boards.straightdope.com/t/info-about-the-outage/752843.md?page=6)
