ℹ️ **平台技术迁移：** LessWrong 正在从 AWS 迁移至 Vercel，并同步进行代码库向 NextJS 的升级。此次技术调整旨在优化平台性能和用户体验，但可能在短期内引入新的技术挑战。

⚠️ **潜在用户体验影响：** 迁移过程中，用户可能会遇到一些暂时的 bug、操作上的不流畅或页面加载速度的波动。平台承认这些潜在问题，并呼吁用户保持理解。

📢 **问题反馈机制：** LessWrong 提供了便捷的问题反馈渠道。用户可以通过屏幕右下角的 Intercom 图标或直接在相关帖子下留言报告 bug。详细描述问题发生的时间和操作步骤将有助于平台快速定位和解决问题。

🔄 **风险控制与回滚计划：** 平台已为 DNS 切换设置了较短的 TTL 值（60秒）以减少潜在的停机时间。若在迁移过程中出现严重问题，LessWrong 保留随时回滚至先前状态的权利，以确保服务的稳定性。

Published on September 13, 2025 3:59 AM GMT

LessWrong is currently in the process of migrating from AWS to Vercel, as part of a project to migrate our codebase to NextJS^[1].  This post should go live shortly after we cut over traffic to the new host (and updated codebase).  This should hopefully be a pretty low-risk operation.  If all goes well, we plan on doing the DNS cutover next week, which is a higher-risk^[2] operation.  (If we notice something terribly wrong we might roll back without warning.)

This is all to say that there's a higher-than-usual chance that you'll run into some new bugs, bumpiness, or performance degradation^[3] in the next few days.  If you do, please report them to us.  The best way to do this via Intercom.  You should^[4] see this icon in the bottom-right corner of your screen:

You can also leave a comment on this post.

Bug reports ideally include "when did you first encouter the bug" and "what were you doing at the time", but don't worry about writing an essay, if we have questions we'll just ask.

You should feel free to report pre-existing bugs, just please let us know if you're reporting a bug which you're pretty sure was around before today.

1. ^{^}

   "Why" is a longer story that we might get into in the comments if people are curious.

2. ^{^}

   If something goes wrong here, some fraction of users might see downtime on the order of an hour, if they happen to be behind some piece of infrastructure which doesn't honor short DNS TTLs.  (We've ensured that the DNS TTL is set to 60 seconds a few days ahead of time.)

3. ^{^}

   I expect a moderate performance hit for e.g. initially loading the front page on a new tab, maybe on the order of 20-30%, at least until we get around to optimizing that harder.  If you're on a fast internet connection, this should hopefully not be very noticeable - our median front page load is under 1 second.  If you run into something that seems to take longer than it used to, in a way that's perceptible to you, please err on the side of letting us know.  It might end up being nothing, or might be too costly to fix in the short-term, but we can't perform triage if we don't know about the problems in the first place.

4. ^{^}

   Unless you've hidden it in your account settings.