Forums

Hi,

Since roughly 2026-07-31 (server-log time), my web app has become extremely slow to start and reload(fail). CPU usage is almost nothing, so this doesn't look like a CPU-quota issue — it looks like the process is waiting on I/O. I'd appreciate help checking whether there's a file-storage / filesystem problem on my account or server.

• Web app: atickorea.pythonanywhere.com
• Server: blue-liveweb9
• Account: ATICKorea (free tier)

1) Startup time jumped ~100× (same code the whole time). From the server log (WSGI app ... ready in N seconds):

| Time (server log) | Startup | |---|---| | 2026-07-30 00:30 | 8 s | | 2026-07-30 00:54 | 3 s | | 2026-07-31 02:04 | 536 s / 439 s | | 2026-07-31 02:57 | 707 s / 822 s / 888 s | | 2026-07-31 04:39 | 918 s / 842 s |

2) CPU usage is almost zero. Dashboard shows 6.92 s of 100 s (6%) used for the day, yet a single startup takes 200–900 s. So the app is not CPU-bound — it's spending that time blocked on I/O, not computing. (Doesn't look like CPU throttling.)

3) Dashboard "File storage:" field is blank — it shows no usage figure at all (normally it shows something like "X MB of 512 MB used").

4) git is very slow too (Bash console), with near-zero user/sys CPU: - git fetch origin (nothing to fetch) → ~22 s - git merge --ff-only origin/main ("Already up to date") → ~4.5 s

5) Reload storm. The log shows many repeated SIGINT/SIGTERM received...killing workers / *** Starting uWSGI *** cycles, with reloads queuing up (e.g. a start stamped "on [04:24]" only actually running at 04:39) because each startup takes minutes.

My app imports WeasyPrint at startup, which loads native libs and scans the fontconfig font cache — very I/O-heavy. When the underlying (network) file storage is slow, that import stalls for minutes while using almost no CPU. Combined with the blank "File storage" figure on the dashboard, this looks like file-storage / filesystem slowness on the server side, not my code or my CPU quota.

Is there a known file-storage / file-server issue affecting blue-liveweb9 (or my account) around 2026-07-31? Is there anything I can do on my end, or can you take a look?

Thanks!

Yeah, I’m also having major issues.

Its been horrible for the last week and I’m this close to ending my subscription.

Thanks for reporting this. Your PythonAnywhere account files are stored on a storage server that is experiencing some issues. It's a new failure mode and we're investigating it now to find a proper fix. Your files and data shouldn't be affected, but there may be degraded performance for your PythonAnywhere-hosted apps and scripts while we're working on a solution.

Apologies for any inconvenience!