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] Question about "location setting" of RIPE Atlas
- Previous message (by thread): [atlas] Afilias, Los Angeles, CA, United States has joined RIPE Atlas anchors
- Next message (by thread): [atlas] Question about "location setting" of RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anurag Bhatia
me at anuragbhatia.com
Sat Aug 22 23:42:16 CEST 2015
I have been hosting one of RIPE probes and recently I have switched over my ISP. Basically my previous ISP provider was regular ISP network with full L3 PoPs nearby but in my new setup I have got a point to point to a city 900km away and getting IP transit over there. Now under such case, I am "technically" customer of that network. Should I still keep my location as I have current one or better update it to that new location 900km away? The latency of course is low (as it is provisioned on fiber and hence just 20ms roundtrip) but I think it will confuse off stats if anyone considers to use this probe for any data in my region. What you all think? Can someone recommend on correct location? Thanks. -- Anurag Bhatia anuragbhatia.com PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20150823/926a01e7/attachment.html>
- Previous message (by thread): [atlas] Afilias, Los Angeles, CA, United States has joined RIPE Atlas anchors
- Next message (by thread): [atlas] Question about "location setting" of RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]