Ok, sorry I didn't check this earlier, but I found the _potential_ source for the traffic bursts at least: The probe has accumulated about 642MByte of data in /var/spool/ripe-atlas/data/ so far. It seems a sizeable portion of that data is sent in the POST before the POST fails with the 429 error code, causing a very short traffic spike. And since the data cannot be uploaded successfully, the probe keeps it around for the next upload attempt. And as the uploads apparently keep failing since a few days now, the amount of data to be uploaded keeps growing. So the question is: Why does the upload fail with a 429 "Too many requests" error code ? Cheers, R. On 6/10/26 22:53, via ripe-atlas wrote:

Hi,

I have a software probe that since a few days only is sending very short traffic bursts at very high bitrates (for a probe), amounting to a 5 minute bitrate average nearing 1 Mbit/s.

I _think_ this _may_ have started on or around 2026-06-07, but I don't have detailed logs going back that far anymore (destroyed the container the probe was originally running in, see below, several times in the course of troubleshooting this without saving the logs :-()

When looking into the current logs, I see (as per my understanding) that the POST upload of the measurement data apparently fails with a 429 error, or an occasional "httppost: error reading from server: Connection reset by peer". See below for two instances from the log.

Originally, the probe was running in a container (like most of my other probes as well without issues), then version 5100 natively on Debian 12 x86_64 VPS, just upgraded to 5120 - same result.

Probe ID 1009529.

Any thoughts?

Thanks!

Cheers,

R.

Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: total size in dir: 6254 Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: before getaddrinfo Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: before connect Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: sending request Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/1' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/5' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/2' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/0' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/3' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/6' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/7' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/8' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/4' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/9' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: getting result Jun 10 18:59:25 vps-cbf1 ripe-atlas[173212]: httppost: POST command failed: '429 ' Jun 10 18:59:25 vps-cbf1 ripe-atlas[173212]: httppost: leaving with error Jun 10 18:59:25 vps-cbf1 ripe-atlas[173212]: ooqd: httppost failed with 1

Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: total size in dir: 6254 Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: before getaddrinfo Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: before connect Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: sending request Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/1' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/5' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/2' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/0' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/3' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/6' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/7' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/8' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/4' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ ripe-atlas/data/out/ooq/9' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: getting result Jun 10 18:57:25 vps-cbf1 ripe-atlas[173212]: httppost: error reading from server: Connection reset by peer Jun 10 18:57:25 vps-cbf1 ripe-atlas[173212]: httppost: leaving with error Jun 10 18:57:25 vps-cbf1 ripe-atlas[173212]: ooqd: httppost failed with 1

----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe- atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/ mailman-3-migration/