Part of the contributor base could not upload.
One upload server was having problems. A storage array needed restoration work. While that happened, two people were looking for a way to move the affected contributors onto another server.
That was the incident in three lines.
The contributor impact made it urgent. A portion of the people trying to send us content could not do it. The message did not call the entire site down. It said exactly which part was broken for which group.
The recovery work was already split. One person was overseeing the storage restoration. Two others were investigating whether the affected contributors could be moved. I sent the update and said I would follow up when we had a more concrete outline for full service restoration.
The first message did not guess at a restoration time. We did not yet know enough.
We did not have a known root cause or a finished restoration. We knew about the upload-server issue, the contributor impact, and the work underway. That was the available picture.
The storage work and the attempt to move contributors were both still in progress when I wrote. Neither path was done.
For now, the honest update was short. Part of the contributor base could not upload. The team was restoring storage and looking for another route. I would send more when the restoration plan became concrete.
Restore the storage. See who we can move. Update everyone when the path to full service is concrete.
That was the job in front of us.