As was Facebook, uses the same servers. An auth/user issue
Try again..
This is to encourage you to upload 4 million new photos⌠
I missed this topic. I assume it works at this point, or at least I canât reproduce it on my end. Also, I think we had some infrastructure issues a few days ago; I believe this might be related.
__
BR, Yaro
FYIO @Yaro
The Mapillary access failure was username related. ie some kind of login/auth issue. In my case the failure period dovetailed with that of a username login/auth failure of Facebook, so I think it was related. Both were offline for me between 2 and 4 hours.
Working fine now.
Cheers
It is very fast now, but I have to retry the whole time.
I must confess that I have troubles with my computer.
It often reloads the same sequence.
So I donât know if everything will have been uploaded. I doubt it.
You have a very advanced processor! It is called Speculative Execution. 
Mapillary down!! Yet, some files were uploaded; started some 8 hours ago with like 60GB; looked to start second series upload some 3 hours ago (didnât jot down much, as 90% asleep at that time); current upload (third attempt, at 8am Brussels time) EDIT: of the second (smaller) series also failed; END OF EDIT obviously, something must have gotten through, then something decided to drop the line.
Current state, at 08u15 EDIT: at 08u45 END OF EDIT Brussels time: âUpload failedâ , âunable to connect to Mapillary âŚâ
= = =
And, like Philipâs post: not able to copy/paste whatâs in the tiny log pop-up window.
>> Feature request for Mapillary Windows uploader:
1/ a resizable log window, and
2/ copy/paste whatâs in that window
= = =
Rather than post five screenshots of whatâs in the tiny log window: which of the following files would be of interest to hunt down this continuing problem, please?
Met als immer vriendelijke groet (Dutch for âwith as ever friendly greetingâ),
I will take a look at it ASAP, thank you for the report.
__
BR, Yaro
I see some minor issues in uploading, but in general the service looks stable (so normal operational retries because of network, etc). So the issue is more subtle (or somewhere else). At this point, I need to take a look at our uploader itself. It takes some time, but it is moving somewhere 
Separately, I will create new feature requests reported by @koninklijke
__
BR, Yaro
Generally speaking, ISPs sometimes have troubles too.
For the latest Desktop Uploader session log.log is your friend. 
Every next session accumulates previous log content in log.old.log, so you can delete it from time to time.
Upload isnât working no matter how often I try:
16:09:43.422 - INFO - ==> Uploading...
Uploading IMAGE (1/1): 8%|ââ | 291M/3.46G [00:00<00:07, 444MB/s]16:10:02.516 - WARNING - Error uploading sequence_0/IMG_20260711_145250_00_035.jpg at offset=10557427 since begin_offset=0: HTTPError: 400 Client Error: Bad Request for url: https://rupload.facebook.com/mapillary_public_uploads/mly_tools_1584d6ffccdd87d8f08738d0761b788e.jpg
16:10:04.680 - WARNING - Error uploading sequence_0/IMG_20260711_144904_00_011.jpg at offset=8424372 since begin_offset=0: HTTPError: 400 Client Error: Bad Request for url: https://rupload.facebook.com/mapillary_public_uploads/mly_tools_c07a5fe16c6b6ae245f1e92ce7fd0c12.jpg
16:10:07.356 - WARNING - Error uploading sequence_0/IMG_20260711_145115_00_025.jpg at offset=10478557 since begin_offset=0: HTTPError: 400 Client Error: Bad Request for url: https://rupload.facebook.com/mapillary_public_uploads/mly_tools_150f607674d2230717d0d7e6f1f32a46.jpg
16:10:08.863 - WARNING - Error uploading sequence_0/IMG_20260711_145259_00_036.jpg at offset=9991394 since begin_offset=0: HTTPError: 400 Client Error: Bad Request for url: https://rupload.facebook.com/mapillary_public_uploads/mly_tools_3d9c34d6f2950ae8942e7390faa0ade0.jpg
Uploading IMAGE (1/1): 8%|ââ | 291M/3.46G [00:11<02:10, 26.1MB/s]
16:10:09.185 - INFO - ==> Upload summary
16:10:09.186 - INFO - Nothing uploaded. Bye.
Upload servers in specific regions may be offline. 
Though, upload requests should be automatically redirect to online servers in other regions (data centers). But, it takes some time for client DNS caches to expire depending on TTLs. You should be able to shorten this period of time by flushing your DNS cache explicitly.
On Windows:
ipconfig /flushdns
On Linux distros employing Systemd:
resolvectl flush-caches
Sometimes, Wi-Fi routers are used as local (relay) DNS servers, so you would need to either wait for the Wi-Fi routerâs DNS cache to expire or manually flush/reset the Wi-Fi routerâs DNS cache explicitly.
Here the same 
No result.
Apology for the late response; weâre looking at the issue (since morning), and it looks like it is deep in the infra side. It is hard to catch as it is flaky as well (so sometimes it gets through, sometimes it doensât). I donât see any workaround for now.
__
BR, Yaro
The issue has been identified and is currently being fixed and verified. The impact was that around 10% of uploads got errors (no data loss, the error was very early on uploading), and more checks will follow once everything is mitigated. I will provide the next update tomorrow, have a good night everyone and thank you for your patience!
__
BR, Yaro