Hello,
my probe 1007423 is online, however it does not appear to do any
measurements (which is a silent failure one only notices when trying
to use it's own probe unfortunately).
It's running on OpenWRT 23.05.3 (installed atlas-sw-probe package).
I'm not sure since when this is happening.
On Fri, 12 Jan 2024 at 11:34, Johan ter Beest wrote:
>
> Hi Lukas,
>
> I looked into this briefly and the system notified you because for some
> reason we did not charge you for those measurements until January 10th.
Ah, so it's a 3 step process; actual measurement -> accounting ->
notifications
ast 48 hours as well?
This is not a first, I got many of those erroneous messages in the past.
Thanks,
Lukas
-- Forwarded message -
From: RIPE Atlas
Date: Thu, 11 Jan 2024 at 02:56
Subject: Your credits are decreasing dramatically!
To: Lukas Tribus
Dear RIPE Atlas
Hello,
FYI HE's new "supertraceroute" exposes ATLAS traceroute functionality
to the public:
https://bgp.he.net/traceroute/
Other sources are (NLNOG) RING nodes and other projects.
Interesting approach, not sure if I should be happy about this, but I
guess HE is paying for it with Atlas
bution
> maintainers who are willing to help do the same for Debian. OpenWRT is also
> something I’ll be looking at.
>
> Short and simple. Master contains the latest production code. Use it in good
> health :)
>
> Cheers,
>
> Michel
>
> On 4 Jun 2023, at 20:03, Lukas Tribu
Hello Michel,
On Sun, 12 Feb 2023 at 22:51, Michel Stam wrote:
>
> Hello Randy,
>
> We are currently actually looking at providing packages for other
> distributions, through
> the regular repositories of the distribution. However that means we have to
> work pieces
> of the software probe to
On Mon, 30 Jan 2023 at 17:34, Ernst J. Oud wrote:
>
> Lukas,
>
> Keep in mind that - as I experienced - any VM or Docker container introduces
> some problems, such as higher latency. My CentOS VM has 2 ms. higher
> latency in the first hop compared to a v5 probe on the same fiber.
Any
On Mon, 30 Jan 2023 at 13:34, Robert Kisteleki wrote:
>
> Hi,
>
> To me it seems that there are oh-so-many ways of packaging and
> distributing this software to the match the multitude of needs (RPMs,
> DEBs, openwrt, docker, VMs, ...) and us giving support to multitude of
> these stretches our
Hello,
On Thu, 29 Dec 2022 at 15:15, Stephane Bortzmeyer wrote:
>
> On Tue, Dec 20, 2022 at 05:48:08PM +0100,
> Lukas Tribus wrote
> a message of 60 lines which said:
>
> > - where have those security concerns been previously discussed?
>
> Several times on thi
Hello,
On Fri, 16 Dec 2022 at 14:15, Hugo Salgado wrote:
> Dear Robert,
> As I have expressed at other times, I think we have to be very careful
> with enabling HTTP probes due to traffic increase issues.
>
> I have personally delivered quite a few probes to remote locations
> in regions with
Hello,
On Tue, 20 Dec 2022 at 14:38, wrote:
> But maybe there's another way, to select which one of those providers/CDNs to
> measure?
> Instead of manually selecting them, there could be some sort of "threshold"
> which a
> provider/CDN has to reach
One layer of indirection doesn't solve
On Mon, 14 Mar 2022 at 13:17, Stephane Bortzmeyer wrote:
>
> On Mon, Mar 14, 2022 at 10:26:46PM +1100,
> Jen Linkova wrote
> a message of 37 lines which said:
>
> > It is. Facebook is officially blocked in Russia [1]
> >
> > [1] https://rkn.gov.ru/news/rsoc/news74156.htm
>
> I know but I was
On Sun, 30 May 2021 at 14:49, Lukas Tribus wrote:
>
> Hello,
>
> On Sun, 30 May 2021 at 14:39, Stephane Bortzmeyer wrote:
> > > To reproduce, just try to resolve zoom.us or google.us against 8.8.8.8
> > > or 1.1.1.1 on your probe.
> >
> > It works and
Hello,
On Sun, 30 May 2021 at 14:39, Stephane Bortzmeyer wrote:
> > To reproduce, just try to resolve zoom.us or google.us against 8.8.8.8
> > or 1.1.1.1 on your probe.
>
> It works and I don't see one SERVFAIL:
>
> % blaeu-resolve --requested 100 --area North-Central --nameserver 8.8.8.8
>
Dear list,
while troubleshooting DNS issues on the Google network yesterday [1]
we found that RIPE Atlas probes did not recover after Google fixed the
issue, we kept seeing SERVFAIL answers on the RIPE Atlas probes.
We now know that those ATLAS results are bogus.
For example google.us against
15 matches
Mail list logo
