Discussie m.b.t. RIPE Atlas en Globalping

[neeecht]

https://dash.globalping.io/
Your probe went offline
Oct 25, 2025, 2:00 AM

Ik kan de probe wel pingen. Wat nu?
Modem opnieuw opgestart, probe opnieuw opgestart.

Maakt mij verder weinig uit, deed het voor de fun/om te helpen.
Mocht iemand nog tips hebben, zonder gedoe, hoor ik het graag.

[ernstoud]

Ticket maken op GitHub?

https://github.com/jsdelivr/globalping/issues

[neeecht]

ernstoud schreef op maandag 27 oktober 2025 @ 02:23:
Ticket maken op GitHub?

https://github.com/jsdelivr/globalping/issues

Als ik inlog op: logs@192.168.2.50
Krijg ik heel snel een melding:
Error: No such container: globalping-probe
Overleden? Fout gegaan met update naar v0.41.2? Die ik nu zie.
https://github.com/jsdeli...robe/releases/tag/v0.41.2
( Mijn probe zit nog op v0.41.1 aldus https://dash.globalping.io )

Ik ga geen tickets maken. Of snelle fix/auto fix, of helaas.

[ Voor 6% gewijzigd door neeecht op 27-10-2025 02:31 ]

[Vliegvlug]

Nav bericht van @neeecht was ik benieuwd of mijn probe nog online was maar om in het GlobalPing dashboard te komen moet ik nu opeens meer rechten geven?



Waarom moet dat dashboard opeens your organization, team membership, and private project boards. kunnen lezen.
Vooral dat laatste, waarom zijn die dingen dan private.

Nou lama dan!

[neeecht]

Is er nog een simpele manier om de probe een reset te geven ofzo naar factory settings en dat deze de nieuwe software download? Anders is het helaas over.
(Of de SD kaart opnieuw te schrijven, in Windows 10.)

[ernstoud]

neeecht schreef op maandag 27 oktober 2025 @ 13:29:
Is er nog een simpele manier om de probe een reset te geven ofzo naar factory settings en dat deze de nieuwe software download? Anders is het helaas over.
(Of de SD kaart opnieuw te schrijven, in Windows 10.)

Geen idee. Ik ga de jou en de bovengenoemde vraag even doorspelen aan de developer.

[ernstoud]

Vliegvlug schreef op maandag 27 oktober 2025 @ 07:34:
Nav bericht van @neeecht was ik benieuwd of mijn probe nog online was maar om in het GlobalPing dashboard te komen moet ik nu opeens meer rechten geven?

[Afbeelding: GlabslPing wil meer Github rechten]

Waarom moet dat dashboard opeens your organization, team membership, and private project boards. kunnen lezen.
Vooral dat laatste, waarom zijn die dingen dan private.

Nou lama dan!

Antwoord van de developer, zie hier de uitleg: https://blog.globalping.i...ns-for-tags-public-pages/

[ernstoud]

neeecht schreef op maandag 27 oktober 2025 @ 13:29:
Is er nog een simpele manier om de probe een reset te geven ofzo naar factory settings en dat deze de nieuwe software download? Anders is het helaas over.
(Of de SD kaart opnieuw te schrijven, in Windows 10.)

Antwoord van de developer:

“Did he reboot the probe and give it 10 minutes? Additionally he can check the logs by connecting to ssh using the devlogs user.
They could contain the explanation. Otherwise the easiest solution would probably be to flash the latest firmware from our repo to the card.”

[Vliegvlug]

ernstoud schreef op maandag 27 oktober 2025 @ 14:41:
[...]

Antwoord van de developer, zie hier de uitleg: https://blog.globalping.i...ns-for-tags-public-pages/

Dank voor de link maar ik lees daar alleen hoe handig organizations wel niet zijn en hoe je het zou kunnen gebruiken.
Ik ben geen bedrijf en ga die features helemaal niet gebruiken maar er staat vervolgens nergens beschreven hoe ik het dashboard dan wel kan benaderen zonder die rechten te geven.

[ernstoud]

Vliegvlug schreef op maandag 27 oktober 2025 @ 20:08:
[...]

Dank voor de link maar ik lees daar alleen hoe handig organizations wel niet zijn en hoe je het zou kunnen gebruiken.
Ik ben geen bedrijf en ga die features helemaal niet gebruiken maar er staat vervolgens nergens beschreven hoe ik het dashboard dan wel kan benaderen zonder die rechten te geven.

Gewoon de rechten toestaan. Je geeft dan rechten tot het benaderen van iets wat je niet hebt. Lijkt me niet een probleem toch?

[ernstoud]

Overigens weet ik niet of de Globalping gebruikers hier het gezien hebben maar in het dashboard kun je nu de logs van de probe ophalen en live meekijken.

De developer heeft aangegeven dat binnenkort er een nieuwe achterliggende database en API komt waardoor ze grafieken kunnen gaan aanbieden in het dashboard (op enige termijn).

[Vliegvlug]

ernstoud schreef op maandag 27 oktober 2025 @ 20:51:
[...]

Gewoon de rechten toestaan. Je geeft dan rechten tot het benaderen van iets wat je niet hebt. Lijkt me niet een probleem toch?

Kijk dat is nuttige informatie, dat hadden ze in dat linkje moeten vermelden.
Wist niet dat ik dat niet had, ging er vanuit dat dat standaard aan stond want waarom wordt er dan om rechten gevraagd vraag ik me af. Dat zou dan toch überhaupt niet nodig zijn om het te vragen bij iedereen. Of dat als je dat afwijst het wel gewoon werkt zonder die features.

[neeecht]

ernstoud schreef op maandag 27 oktober 2025 @ 14:42:
[...]


Antwoord van de developer:

“Did he reboot the probe and give it 10 minutes? Additionally he can check the logs by connecting to ssh using the devlogs user.
They could contain the explanation. Otherwise the easiest solution would probably be to flash the latest firmware from our repo to the card.”

Every 2.0s: cat /tmp/log_col... globalping-probe-050b: Mon Oct 27 23:26:47 2025

Mon Oct 27 23:26:45 UTC 2025
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!

[Raven]

ernstoud schreef op maandag 27 oktober 2025 @ 20:51:
[...]


Gewoon de rechten toestaan. Je geeft dan rechten tot het benaderen van iets wat je niet hebt. Lijkt me niet een probleem toch?

Uit nieuwsgierigheid: zelfs al heb je die wel, waarom geen mogelijkheid tot weigering zonder toegang te verliezen?

[ Voor 3% gewijzigd door Raven op 28-10-2025 08:31 ]

[ernstoud]

neeecht schreef op dinsdag 28 oktober 2025 @ 00:27:
[...]


Every 2.0s: cat /tmp/log_col... globalping-probe-050b: Mon Oct 27 23:26:47 2025

Mon Oct 27 23:26:45 UTC 2025
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!
Container status is NOT running!!

FW file op de SD Card vernieuwen dus.

[Tom Paris]

ernstoud schreef op maandag 27 oktober 2025 @ 20:51:
[...]


Gewoon de rechten toestaan. Je geeft dan rechten tot het benaderen van iets wat je niet hebt. Lijkt me niet een probleem toch?

Dat is wel kort door de bocht he. Als je verder helemaal niets doet en nooit gedaan hebt met GitHub heb je gelijk, maar als je wel lid bent van projecten, of zelf projecten host op GitHub geef je dus wel degelijk toegang.

[ernstoud]

Raven schreef op dinsdag 28 oktober 2025 @ 08:30:
[...]

Uit nieuwsgierigheid: zelfs al heb je die wel, waarom geen mogelijkheid tot weigering zonder toegang te verliezen?

Vraag het in GitHub, daar krijg je vast antwoord, ik ben ook maar gebruiker.

[neeecht]

ernstoud schreef op dinsdag 28 oktober 2025 @ 10:59:
[...]


FW file op de SD Card vernieuwen dus.

Zolang ik geen link kan vinden met:
1: Download tool X.
2: Download SD image.
3: Stop SD is SD writer
Op Windows, is het helaas over. Ik doe niet meer aan 1998 stappenplannen.

[ernstoud]

neeecht schreef op dinsdag 28 oktober 2025 @ 11:30:
[...]


Zolang ik geen link kan vinden met:
1: Download tool X.
2: Download SD image.
3: Stop SD is SD writer
Op Windows, is het helaas over. Ik doe niet meer aan 1998 stappenplannen.

Heb je wel gezocht dan?

Want hier staat de firmware en de instructie, ook voor Windows (met Rufus):

https://github.com/jsdelivr/globalping-hwprobe

Directe link naar de FW file: https://github.com/jsdeli....3/globalping-firmware.gz
Directe link naar Rufus: https://rufus.ie/

Ik begrijp je eerlijk gezegd niet helemaal.

[ Voor 14% gewijzigd door ernstoud op 28-10-2025 11:50 ]

[neeecht]

ernstoud schreef op dinsdag 28 oktober 2025 @ 11:48:
[...]


Heb je wel gezocht dan?

Want hier staat de firmware en de instructie, ook voor Windows (met Rufus):

https://github.com/jsdelivr/globalping-hwprobe

Directe link naar de FW file: https://github.com/jsdeli....3/globalping-firmware.gz
Directe link naar Rufus: https://rufus.ie/

Ik begrijp je eerlijk gezegd niet helemaal.

Okay dank u!
Ik had die globalping-hwprobe link nooit gezien
Had iets beter moeten zoeken blijkbaar.
Firmware op SD kaart gezet. In probe gedaan, herstart en klaar.
Alleen in modem nieuw MAC zichtbaar van de probe, dus IP reservering even geupdate en weer online.

Geen idee hoe de probe herkend wordt met een schone firmware, maar het werkt.

[neeecht]

IPv6 ping test unsuccessful for k.root-servers.net: 100% packet loss. IPv6 tests pass.
Is wel weer apart dan. KPN ipv6 zou nu allemaal goed moeten zijn.

[ernstoud]

neeecht schreef op dinsdag 28 oktober 2025 @ 13:18:
IPv6 ping test unsuccessful for k.root-servers.net: 100% packet loss. IPv6 tests pass.
Is wel weer apart dan. KPN ipv6 zou nu allemaal goed moeten zijn.

Ik zie die IPv6 errors ook op mijn probe op Delta, waar ik IPv6 op heb. Bijzonder dus.

[Roetzen]

Ik zie niets bijzonders, zowel mijn probe op het Delta netwerk als die op het Ziggo netwerk lijken normaal te functioneren en ik kon ook normaal inloggen op dash.globalping.io.

[rescla]

Mijn HW probe was ook overleden begin september. Hij was offline gemeld in het dashboard en als ik via SSH inlog kreeg ik een of andere vage segmentation fault. Even een nieuwe image op de SD geflashed en hij werkt weer naar behoren.

[neeecht]

https://dash.globalping.io/probes/<id>?tab=logs
In het Logs tab:

[2025-10-31 11:53:38 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for time.apple.com: 14.2857% packet loss. IPv6 tests pass.
[2025-10-31 11:53:38 +01:00] [status-manager] [WARN] IPv4 ping test unsuccessful for time.apple.com: 25% packet loss. IPv4 tests pass.

Is dit iets wat misschien beter gefixt moet worden op de probe?
Ik heb nu de firewall in de modem openstaan, maar dit blijft. Nog tips?

Update log errors:
[2025-10-30 17:37:37 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for k.root-servers.net: 100% packet loss. IPv6 tests pass.

[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for a.gtld-servers.net: ping: connect: Network is unreachable.
[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for k.root-servers.net: ping: connect: Network is unreachable.
[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for time.apple.com: ping: connect: Network is unreachable.
[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping tests failed. Retrying in 10 minutes. Probe marked as not supporting IPv6.

Dit is dat een normale disconnect:
[2025-10-30 01:29:22 +01:00] [api:error] [DEBUG] Disconnected from API: (ping timeout).
[2025-10-30 01:29:44 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:05 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:26 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:47 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:48 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:49 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:50 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:51 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:52 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:53 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:54 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:55 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:56 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:57 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:58 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:59 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:00 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:01 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:02 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:03 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:04 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:05 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:06 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:07 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:08 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:09 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:30 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:31:51 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:31:57 +01:00] [general] [DEBUG] Connection to API established.

[ Voor 101% gewijzigd door neeecht op 31-10-2025 12:33 ]

[ernstoud]

neeecht schreef op vrijdag 31 oktober 2025 @ 12:29:
https://dash.globalping.io/probes/<id>?tab=logs
In het Logs tab:

[2025-10-31 11:53:38 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for time.apple.com: 14.2857% packet loss. IPv6 tests pass.
[2025-10-31 11:53:38 +01:00] [status-manager] [WARN] IPv4 ping test unsuccessful for time.apple.com: 25% packet loss. IPv4 tests pass.

Is dit iets wat misschien beter gefixt moet worden op de probe?
Ik heb nu de firewall in de modem openstaan, maar dit blijft. Nog tips?

Update log errors:
[2025-10-30 17:37:37 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for k.root-servers.net: 100% packet loss. IPv6 tests pass.

[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for a.gtld-servers.net: ping: connect: Network is unreachable.
[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for k.root-servers.net: ping: connect: Network is unreachable.
[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping test unsuccessful for time.apple.com: ping: connect: Network is unreachable.
[2025-10-30 01:42:01 +01:00] [status-manager] [WARN] IPv6 ping tests failed. Retrying in 10 minutes. Probe marked as not supporting IPv6.

Dit is dat een normale disconnect:
[2025-10-30 01:29:22 +01:00] [api:error] [DEBUG] Disconnected from API: (ping timeout).
[2025-10-30 01:29:44 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:05 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:26 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:47 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:30:48 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:49 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:50 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:51 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:52 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:53 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:54 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:55 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:56 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:57 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:58 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:30:59 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:00 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:01 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:02 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:03 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:04 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:05 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:06 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:07 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:08 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:09 +01:00] [api:error] [ERROR] Connection to API failed: getaddrinfo EAI_AGAIN api.globalping.io
[2025-10-30 01:31:30 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:31:51 +01:00] [api:error] [ERROR] Connection to API failed: Error: timeout
[2025-10-30 01:31:57 +01:00] [general] [DEBUG] Connection to API established.

Je verbinding naar internet is wel goed?

Als je langere tijd zelf time.apple.com pingt heb je dan packet loss?

Doe eens:

ping -n 100 time.apple.com

[neeecht]

ernstoud schreef op vrijdag 31 oktober 2025 @ 12:45:
[...]


Je verbinding naar internet is wel goed?

Als je langere tijd zelf time.apple.com pingt heb je dan packet loss?

Doe eens:

ping -n 100 time.apple.com

Uiteraard.
KPN glasvezel, nieuwe aangelegd, echt perfect.
V14 modem. Firewall: Standaard (dus alles open, aldus de modem info.)

Ik denk sowieso dat apple wat moeite heeft:

ping -n 100 time.apple.com

Pinging time.g.aaplimg.com [2a01:b740:a30:4000::1e2] with 32 bytes of data:
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=14ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=14ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=67ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms

Ping statistics for 2a01:b740:a30:4000::1e2:
Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 67ms, Average = 12ms
Control-C
^C


google.com wil wat beter:

ping -n 100 google.com

Pinging google.com [2a00:1450:400e:810::200e] with 32 bytes of data:
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=3ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=3ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=3ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=4ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms

Ping statistics for 2a00:1450:400e:810::200e:
Packets: Sent = 46, Received = 46, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 1ms
Control-C
^C

[ernstoud]

neeecht schreef op vrijdag 31 oktober 2025 @ 13:24:
[...]


Uiteraard.
KPN glasvezel, nieuwe aangelegd, echt perfect.
V14 modem. Firewall: Standaard (dus alles open, aldus de modem info.)

Ik denk sowieso dat apple wat moeite heeft:

ping -n 100 time.apple.com

Pinging time.g.aaplimg.com [2a01:b740:a30:4000::1e2] with 32 bytes of data:
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=14ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=14ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=67ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Request timed out.
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=12ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms
Reply from 2a01:b740:a30:4000::1e2: time=11ms

Ping statistics for 2a01:b740:a30:4000::1e2:
Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 67ms, Average = 12ms
Control-C
^C


google.com wil wat beter:

ping -n 100 google.com

Pinging google.com [2a00:1450:400e:810::200e] with 32 bytes of data:
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=3ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=3ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=3ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=4ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=1ms
Reply from 2a00:1450:400e:810::200e: time=2ms
Reply from 2a00:1450:400e:810::200e: time=2ms

Ping statistics for 2a00:1450:400e:810::200e:
Packets: Sent = 46, Received = 46, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 1ms
Control-C
^C

Probleem ligt dus niet bij jou maar bij time.apple.com.