# Atlas Parallel Running Quota

**URL:** <https://forum.ripe.net/t/atlas-parallel-running-quota/1363>\
**Category:** RIPE Atlas\
**Created:** [9 March 2025 23:50 UTC](https://forum.ripe.net/t/atlas-parallel-running-quota/1363 "2025-03-09T23:50:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Read](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/jason_read/32/667_2.png) [@Jason\_Read](https://forum.ripe.net/u/Jason_Read)\
**Post date:** [9 March 2025 23:50 UTC](https://forum.ripe.net/t/atlas-parallel-running-quota/1363/1 "2025-03-09T23:50:46Z")

</div>

I’m working on graduate research related to the reliability of hyperscale cloud platforms. I use Ripe Atlas to monitor network reachability using many short duration ping and DNS measurements. With only 1-2 probes, these tests complete in \< 30s typically.

I began hitting the parallel running measurements quota (max 100). From what I can tell, it seems that once you start a measurement, there is a minimum time it will count against the quota - maybe in the 5-10 minute range. Is there any guidance on what this duration is?

---

<div class="post-metadata">

**Author:** ![camin](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/camin/32/243_2.png) [@camin](https://forum.ripe.net/u/camin)\
**Post date:** [10 March 2025 11:22 UTC](https://forum.ripe.net/t/atlas-parallel-running-quota/1363/2 "2025-03-10T11:22:06Z")

</div>

So the notional duration for a oneoff is indeed 5 minutes, but that’s complicated by the fact that the process which “stops” them only runs every 5 minutes, which gives you the 5-10 minute range. We have an upcoming change that will reduce that to 5-6 minutes.

If you’re willing to share details of your research campaign with me (camin at- symbol [ripe.net](http://ripe.net)) then we can discuss ways of making it work better, potentially temporarily increasing your concurrent measurement limit.