We use privacy-focused hosting service Kyun to host a portion of our infrastructure, which went down on September 16, 2026, due a serious incident on Kyun's side. After a few days of waiting, we decided to redeploy everything to another server.
Most of our infra runs on Spasm, which has easy deployment methods with Docker/Podman and Ansible, as well as scripts for restoring backups, but Session SOGS is pretty outdated, so it only supports old distros like Debian 12 and Ubuntu 22, and restoring a backup is not a trivial task. Anyway, this incident was a great stress test for our infrastructure that allowed us to evaluate our censorship resistance, since our directory, podcast, videos, blog, forum, and Session channel went down.
Here is a full report that explains which parts of our infrastructure survived during an outage (Session, SimpleX, Spasm, Nostr) and how vulnerable they are to censorship.
https://dark.vegas/infra-stress-test-amid-kyun-outage
npub1c7…n5zen
2026-09-28 17:12:19 UTC
Author Public Key
npub1c7atcdzugulqq2x8cufyycs593pmlcg85zl7gfrrgza4gyazcnqsdn5zenSeen on
wss://relay.damus.ioPublished at
2026-09-28 17:12:19 UTCEvent JSON
{
"id": "54e5eee8dc92e2e869a78b34eb224935086187040957085da456955e51525f90",
"pubkey": "c7babc345c473e0028c7c7124262142c43bfe107a0bfe4246340bb5413a2c4c1",
"created_at": 1790615539,
"kind": 1,
"tags": [
[
"spasm_action",
"post"
],
[
"spasm_timestamp",
"1790615539825"
],
[
"license",
"SPDX-License-Identifier: CC0-1.0"
],
[
"spasm_version",
"2.0.0"
],
[
"nostr_spasm_version",
"2.0.0"
],
[
"spasm_category",
"tech"
],
[
"title",
"Infra stress test amid Kyun outage"
],
[
"O",
"spasm_author:0x404a313df99cb82425dccdbb1db07a88b2c165ec",
"spasm_aadd_1"
],
[
"tags_mapping",
"spasm_aadd_1",
"O",
"spasm_author:0x404a313df99cb82425dccdbb1db07a88b2c165ec",
"se2",
"authors.addresses",
"0",
"0",
"slice.13",
"",
"ethereum-pubkey",
"",
"",
""
],
[
"O",
"spasm_author:c7babc345c473e0028c7c7124262142c43bfe107a0bfe4246340bb5413a2c4c1",
"spasm_aadd_1"
],
[
"tags_mapping",
"spasm_aadd_1",
"O",
"spasm_author:c7babc345c473e0028c7c7124262142c43bfe107a0bfe4246340bb5413a2c4c1",
"se2",
"authors.addresses",
"0",
"1",
"slice.13",
"",
"nostr-hex",
"",
"",
""
],
[
"spasm_tips",
"86z3du7h4bokgnawaxygt565spo9sfncunhubyghrxvsfkaxmwyukdafsxygmeceyglrakmptdkvxrlddjq73uoju7l3gtp",
"",
"",
"monero",
"xmr",
"",
""
],
[
"spasm_tips",
"0x404a313df99cb82425dccdbb1db07a88b2c165ec",
"",
"",
"ethereum",
"eth",
"",
""
],
[
"spasm_tips",
"bc1qztekyx3drdmez9694989lldw9t3u9kq3dzldre",
"",
"",
"bitcoin",
"btc",
"",
""
]
],
"content": "We use privacy-focused hosting service Kyun to host a portion of our infrastructure, which went down on September 16, 2026, due a serious incident on Kyun's side. After a few days of waiting, we decided to redeploy everything to another server.\n\nMost of our infra runs on Spasm, which has easy deployment methods with Docker/Podman and Ansible, as well as scripts for restoring backups, but Session SOGS is pretty outdated, so it only supports old distros like Debian 12 and Ubuntu 22, and restoring a backup is not a trivial task. Anyway, this incident was a great stress test for our infrastructure that allowed us to evaluate our censorship resistance, since our directory, podcast, videos, blog, forum, and Session channel went down.\n\nHere is a full report that explains which parts of our infrastructure survived during an outage (Session, SimpleX, Spasm, Nostr) and how vulnerable they are to censorship.\nhttps://dark.vegas/infra-stress-test-amid-kyun-outage",
"sig": "cd1f4ede6b63d61d806494feb813765ad182c538f1f944b951e06999856a4b0d4a6c9baee867c74eb803d713be4a46ca975bcdeaf98575c345cf7af5fb1ec643"
}