This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Local network checks
- Previous message (by thread): [atlas] Local network checks
- Next message (by thread): [atlas] Local network checks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alison Wheeler
ripecontact at markyate.net
Mon Apr 11 13:49:04 CEST 2016
Sadly, there was nothing in there to indicate a problem, other than no records: <pre> 74.125.47.144 2016-04-07 18:57:44 A 0h 1m 74.125.47.140 2016-04-07 18:57:44 AAAA 0h 1m 2a00:1450:400c:c08::116 2016-03-26 00:58:46 A 8d 9h 17m 74.125.47.14 2016-03-26 00:58:46 AAAA 8d 9h 17m </pre> and as I don't check the probe's status daily (mea culpa!) it wasn't until I was mailed after a week of it being down that I knew there was an issue. But even then, if the RIPE servers can't 'see' the probe I can't do anything via the web interface, hence my wondering if there is any way to awaken it via a local network action (analogous to sending a WakeOnLAN ping) Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [atlas] Local network checks
- Next message (by thread): [atlas] Local network checks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]