Elevated upload latency in Frankfurt
Resolved after 47 minutes. One storage node was rebuilt after a disk controller fault; writes were served by the remaining two nodes throughout and no objects were lost. Reads were unaffected.
System status
Updated continuously from internal health checks.
API — app.freeshka.orgOperational
S3 endpoint — s3.freeshka.orgOperational
Delivery cache — cdn.freeshka.orgOperational
Storage — Amsterdam (ams)Operational
Storage — Frankfurt (fra)Operational
Past incidents
Cache misses on newly written objects
Resolved after 22 minutes. A configuration push shortened the negative cache window; objects written during the window returned 404 from the delivery endpoint for up to a minute after upload. The API itself was correct throughout.
Maintenance
Planned work is announced here at least five days ahead and is scheduled between 02:00 and 05:00 UTC. Nothing is currently scheduled.