# Monthly probe report wrong

**URL:** <https://forum.ripe.net/t/monthly-probe-report-wrong/1802>\
**Category:** RIPE Atlas\
**Tags:** troubleshooting\
**Created:** [1 September 2026 07:42 UTC](https://forum.ripe.net/t/monthly-probe-report-wrong/1802 "2026-09-01T07:42:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tschaefer](https://avatars.discourse-cdn.com/v4/letter/t/a9a28c/32.png) [@tschaefer](https://forum.ripe.net/u/tschaefer)\
**Post date:** [1 September 2026 07:42 UTC](https://forum.ripe.net/t/monthly-probe-report-wrong/1802/1 "2026-09-01T07:42:50Z")

</div>

For probe #1000568 the monthly report states disconnected time: 12d 17:12.

while I can’t find such long disconnected times in the portal:

> **[RIPE Atlas - RIPE Network Coordination Centre](https://atlas.ripe.net/probes/1000568/network)**
>
> RIPE Atlas is the RIPE NCC's main Internet data measurement system.

Probably some thing went wrong here. Total availability: 58.98% isn’t true for that probe during the last month.

Calculation interval: 2026-08-01 00:00:00 - 2026-09-01 00:00:00  
Total connected time: 18d 06:47  
Total disconnected time: 12d 17:12  
Total availability: 58.98%

---

<div class="post-metadata">

**Author:** ![jterbeest](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/jterbeest/32/30_2.png) [@jterbeest](https://forum.ripe.net/u/jterbeest)\
**Post date:** [19 September 2026 13:47 UTC](https://forum.ripe.net/t/monthly-probe-report-wrong/1802/2 "2026-09-19T13:47:37Z")

</div>

Hi,

Apologies for the late response. The connect that happened in early August was missed by the system so for the report we did not see it connected again until the next disconnect → connect events which happened on August 13.

I’ll check a bit more next week but it seems this only affected the report data. I’ll see if I can avoid this for future reports.

Kind regards,  
Johan ter Beest  
RIPE Atlas Team