CURRENT MISSION: Conclude the 2026 soyjak.party hack page, aswell as any pages relating to it, such as the Summer 2026 Crisis page.
Update Quotecord with any relevant info. See the blackboard for more info.

2026 Soysphere outage

From Soyjak Wiki, the free ensoyclopedia
Revision as of 06:17, 9 August 2026 by TheCatalan1977 (talk | contribs)
Jump to navigationJump to search
>Though maybe you were looking for Second Splintered Age?
🤣 Rest in piss, 2026 Soysphere outage 🤣Smoking that 2026 Soysphere outage pack tonight. 💯
This may have been a DDOS attack, as some were still able to use the site for about 10 seconds before the Cloudflare error.
Some images were lost due to a disk transfer failure and weren't properly archived
>Error 1033 Cloudflare Tunnel Error

>Error creating thumbnail: File missing

The 2026 outage, also called Soypocalypse 2, was a Soysphere-wide outage that started on August 5, 2026, almost three years after the first Soypocalypse. All official Soysphere sites except irc.soyjak.st and status.soyjak.st abruptly went offline. The event caused mass panic due to its length, causing fears of Quote having just shut it down to run rampant. On August 5, around 18:00 UTC, the Sharty and Soyjak Wiki went down due to unknown reasons, showing a 404 error. Shortly afterward, SoyBooru would also go down, bringing the entire Soysphere offline. All three sites suffered from a Cloudflare Tunnel error.[a] For months before this, the Soysphere would suffer relatively short-term downtime due to Cloudflare brapping with either a 1033 or 502 error, usually lasting from 1-5 minutes, but nobody expected the Soysphere to be down for so long. Quote and Mustard said on the Boorum that this was due to a disk drive failure so as a result the servers had to be transferred.[1]

Context

Fears that Quote intended to JSID stemmed from January 28, better known as the Cacacaust, where Quote said: >Once I've had enough I'm going to JSID instead of passing it on or selling it. Quote later clarified that he did not intend to do so "any time soon"; this still left ambiguity.

Shutdown

Around August 5, 18:00 UTC, the Sharty and Wiki suddenly went down, showing 404 errors whenever you attempted to access them. Users noticed this on the booru,[2] and while some panic ensued, nothing major was coming out of it. An Hour Later, The Sharty was briefly back up before it suddenly went down again, This continued until new comments and posts on SoyBooru started failing, showing "integrity_token_missing" whenever you attempted to post. Before long, all three sites showed a Cloudflare Tunnel error, and only the IRC remained.

Do xhey really?
Xhey really dont!!!
The ban message you would get trying to join the IRC at the time.[b]

Confusion set in, and people started flooding into the IRC, looking for answers on why the entire Soysphere seemed to be down. The situation flooded the IRC, and channels were quickly heavily moderated as people flooded in. At one point, close to everyone connected or trying connect received a message saying they were banned and unable to connect to the IRC.[Does anyone know when this was + duration] Eventually, the IRC was gigaraped by splinter ads, causing a clitty-leaking admin to G-line (network ban) everyone that attempted to join. As things calmed down, it became clear that this shutdown was intentional, and people instinctively started rumors that Quote had shut it down without anyone noticing. Mustard was the only admin active at the time, and was notified about the situation at 21:00 UTC. Soyteens were faced with the choice of staying in the IRC and waiting it out, posting on platforms like the Shroom or the Swinny, taking a torch to the Shiwi or finally going outside after spending so much time posting on the Sharty.

SWINNY PPH THROUGH THE ROOF NIGGAAAAAA [3]
The supposed "evidence" that Quote intended to shut it down. It's not even correct admins have a ~ at the start of their names not + KEKK

Mustard hinted at server issues on August 6, 8:01 UTC, on the Sharty's thread in Kiwi Farms,[4] and confirmed that Quote had been "AFK for 6 days" and that he had "no clue" what had happened or when it would come back.[5]

a24.ct.ws

One of the splinter sites being advertised during the IRC giga-rape was a24.ct.ws, also known by the Arty, even doe nophono says this. It was created by a Swede named "Aoot", hosting the bunker site on InfinityFree, running a modified version of Vichan. Before the gigarape, it was advertised on the Swinny back when the site was created. But during that gigarape, some 'teens actually flocked to the site and used it as a bunker. /soy/ reached a peak of 77 PPH during its life and after the Janny applications closed. Right after, the site got raided by the Kuzzy and the Chaddy, another splinter site, though it was mostly thread spam. A new board gets added called /meta/, it got around 20 posts before getting shut down. KEK. Someone asked on /soy/ if there was a soysona for Aoot, and there was - it was just the A24 'jak coloured red. But someone actually made AI trans porn of the soysona. Shortly after, the site got temporarily shut down due to a rogue janny, but it was back up[6] until the owner just shut it down.

Archives

soyposter.party

Another splinter advertised during this time was soyposter.party. Also running Vichan, it had a /soy/ and /qa/ board, and a lax set of rules. It was advertised aggresively on the Swinny, but some 'teens actually used it as a bunker even though you couldn't even attach multiple images. The site soon got targeted and raped by the Chaddy due to a call for action being made against the splinter. They started threadspamming and even ended up stealing the 100th post on the site's /soy/ board, although the jannies were quick to mop it up. They would then rape the site further, taking it down for a bit and spamming the log. /soy/ was active due to being shilled on the swinny and all of the rape, but /qa/ was neglected, only having 7 posts in total. This site, even with it being actually hosted on a real server, proved rather undeveloped compared to the Arty, and will probably be forgotten about immediately after this kek.

Archives

SoyBooru returns

Around August 6, 13:00 UTC, SoyBooru was revived but non-functional for about an hour due to the server's browser validation responding Error 429 "Too Many Requests". The server went down again multiple times, responding this time with a Cloudflare Error 502. Within an hour, the site became operational and the first post-shutdown post[7] was made during this time. Shortly afterward, the Sharty and Soyjak Wiki began to display Error 502 as well. Some users were able to load their caches of random wiki pages, leading to confusion as to whether it had come back or not.

Quote would shortly after respond to users asking about what had happened, saying that the "server transfer isn't finished yet",[8] which led to confusion, and he refused to elaborate on what he meant, only responding to a question about whether Mustard was acquiring the server, answering "Nope".[9] Through the rest of the day, the Sharty and wiki remained down.

On August 7, at 4:02 UTC, Mustard mentioned on the IRC that his "SSH access is broken" but did not elaborate further. During this time, however, he was able to add new features to the Booru such as readding the "Favored by" slider and making tags sorted in alphabetical order.[10]

Wiki returns

>OH MY FAUCI THIS IS JUST LIKE MUH ED WEBSITE ERRORS!!!1!

On August 7, at 7:20 UTC, the wiki came back online, hosted on wikitest.soyjak.soy and wiki.soyjak.st briefly before being put back on the current domain, but with a few caveats - all images uploaded from June 8 onwards were lost due to disk failures, causing a lot of pages to be broken and configuration info to spill out of thumbnails. A sitewide campaign, akin to the "Undo the Gradingcaust" campaign, has commenced in light of this.

Reupload all of the lost images and media from June 8 onward [sic].
Please name your files as "Reuploaded" with the orginal name so the lost files can be overwritten with their orginal names by a helper or above [sic]

Sharty returns

The sharty returns.... and Quote is dead. A new owner has taken the Sphere!

Affected splinters sites

If the Soysphere dying wasn't enough, splinters also got affected by the outage, including:

This splinter had the largest BRAP of all, with an outstanding 500+ PPH and 8000 PPD. The site got DDoSed (possibly by Quote himself) but stayed online with a few more BRAPs.
Swinny achieved a PPH of 2010 by spam threads🗝️[11]

Theories

As the outage continues, there have been a plethora of theories as to why the outage occurred. Most of the theories provided are baseless and are just speculation, but some do have merit to them.

Some theories include:

  • Quote faked an outage to wipe as much evidence concerning the Furcord leaks, as all media from June 8th and after have been lost here on the 'ki.
  • The same foodists who were DDoS-ing KiwiFarms are now DDoS-ing the Sharty out of boredom.
  • There was a sudden influx of new users onto the Sharty, which overwhelmed the servers and caused an HTTPS Error code 429 (Too Many Requests).
  • Cloudflare pulled the plug on the Sharty.
  • A solar particle switched an integer inside the Sharty servers and caused it to brap, just like my heckin' Super Mario 64 or something like that.

Notes

  1. ↑ 1033 does not mean Cloudflare was at fault. There is no indication that any of the downtime was caused by issues relating to Cloudflare by itself.
  2. ↑ The ban message was different for already-joined 'teens and nusois.

Snopes

  1. ↑
    Quotes response to questions about the Sharty outage on the Boorum.
  2. ↑ https://soybooru.com/forum/gen/thread/42235
  3. ↑ https://megalodon.jp/2026-0809-0547-23/https://swedishwin.com:443/stats.html
  4. ↑ https://kiwifarms.st/threads/soyjak-party-the-sharty.145349/page-5471#post-25175802
  5. ↑ https://kiwifarms.st/threads/soyjak-party-the-sharty.145349/post-25175921
  6. ↑ https://megalodon.jp/2026-0808-0447-32/https://a24.ct.ws:443/soy/thread/271.html
  7. ↑ https://soybooru.com/post/view/271589
  8. ↑ https://soybooru.com/forum/gen/thread/42263?page=2#p1785636
  9. ↑ https://soybooru.com/forum/gen/thread/42263?page=3#p1785668
  10. ↑ https://soybooru.com/forum/meta/thread/968?page=4#p1793225
  11. ↑ https://megalodon.jp/2026-0809-0547-23/https://swedishwin.com:443/stats.html
2026 Soysphere outage
is part of a series on
SHUTTING DOWN SOYJAK.PARTY

>SHUT IT DOWN! SHUT IT DOWN!
Entities that want to shut down Soyjak.st [-+]
 "(You) are ze puppet, und I'm ze puppeteer!"
Tactics used to shut down Soyjak.st [-+]
Major events [-+]

2026 Soysphere outage
is part of a series on
Quote

V • T • E

"Once I've had enough I'm going to JSID instead of passing it on or selling it."

Related Figures and Entities

Quote (detractor perspective | caveman perspective) ♦ BBQ Sauce† ♦ Broot† ♦ Cobblestone† ♦ Froot† ♦ Limeade† ♦ Mustard ♦ Soysneed† ♦ Root† ♦ Warrior-Z

Major Events and Controversies

1/28 or Cacacaust ♦ acking of /nate/ ♦ /bpa/ ♦ Brownocaust ♦ February 2026 crisis (QLMJEYLA) ♦ Great Handover ♦ Second Soyanniversary ♦ Limeade leak ♦ Nuuru ♦ Pride Month ♦ Quotecord ♦ Soybooru Crisis ♦ Wikifur incident ♦ Seventh Soysurgency ♦ 2026 outage

Enemies of Quote

Cacas ♦ HTSMs ♦ Shiwi ♦ Swinny

Retrieved from "https://soyjakwiki.org/index.php?title=2026_Soysphere_outage&oldid=462254"