Question about "location setting" of RIPE Atlas
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
On Sat, Aug 22, 2015 at 11:42 PM, Anurag Bhatia <me@anuragbhatia.com> wrote:
What you all think? Can someone recommend on correct location?
I for one would leave the location intact and add an additional tag (point-to-point?) to your probe. You can do so by clicking the "Edit" link under "My Probe" section. While at it, you may also consider checking the "Fibre" tag too :-) -- "If you want to go fast, go alone. If you want to go far, go together."
Anurag, thanks for the good question. Please set the location as the physical location of the probe itself. We need a common definition for this. If we all over-think and fudge this, the data will become meaningless. Also Inigo's suggestions are good ones. Daniel On 22.08.15 23:42 , Anurag Bhatia wrote:
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 <http://anuragbhatia.com>
PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2
Thanks for replies everyone! I completely agree to what you are saying and I think Tomas hits it right saying that I anyway have 19ms latency hence result would be messy. So no over thinking, I kept location as where Probe physically is and updated it with "point-to-point" tag. :) Thanks again for suggestions. On Mon, Aug 24, 2015 at 1:11 PM, Daniel Karrenberg < daniel.karrenberg@ripe.net> wrote:
Anurag,
thanks for the good question.
Please set the location as the physical location of the probe itself. We need a common definition for this. If we all over-think and fudge this, the data will become meaningless. Also Inigo's suggestions are good ones.
Daniel
On 22.08.15 23:42 , Anurag Bhatia wrote:
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 <http://anuragbhatia.com>
PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2
-- Anurag Bhatia anuragbhatia.com PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2
participants (3)
-
Anurag Bhatia -
Daniel Karrenberg -
Iñigo Ortiz de Urbina