Changes Box [Medium] Issue with multiple Box Services

Box: Incident silently edited: [Medium] Issue with multiple Box Services

Silent editNormal progress (typesafe/jev-1.13-20260917, 60%)Changed 2026-11-09 08:13 UTCstspg.io

Summary

Box’s medium-impact incident postmortem now attributes Public API, Downloads, and Box Sign degradation to a focused traffic spike that increased latency for some data assets. It states that additional targeted caching mitigated the impact by relieving datastore stress; the preliminary-information disclaimer was removed.

Machine-written from the diff below (Sol; type: incident edit). Check the diff before relying on it.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what Box removed; blue is what they added. Muted text is unchanged context.

ChangedUpdatepostmortem2026-10-27 21:29 UTC#1

Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed. On October 19, 2026 between 6:44 PM and…

removed On October 19, 2026 between 6:44 PM and…

…returned to normal levels by 8:32 PM PDT. We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. Sincerely, The Box Team…

…returned to normal levels by 8:32 PM PDT. Analysis The issue began in an internal service that provides Metadata to other parts of Box. At 6:44 PM PDT, requests for one widely used Template started taking longer than usual to complete. Services that depend on this information automatically retried the slow requests, which increased the number of requests for that Template by more than twice its normal rate. Once we identified the cause, we began serving the Template from a cache, which reduced the load on the database and restored normal service by 8:32 PM PDT. Background Metadata updates that could not be completed during the incident were processed after service was restored. After mitigation, we identified how to improve the system so that a temporary slowdown does not cause broader degradation. Corrective Actions Box has initiated the following corrective actions: Serving select frequently used Metadata Templates from a cache to reduce load on individual database rows. Updating retry behavior across dependent services so that they backoff more effectively, instead of adding load during a slowdown. Shortening the time requests wait on a slow response so that the system recovers capacity sooner. Increaseing granular obse … Sincerely, The Box Team…

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Oct 27
Before captured 21:34 UTC
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on Oct 28, 00:41 UTC. Record hash c9ba53cf7f889a60…
Download proof

Rewindex captured a newer version after the last checkpoint; the next run (00:41 UTC) commits it.

History of this incident

TodayMonday, November 9Mon, Nov 9

1 rewrite

Normal progress
08:13Edited by the vendor
[Medium] Issue with multiple Box Servicesthis change
Box’s medium-impact incident postmortem now attributes Public API, Downloads, and Box Sign degradation to a focused traffic spike that increased latency for some data assets. It states that additional targeted caching mitigated the impact by relieving datastore stress; the preliminary-information disclaimer was removed.

Tuesday, October 27

1 incident change

Normal progress
21:34Incident
Incident update[Medium] Issue with multiple Box Services

Tuesday, October 20

1 rewrite, 4 incident changes

Normal progress
03:53Incident
Incident update[Medium] Issue with multiple Box Services
Normal progress
03:13Incident
Incident update[Medium] Issue with multiple Box Services
Normal progress
02:43Incident
Incident update[Medium] Issue with multiple Box Services
Wording only
02:33Edited by the vendor
[Medium] Issue with multiple Box Services
Box renamed the incident from “[Medium] Issue with Box Sign and API” to “[Medium] Issue with multiple Box Services,” broadening the title without identifying additional affected services or changing the stated impact level.
Degradation
02:19Major incident
[Medium] Issue with Box Sign and API
Box reported a major-impact issue affecting the Public API and Box Sign, with users potentially seeing errors or timeouts. It started at 2026-10-20 02:19 UTC and was still under investigation when archived, open for 0 min at the last update; no cause or fix was stated.

Cite this

Incident silently edited: [Medium] Issue with multiple Box Services on Box’s status page, changed 2026-11-09 08:13 UTC (change 7 of 7).

Title: Incident silently edited: [Medium] Issue with multiple Box Services
Vendor: Box
Date: 2026-11-09 08:13 UTC
URL: https://rewindex.com/change/rd4743e13b208bf

All Box changes Box profile Markdown JSON