Hi,
Our web app runs on Cloudflare Workers. It reads and writes files in users' Dropbox through the HTTP API: files/download and files/upload on content.dropboxapi.com, and files/get_metadata on api.dropboxapi.com. Almost all of our users are in Japan.
On 2026-10-13, between 15:00 and 20:00 UTC, every request became slower by a fixed amount. It has not recovered as of 2026-11-08:
- content.dropboxapi.com: about +430 to +580 ms per request
- api.dropboxapi.com: about +80 ms per request
Weekly medians, before -> after:
- files/get_metadata: 197-206 ms -> 277-285 ms
- files/download (small file): 404 ms -> 831 ms
- files/upload, under 100 KB: 817 ms -> 1,465 ms
- files/upload, 100 KB-1 MB: 875 ms -> 1,395 ms
- files/upload, 1-5 MB: 1,029 ms -> 1,529 ms
- files/upload, 5-15 MB: 1,207 ms -> 1,666 ms
- files/upload, 15 MB and over: 2,099 ms -> 2,478 ms
What we checked:
- The extra time is about the same for every file size, at every hour of the day, and for each of our 16 most active users (+0.4 to +0.6 s). It looks like a fixed cost per request, not bandwidth or load.
- We deployed nothing in that window. Our last deploy before it finished at 02:09 UTC on Oct 13; the next one was at 04:19 UTC on Oct 14.
- Calls from the same Worker to other services (Club Log in the UK, QRZ.com in the US) did not get slower.
- We ran a Worker in Cloudflare's Tokyo location (NRT). A TCP connection to your Tokyo edge (162.125.80.14 for content, 162.125.80.19 for api) takes 1-10 ms. An unauthenticated request is rejected with 401 in 160-240 ms (content) and 151-165 ms (api). So the network path to your edge looks fine; the extra time only appears on real, authenticated downloads and uploads.
- Responses from content.dropboxapi.com carry "x-dropbox-response-origin: far_remote"; responses from api.dropboxapi.com carry "remote". We see the same values from a home internet connection in Japan. Older reports from other people show this header too, so we are not sure it is new.
Questions:
- Was there a change around 2026-10-13 15:00-20:00 UTC in how requests to content.dropboxapi.com that arrive at the Tokyo edge are handled or routed?
- What does "x-dropbox-response-origin: far_remote" mean? Can an app do anything to be served from a closer location?
- Is there anything else we should check or send? If it helps, we can capture x-dropbox-request-id values for slow requests and share them privately.
Thank you.