# Processing times

**URL:** <https://forum.mapillary.com/t/processing-times/9871>\
**Category:** Contributing and equipment\
**Created:** [August 14, 2025, 1:34pm UTC](https://forum.mapillary.com/t/processing-times/9871 "2025-08-14T13:34:00Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![tao](https://avatars.discourse-cdn.com/v4/letter/t/f9ae1b/32.png) [@tao](https://forum.mapillary.com/u/tao)\
**Post date:** [September 8, 2025, 8:07pm UTC](https://forum.mapillary.com/t/processing-times/9871/21 "2025-09-08T20:07:34Z")

</div>

Hey eserte, what does your API query look like and what’s expected?

---

<div class="post-metadata">

**Author:** ![eserte](https://avatars.discourse-cdn.com/v4/letter/e/67e7ee/32.png) [@eserte](https://forum.mapillary.com/u/eserte)\
**Post date:** [September 8, 2025, 9:17pm UTC](https://forum.mapillary.com/t/processing-times/9871/22 "2025-09-08T21:17:11Z")

</div>

I try to fetch all images of one day (or smaller time periods) in the Berlin area, something I do every day since the v4 API exists, and it works most of the time (exceptions are always caused by Facebook or Mapillary breakage). Request looks like this:

```auto
GET https://graph.mapillary.com/images?fields=id,creator,make,geometry,captured_at,sequence&bbox=13.051179,52.337621,13.764158,52.689878&start_captured_at=2025-08-27T22:00:00Z&end_captured_at=2025-08-28T22:00:00Z

```

I do not expect this response:

```auto
{"data":[]}

```

Yes, there are images in this area in the last 11-12 days available.

Just curious: what do your health checks tell about the API health?

---

<div class="post-metadata">

**Author:** ![knikel](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@knikel](https://forum.mapillary.com/u/knikel)\
**Post date:** [September 9, 2025, 7:19am UTC](https://forum.mapillary.com/t/processing-times/9871/23 "2025-09-09T07:19:16Z")

</div>

Hey everyone, apologies for the issues. We’re working on replacing underlying spatial indexing service - as you see, the current one is not very reliable. We’re likely to add some spatial contstraing (area of box/bing tile level/s2 cell level), to ensure the new service remains stable. I’ll come back to this thread once I have more updates. Apologies for the hiccups.

---

<div class="post-metadata">

**Author:** ![Welop7257](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/welop7257/32/73588_2.png) [@Welop7257](https://forum.mapillary.com/u/Welop7257)\
**Post date:** [September 11, 2025, 1:11pm UTC](https://forum.mapillary.com/t/processing-times/9871/24 "2025-09-11T13:11:46Z")

</div>

Appreciate the update, knikel. I can attest to issues on my end as well. Couple sequences from a recent trip are stuck in the permanent “Processing X captures from September 8”. while later ones were processed without issues. Same stuck-in-processing sequences have also disappeared from my Android app. All the best of luck on continuing to work on this!

---

<div class="post-metadata">

**Author:** ![eserte](https://avatars.discourse-cdn.com/v4/letter/e/67e7ee/32.png) [@eserte](https://forum.mapillary.com/u/eserte)\
**Post date:** [September 25, 2025, 6:20pm UTC](https://forum.mapillary.com/t/processing-times/9871/25 "2025-09-25T18:20:23Z")

</div>

Is it stuck again? The API hasn’t returned any new data since last Monday.

[Previous page](https://forum.mapillary.com/t/processing-times/9871.md?page=1)