Hi Atlas list, I sent a probe to Jersey (https://atlas.ripe.net/probes/28215/), but it shows up as GB instead of JE. Seems like perhaps a geodb is wrong :)
On Wed, 11 Jan 2017 11:22:39 +0000 Marty Strong <marty@martystrong.co.uk> wrote:
Hi Atlas list,
I sent a probe to Jersey (https://atlas.ripe.net/probes/28215/), but it shows up as GB instead of JE.
Seems like perhaps a geodb is wrong :)
Did you check `whois 82.112.155.203 | grep country`? What do you want from the Atlas project in this case? -- With respect, Roman
I assumed that the flag shown was based on the location set by the host when the registered it. The network tab does show it’s in JE. Country seems to be JE for the prefix too: $ cwhois 82.112.155.203 AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name 8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE On 11 January 2017 at 11:27, Roman Mamedov <rm@romanrm.net> wrote:
On Wed, 11 Jan 2017 11:22:39 +0000 Marty Strong <marty@martystrong.co.uk> wrote:
Hi Atlas list,
I sent a probe to Jersey (https://atlas.ripe.net/probes/28215/), but it shows up as GB instead of JE.
Seems like perhaps a geodb is wrong :)
Did you check `whois 82.112.155.203 | grep country`? What do you want from the Atlas project in this case?
-- With respect, Roman
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk> wrote:
$ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '82.112.152.0 - 82.112.155.255' % Abuse contact for '82.112.152.0 - 82.112.155.255' is ' ripe@jerseytelecom.com' inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 fax-no: +44 1534 882883 remarks: trouble: please email trouble reports to ripe@jerseytelecom.com admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered % Information related to '82.112.144.0/20AS8681' route: 82.112.144.0/20 descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE % This query was served by the RIPE Database Query Service version 1.88 (WAGYU) -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane
Hmm, I could have sworn that it was based on where you physically locate the probe. I've seen plenty of probes that are geo-located wrong when somebody moves to another country but fails to update the location of the probe. I guess I'll point them to update it. On 11 January 2017 at 11:53, Sanjeev Gupta <ghane0@gmail.com> wrote:
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk> wrote:
$ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag.
% Information related to '82.112.152.0 - 82.112.155.255'
% Abuse contact for '82.112.152.0 - 82.112.155.255' is ' ripe@jerseytelecom.com'
inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered
role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 <+44%201534%20882882> fax-no: +44 1534 882883 <+44%201534%20882883> remarks: trouble: please email trouble reports to ripe@jerseytelecom.com admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered
% Information related to '82.112.144.0/20AS8681'
route: 82.112.144.0/20 descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
-- Sanjeev Gupta +65 98551208 <9855%201208> http://www.linkedin.com/in/ghane
Looks like some are correct and some are incorrect. $ while read p; do whois -h whois.ripe.net $p | egrep "inetnum|country|route|descr"; done<as8681.txt inetnum: 31.186.112.0 - 31.186.119.255 country: JE mnt-routes: JE-TEL-MNT route: 31.186.112.0/21 descr: Jersey Telecom -CIDR Block 5 inetnum: 37.156.38.0 - 37.156.39.255 country: JE mnt-routes: JE-TEL-MNT route: 37.156.38.0/23 descr: JTGlobal - WHS-CIDR inetnum: 81.20.176.0 - 81.20.191.255 country: JE mnt-routes: NEWTEL2-RIPE-MNT route: 81.20.176.0/20 descr: Newtel CIDR Block mnt-routes: NEWTEL2-RIPE-MNT inetnum: 82.112.128.0 - 82.112.159.255 country: JE mnt-routes: JE-TEL-MNT route: 82.112.128.0/19 descr: Jersey Telecom - CIDR block 2 descr: <address> inetnum: 87.244.64.0 - 87.244.127.255 country: JE mnt-routes: JE-TEL-MNT route: 87.244.64.0/18 descr: Jersey Telecom - CIDR block 3 inetnum: 185.3.52.0 - 185.3.55.255 country: JE mnt-routes: JE-TEL-MNT route: 185.3.52.0/22 descr: JTGlobal - CIDR Block 11 inetnum: 209.251.252.0 - 209.251.253.255 country: JE mnt-routes: JE-TEL-MNT route: 209.251.252.0/23 descr: Jersey Telecom - CIDR block 13 inetnum: 212.9.0.0 - 212.9.31.255 country: JE mnt-routes: JE-TEL-MNT route: 212.9.0.0/19 descr: Jersey Telecom - CIDR block 1 descr: <address> inetnum: 185.57.212.0 - 185.57.215.255 country: JE mnt-routes: NEWTEL2-RIPE-MNT route: 185.57.212.0/22 descr: Newtel Limited WL Range inetnum: 46.31.240.0 - 46.31.247.255 country: GB mnt-routes: WAVE-TEL-MNT route: 46.31.240.0/21 descr: Jersey Telecom -CIDR Block 4 inetnum: 78.41.0.0 - 78.41.7.255 country: GB mnt-routes: WAVE-TEL-MNT route: 78.41.0.0/21 descr: Wave Telecom inetnum: 92.43.208.0 - 92.43.215.255 country: GB mnt-routes: WAVE-TEL-MNT route: 92.43.208.0/21 descr: Wave Telecom inetnum: 93.187.0.0 - 93.187.7.255 country: GB mnt-routes: WAVE-TEL-MNT route: 93.187.0.0/21 descr: JT GNSY inetnum: 93.189.160.0 - 93.189.167.255 country: GB mnt-routes: WAVE-TEL-MNT route: 93.189.160.0/21 descr: Wave Telecom inetnum: 185.37.76.0 - 185.37.79.255 country: GB mnt-routes: WAVE-TEL-MNT route: 185.37.76.0/22 descr: Jersey Telecom - CIDR block 12 inetnum: 195.226.128.0 - 195.226.159.255 country: GB mnt-routes: WAVE-TEL-MNT route: 195.226.128.0/19 descr: Jersey Telecom On 11 January 2017 at 12:00, Marty Strong <marty@martystrong.co.uk> wrote:
Hmm, I could have sworn that it was based on where you physically locate the probe. I've seen plenty of probes that are geo-located wrong when somebody moves to another country but fails to update the location of the probe.
I guess I'll point them to update it.
On 11 January 2017 at 11:53, Sanjeev Gupta <ghane0@gmail.com> wrote:
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk> wrote:
$ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag.
% Information related to '82.112.152.0 - 82.112.155.255'
% Abuse contact for '82.112.152.0 - 82.112.155.255' is ' ripe@jerseytelecom.com'
inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered
role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 <+44%201534%20882882> fax-no: +44 1534 882883 <+44%201534%20882883> remarks: trouble: please email trouble reports to ripe@jerseytelecom.com admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered
% Information related to '82.112.144.0/20AS8681'
route: 82.112.144.0/20 descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
-- Sanjeev Gupta +65 98551208 <9855%201208> http://www.linkedin.com/in/ghane
JT kit can be located in the UK as well :) at least a lot was a while ago from ex psinet work. Colin
On 11 Jan 2017, at 12:13, Marty Strong <marty@martystrong.co.uk> wrote:
Looks like some are correct and some are incorrect.
$ while read p; do whois -h whois.ripe.net <http://whois.ripe.net/> $p | egrep "inetnum|country|route|descr"; done<as8681.txt
inetnum: 31.186.112.0 - 31.186.119.255
country: JE
mnt-routes: JE-TEL-MNT
route: 31.186.112.0/21 <http://31.186.112.0/21> descr: Jersey Telecom -CIDR Block 5
inetnum: 37.156.38.0 - 37.156.39.255
country: JE
mnt-routes: JE-TEL-MNT
route: 37.156.38.0/23 <http://37.156.38.0/23> descr: JTGlobal - WHS-CIDR
inetnum: 81.20.176.0 - 81.20.191.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 81.20.176.0/20 <http://81.20.176.0/20> descr: Newtel CIDR Block
mnt-routes: NEWTEL2-RIPE-MNT
inetnum: 82.112.128.0 - 82.112.159.255
country: JE
mnt-routes: JE-TEL-MNT
route: 82.112.128.0/19 <http://82.112.128.0/19> descr: Jersey Telecom - CIDR block 2
descr: <address>
inetnum: 87.244.64.0 - 87.244.127.255
country: JE
mnt-routes: JE-TEL-MNT
route: 87.244.64.0/18 <http://87.244.64.0/18> descr: Jersey Telecom - CIDR block 3
inetnum: 185.3.52.0 - 185.3.55.255
country: JE
mnt-routes: JE-TEL-MNT
route: 185.3.52.0/22 <http://185.3.52.0/22> descr: JTGlobal - CIDR Block 11
inetnum: 209.251.252.0 - 209.251.253.255
country: JE
mnt-routes: JE-TEL-MNT
route: 209.251.252.0/23 <http://209.251.252.0/23> descr: Jersey Telecom - CIDR block 13
inetnum: 212.9.0.0 - 212.9.31.255
country: JE
mnt-routes: JE-TEL-MNT
route: 212.9.0.0/19 <http://212.9.0.0/19> descr: Jersey Telecom - CIDR block 1
descr: <address>
inetnum: 185.57.212.0 - 185.57.215.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 185.57.212.0/22 <http://185.57.212.0/22> descr: Newtel Limited WL Range
inetnum: 46.31.240.0 - 46.31.247.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 46.31.240.0/21 <http://46.31.240.0/21> descr: Jersey Telecom -CIDR Block 4
inetnum: 78.41.0.0 - 78.41.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 78.41.0.0/21 <http://78.41.0.0/21> descr: Wave Telecom
inetnum: 92.43.208.0 - 92.43.215.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 92.43.208.0/21 <http://92.43.208.0/21> descr: Wave Telecom
inetnum: 93.187.0.0 - 93.187.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.187.0.0/21 <http://93.187.0.0/21> descr: JT GNSY
inetnum: 93.189.160.0 - 93.189.167.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.189.160.0/21 <http://93.189.160.0/21> descr: Wave Telecom
inetnum: 185.37.76.0 - 185.37.79.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 185.37.76.0/22 <http://185.37.76.0/22> descr: Jersey Telecom - CIDR block 12
inetnum: 195.226.128.0 - 195.226.159.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 195.226.128.0/19 <http://195.226.128.0/19> descr: Jersey Telecom
On 11 January 2017 at 12:00, Marty Strong <marty@martystrong.co.uk <mailto:marty@martystrong.co.uk>> wrote: Hmm, I could have sworn that it was based on where you physically locate the probe. I've seen plenty of probes that are geo-located wrong when somebody moves to another country but fails to update the location of the probe.
I guess I'll point them to update it.
On 11 January 2017 at 11:53, Sanjeev Gupta <ghane0@gmail.com <mailto:ghane0@gmail.com>> wrote:
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk <mailto:marty@martystrong.co.uk>> wrote: $ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 <http://82.112.128.0/19> | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf <http://www.ripe.net/db/support/db-terms-conditions.pdf>
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag.
% Information related to '82.112.152.0 - 82.112.155.255'
% Abuse contact for '82.112.152.0 - 82.112.155.255' is 'ripe@jerseytelecom.com <mailto:ripe@jerseytelecom.com>'
inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered
role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 <tel:+44%201534%20882882> fax-no: +44 1534 882883 <tel:+44%201534%20882883> remarks: trouble: please email trouble reports to ripe@jerseytelecom.com <mailto:ripe@jerseytelecom.com> admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered
% Information related to '82.112.144.0/20AS8681 <http://82.112.144.0/20AS8681>'
route: 82.112.144.0/20 <http://82.112.144.0/20> descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
-- Sanjeev Gupta +65 98551208 <tel:9855%201208> http://www.linkedin.com/in/ghane <http://www.linkedin.com/in/ghane>
Sure, although this particular one is physically in St. Helier, I’ve emailed my contact to point it out, I’ll see what he says. Regards, Marty Strong -------------------------------------- Cloudflare - AS13335 Network Engineer marty@cloudflare.com +44 7584 906 055 smartflare (Skype) https://www.peeringdb.com/asn/13335
On 11 Jan 2017, at 13:09, Colin Johnston <colinj@mx5.org.uk> wrote:
JT kit can be located in the UK as well :) at least a lot was a while ago from ex psinet work.
Colin
On 11 Jan 2017, at 12:13, Marty Strong <marty@martystrong.co.uk> wrote:
Looks like some are correct and some are incorrect.
$ while read p; do whois -h whois.ripe.net $p | egrep "inetnum|country|route|descr"; done<as8681.txt
inetnum: 31.186.112.0 - 31.186.119.255
country: JE
mnt-routes: JE-TEL-MNT
route: 31.186.112.0/21
descr: Jersey Telecom -CIDR Block 5
inetnum: 37.156.38.0 - 37.156.39.255
country: JE
mnt-routes: JE-TEL-MNT
route: 37.156.38.0/23
descr: JTGlobal - WHS-CIDR
inetnum: 81.20.176.0 - 81.20.191.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 81.20.176.0/20
descr: Newtel CIDR Block
mnt-routes: NEWTEL2-RIPE-MNT
inetnum: 82.112.128.0 - 82.112.159.255
country: JE
mnt-routes: JE-TEL-MNT
route: 82.112.128.0/19
descr: Jersey Telecom - CIDR block 2
descr: <address>
inetnum: 87.244.64.0 - 87.244.127.255
country: JE
mnt-routes: JE-TEL-MNT
route: 87.244.64.0/18
descr: Jersey Telecom - CIDR block 3
inetnum: 185.3.52.0 - 185.3.55.255
country: JE
mnt-routes: JE-TEL-MNT
route: 185.3.52.0/22
descr: JTGlobal - CIDR Block 11
inetnum: 209.251.252.0 - 209.251.253.255
country: JE
mnt-routes: JE-TEL-MNT
route: 209.251.252.0/23
descr: Jersey Telecom - CIDR block 13
inetnum: 212.9.0.0 - 212.9.31.255
country: JE
mnt-routes: JE-TEL-MNT
route: 212.9.0.0/19
descr: Jersey Telecom - CIDR block 1
descr: <address>
inetnum: 185.57.212.0 - 185.57.215.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 185.57.212.0/22
descr: Newtel Limited WL Range
inetnum: 46.31.240.0 - 46.31.247.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 46.31.240.0/21
descr: Jersey Telecom -CIDR Block 4
inetnum: 78.41.0.0 - 78.41.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 78.41.0.0/21
descr: Wave Telecom
inetnum: 92.43.208.0 - 92.43.215.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 92.43.208.0/21
descr: Wave Telecom
inetnum: 93.187.0.0 - 93.187.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.187.0.0/21
descr: JT GNSY
inetnum: 93.189.160.0 - 93.189.167.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.189.160.0/21
descr: Wave Telecom
inetnum: 185.37.76.0 - 185.37.79.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 185.37.76.0/22
descr: Jersey Telecom - CIDR block 12
inetnum: 195.226.128.0 - 195.226.159.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 195.226.128.0/19
descr: Jersey Telecom
On 11 January 2017 at 12:00, Marty Strong <marty@martystrong.co.uk> wrote: Hmm, I could have sworn that it was based on where you physically locate the probe. I've seen plenty of probes that are geo-located wrong when somebody moves to another country but fails to update the location of the probe.
I guess I'll point them to update it.
On 11 January 2017 at 11:53, Sanjeev Gupta <ghane0@gmail.com> wrote:
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk> wrote: $ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag.
% Information related to '82.112.152.0 - 82.112.155.255'
% Abuse contact for '82.112.152.0 - 82.112.155.255' is 'ripe@jerseytelecom.com'
inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered
role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 fax-no: +44 1534 882883 remarks: trouble: please email trouble reports to ripe@jerseytelecom.com admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered
% Information related to '82.112.144.0/20AS8681'
route: 82.112.144.0/20 descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
-- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane
Hi all, It’s just a funny possible glitch of google maps. if you move the location picker of a few millimeters, google returns a different country code (even if what changes is just the street). See screenshots: Ciao, Massimo
On 11 Jan 2017, at 14:20, Marty Strong <marty@cloudflare.com> wrote:
Sure, although this particular one is physically in St. Helier, I’ve emailed my contact to point it out, I’ll see what he says.
Regards, Marty Strong -------------------------------------- Cloudflare - AS13335 Network Engineer marty@cloudflare.com +44 7584 906 055 smartflare (Skype)
https://www.peeringdb.com/asn/13335
On 11 Jan 2017, at 13:09, Colin Johnston <colinj@mx5.org.uk> wrote:
JT kit can be located in the UK as well :) at least a lot was a while ago from ex psinet work.
Colin
On 11 Jan 2017, at 12:13, Marty Strong <marty@martystrong.co.uk> wrote:
Looks like some are correct and some are incorrect.
$ while read p; do whois -h whois.ripe.net $p | egrep "inetnum|country|route|descr"; done<as8681.txt
inetnum: 31.186.112.0 - 31.186.119.255
country: JE
mnt-routes: JE-TEL-MNT
route: 31.186.112.0/21
descr: Jersey Telecom -CIDR Block 5
inetnum: 37.156.38.0 - 37.156.39.255
country: JE
mnt-routes: JE-TEL-MNT
route: 37.156.38.0/23
descr: JTGlobal - WHS-CIDR
inetnum: 81.20.176.0 - 81.20.191.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 81.20.176.0/20
descr: Newtel CIDR Block
mnt-routes: NEWTEL2-RIPE-MNT
inetnum: 82.112.128.0 - 82.112.159.255
country: JE
mnt-routes: JE-TEL-MNT
route: 82.112.128.0/19
descr: Jersey Telecom - CIDR block 2
descr: <address>
inetnum: 87.244.64.0 - 87.244.127.255
country: JE
mnt-routes: JE-TEL-MNT
route: 87.244.64.0/18
descr: Jersey Telecom - CIDR block 3
inetnum: 185.3.52.0 - 185.3.55.255
country: JE
mnt-routes: JE-TEL-MNT
route: 185.3.52.0/22
descr: JTGlobal - CIDR Block 11
inetnum: 209.251.252.0 - 209.251.253.255
country: JE
mnt-routes: JE-TEL-MNT
route: 209.251.252.0/23
descr: Jersey Telecom - CIDR block 13
inetnum: 212.9.0.0 - 212.9.31.255
country: JE
mnt-routes: JE-TEL-MNT
route: 212.9.0.0/19
descr: Jersey Telecom - CIDR block 1
descr: <address>
inetnum: 185.57.212.0 - 185.57.215.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 185.57.212.0/22
descr: Newtel Limited WL Range
inetnum: 46.31.240.0 - 46.31.247.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 46.31.240.0/21
descr: Jersey Telecom -CIDR Block 4
inetnum: 78.41.0.0 - 78.41.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 78.41.0.0/21
descr: Wave Telecom
inetnum: 92.43.208.0 - 92.43.215.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 92.43.208.0/21
descr: Wave Telecom
inetnum: 93.187.0.0 - 93.187.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.187.0.0/21
descr: JT GNSY
inetnum: 93.189.160.0 - 93.189.167.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.189.160.0/21
descr: Wave Telecom
inetnum: 185.37.76.0 - 185.37.79.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 185.37.76.0/22
descr: Jersey Telecom - CIDR block 12
inetnum: 195.226.128.0 - 195.226.159.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 195.226.128.0/19
descr: Jersey Telecom
On 11 January 2017 at 12:00, Marty Strong <marty@martystrong.co.uk> wrote: Hmm, I could have sworn that it was based on where you physically locate the probe. I've seen plenty of probes that are geo-located wrong when somebody moves to another country but fails to update the location of the probe.
I guess I'll point them to update it.
On 11 January 2017 at 11:53, Sanjeev Gupta <ghane0@gmail.com> wrote:
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk> wrote: $ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag.
% Information related to '82.112.152.0 - 82.112.155.255'
% Abuse contact for '82.112.152.0 - 82.112.155.255' is 'ripe@jerseytelecom.com'
inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered
role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 fax-no: +44 1534 882883 remarks: trouble: please email trouble reports to ripe@jerseytelecom.com admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered
% Information related to '82.112.144.0/20AS8681'
route: 82.112.144.0/20 descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
-- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane
I looked back at a probe that was listed wrong on the map (GB), but was under the correct country code/flag (US), I guess it is based on the network country entry in the IRR record. Unless somebody from RIPE has the definitive answer? On 11 January 2017 at 13:38, Massimo Candela <mcandela@ripe.net> wrote:
Hi all,
It’s just a funny possible glitch of google maps. if you move the location picker of a few millimeters, google returns a different country code (even if what changes is just the street).
See screenshots:
Ciao, Massimo
On 11 Jan 2017, at 14:20, Marty Strong <marty@cloudflare.com> wrote:
Sure, although this particular one is physically in St. Helier, I’ve emailed my contact to point it out, I’ll see what he says.
Regards, Marty Strong -------------------------------------- Cloudflare - AS13335 Network Engineer marty@cloudflare.com +44 7584 906 055 <+44%207584%20906055> smartflare (Skype)
https://www.peeringdb.com/asn/13335
On 11 Jan 2017, at 13:09, Colin Johnston <colinj@mx5.org.uk> wrote:
JT kit can be located in the UK as well :) at least a lot was a while ago from ex psinet work.
Colin
On 11 Jan 2017, at 12:13, Marty Strong <marty@martystrong.co.uk> wrote:
Looks like some are correct and some are incorrect.
$ while read p; do whois -h whois.ripe.net $p | egrep "inetnum|country|route|descr"; done<as8681.txt
inetnum: 31.186.112.0 - 31.186.119.255
country: JE
mnt-routes: JE-TEL-MNT
route: 31.186.112.0/21
descr: Jersey Telecom -CIDR Block 5
inetnum: 37.156.38.0 - 37.156.39.255
country: JE
mnt-routes: JE-TEL-MNT
route: 37.156.38.0/23
descr: JTGlobal - WHS-CIDR
inetnum: 81.20.176.0 - 81.20.191.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 81.20.176.0/20
descr: Newtel CIDR Block
mnt-routes: NEWTEL2-RIPE-MNT
inetnum: 82.112.128.0 - 82.112.159.255
country: JE
mnt-routes: JE-TEL-MNT
route: 82.112.128.0/19
descr: Jersey Telecom - CIDR block 2
descr: <address>
inetnum: 87.244.64.0 - 87.244.127.255
country: JE
mnt-routes: JE-TEL-MNT
route: 87.244.64.0/18
descr: Jersey Telecom - CIDR block 3
inetnum: 185.3.52.0 - 185.3.55.255
country: JE
mnt-routes: JE-TEL-MNT
route: 185.3.52.0/22
descr: JTGlobal - CIDR Block 11
inetnum: 209.251.252.0 - 209.251.253.255
country: JE
mnt-routes: JE-TEL-MNT
route: 209.251.252.0/23
descr: Jersey Telecom - CIDR block 13
inetnum: 212.9.0.0 - 212.9.31.255
country: JE
mnt-routes: JE-TEL-MNT
route: 212.9.0.0/19
descr: Jersey Telecom - CIDR block 1
descr: <address>
inetnum: 185.57.212.0 - 185.57.215.255
country: JE
mnt-routes: NEWTEL2-RIPE-MNT
route: 185.57.212.0/22
descr: Newtel Limited WL Range
inetnum: 46.31.240.0 - 46.31.247.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 46.31.240.0/21
descr: Jersey Telecom -CIDR Block 4
inetnum: 78.41.0.0 - 78.41.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 78.41.0.0/21
descr: Wave Telecom
inetnum: 92.43.208.0 - 92.43.215.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 92.43.208.0/21
descr: Wave Telecom
inetnum: 93.187.0.0 - 93.187.7.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.187.0.0/21
descr: JT GNSY
inetnum: 93.189.160.0 - 93.189.167.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 93.189.160.0/21
descr: Wave Telecom
inetnum: 185.37.76.0 - 185.37.79.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 185.37.76.0/22
descr: Jersey Telecom - CIDR block 12
inetnum: 195.226.128.0 - 195.226.159.255
country: GB
mnt-routes: WAVE-TEL-MNT
route: 195.226.128.0/19
descr: Jersey Telecom
On 11 January 2017 at 12:00, Marty Strong <marty@martystrong.co.uk> wrote: Hmm, I could have sworn that it was based on where you physically locate the probe. I've seen plenty of probes that are geo-located wrong when somebody moves to another country but fails to update the location of the probe.
I guess I'll point them to update it.
On 11 January 2017 at 11:53, Sanjeev Gupta <ghane0@gmail.com> wrote:
On Wed, Jan 11, 2017 at 7:39 PM, Marty Strong <marty@martystrong.co.uk> wrote: $ cwhois 82.112.155.203
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
8681 | 82.112.155.203 | 82.112.128.0/19 | JE | ripencc | 2003-12-09 | JT , JE
From here: sanjeev@X201wily:~$ whois 82.112.155.203 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered. % To receive output for a database update, use the "-B" flag.
% Information related to '82.112.152.0 - 82.112.155.255'
% Abuse contact for '82.112.152.0 - 82.112.155.255' is ' ripe@jerseytelecom.com'
inetnum: 82.112.152.0 - 82.112.155.255 netname: JT-Rapid-Res descr: Jersey Telecom Rapid Service country: GB admin-c: JT954-RIPE tech-c: JT954-RIPE status: ASSIGNED PA mnt-by: JE-TEL-MNT created: 2005-07-19T15:04:29Z last-modified: 2005-07-19T15:04:29Z source: RIPE # Filtered
role: JT ADMIN address: Jersey Telecom address: P.O. Box 53 address: St Helier address: Jersey phone: +44 1534 882882 <+44%201534%20882882> fax-no: +44 1534 882883 <+44%201534%20882883> remarks: trouble: please email trouble reports to ripe@jerseytelecom.com admin-c: CJ292-RIPE admin-c: WI92-RIPE admin-c: BF413-RIPE tech-c: CJ292-RIPE tech-c: WI92-RIPE tech-c: BF413-RIPE nic-hdl: JT954-RIPE mnt-by: JE-TEL-MNT created: 2002-02-27T13:45:01Z last-modified: 2010-03-09T12:26:51Z source: RIPE # Filtered
% Information related to '82.112.144.0/20AS8681'
route: 82.112.144.0/20 descr: Jersey Telecom origin: AS8681 mnt-by: WAVE-TEL-MNT mnt-by: JE-TEL-MNT mnt-by: AS8681-MNT created: 2016-11-29T15:38:50Z last-modified: 2016-11-29T15:38:50Z source: RIPE
% This query was served by the RIPE Database Query Service version 1.88 (WAGYU)
-- Sanjeev Gupta +65 98551208 <9855%201208> http://www.linkedin.com/in/ghane
participants (6)
-
Colin Johnston -
Marty Strong -
Marty Strong -
Massimo Candela -
Roman Mamedov -
Sanjeev Gupta