Snapshot 156020

Document
Status page
URL
https://status.pruna.ai/
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
browser
Size
1276805 bytes
SHA-256 (raw)
b6b323aabf1bfd17312e7adabe8e373e75121e741292500e527aba9334e070b3
SHA-256 (normalized text)
d11d763b13110140b1bca7299eef422ab5d4f3751f802c00bc12d2aeead97125

Normalized text

Scripts and page chrome removed; this is what change detection compares.

We are fully operational
We’re not aware of any issues affecting our systems.
Systems
September - October
Prun AI API status page
100% uptime
History
2026
October
Prun AI API status page
Incident
File uploads to /v1/files rejected with "Non-UTF8 input" error Fix: we removed the rule from /v1/files, and uploads work again. Affected customers have confirmed this. Prevention: we are adding a monitor that uploads a binary file, so the status page catches and shows this kind of failure.
5 days ago
File uploads to /v1/files rejected with "Non-UTF8 input" error Resolved. From 14 October 16:03 UTC to about 15 October 03:00 UTC (around 11 hours), file uploads to the Pruna AI API failed with a "Non-UTF8 input" error. Models that take an uploaded file, such as p-video/replace, could not be used during this window. Other prediction requests were not affected.
5 days ago
Powered by
bastion