Re: Google IP Geolocation

The issues that others had earlier this month just hit us this morning. Users in Israel (132.74.0.0/15) trying to access Google.com or Youtube.com appear as coming from Iceland (see screenshot). Change happened overnight.  Someone internally in Google's geo-location group typo'ed Israel as Ic

Re: Google IP Geolocation

On 22/04/2021 11:36, Hank Nussbacher wrote: The issues that others had earlier this month just hit us this morning. Users in Israel (132.74.0.0/15) trying to access Google.com or Youtube.com appear as coming from Iceland (see screenshot). Change happened overnight.  Someone internally in Goog

Re: BGP and The zero window edge

On Thu, Apr 22, 2021 at 02:29:31PM +0300, Alexandre Snarskii wrote: > 9002. Hit by Juniper PR1562090, route stuck in DeletePending.. > Workaround applied, sessions with 6939 restarted, route is gone. Thank you for the details and clearing the issue. Kind regards, Job

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

> > If the endpoint (e.g. web server) is physically located in Germany and > you're helping a client misrepresent that it's located in Estonia in > order to evade a legal requirement that it be located in Estonia then > you've made yourself a party to criminal fraud. > While I agree with the overa

RE: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

Hi, >>If the endpoint (e.g. web server) is physically located in Germany and >>you're helping a client misrepresent that it's located in Estonia in >>order to evade a legal requirement that it be located in Estonia then >>you've made yourself a party to criminal fraud. >While I agree with the ov

Re: Geo location Contacts

https://ipdata.co/corrections.html Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐ Original Message ‐‐‐ On Wednesday, April 21, 2021 5:32 PM, Brian wrote: > Good day all. I am trying to find contacts at ipdata.co and ipinfo.io. I > recently acquired new ip space and mo

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

William, The plan is to carve out a /24 for "Estonia" and have special servers on it. This would be the same /24 I'd have to use if I were to put a legitimate POP there. This also means I don't conflict with the real Germany. I am just worried about violating the 'rules' of these providers an

Re: Geo location Contacts

Hi Brian, On 21/04/2021 23:32, Brian wrote: Good day all. I am trying to find contacts at ipdata.co and ipinfo.io . I recently acquired new ip space and most places have updated. But the above 2 have not and still show CA as the location for this ip space

Re: Google IP Geolocation

Hi Hank, I reported it against the /15 you supplied, since I agree you shouldn't have to! Internal bug reference for Google is bug 186090498. If others have gone via Google's NOC, mentioning that reference to the NOC may help get your "me too" on the list, but if it is a systemic .IL -> .IS hopef

Re: BGP and The zero window edge

On Thu, Apr 22, 2021 at 01:24:54AM +0200, Job Snijders via NANOG wrote: [...] > > Another one is > http://lg.ring.nlnog.net/prefix_detail/lg01/ipv6?q=2a0b:6b86:d24::/48 > > 2a0b:6b86:d24::/48 via: > BGP.as_path: 201701 9002 6939 42615 212232 > BGP.as_path: 34927 9002 6939

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

On 4/22/21 15:57, Brian Turnbow via NANOG wrote: So to extend this further, you assign a class of IPs to a customer and register it to them in the RIPE database. Do you assign it to the customers address, in Estonia , or use the DC Address which is in Germany? Which could be the basis of

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

On Thu, Apr 22, 2021 at 7:12 AM nanoguser100 via NANOG wrote: > William, > > The plan is to carve out a /24 for "Estonia" and have special servers on > it. This would be the same /24 I'd have to use if I were to put a > legitimate POP there. This also means I don't conflict with the real > Germ

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

On Wed, Apr 21, 2021 at 12:21:26PM -0700, William Herrin wrote: > a legal requirement that it be located in [Atlantis] A legal requirement of whom? Undoubtedly the requirement is made of provider of this theoretical service doing the restricting. Is that "legal requirement" satisfied by asking a

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

I sincerely doubt that any actual *law* could be enforced against an ISP which is a legal entity in one location, yet has multiple discrete /23 or /24 blocks and without any obfuscation choose to announce them from multiple different geographic locations. Configurations where an AS has multiple isl

RE: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

> > Question - if a country is not assigned to an allocation or sub-assignment, > what does it default to within the RIPE region? > > In the AFRINIC region, for example, it would be MU (Mauritius), as that is > where AFRINIC are located. AFAIK Ripe does not set a default, it is up to the LIR. Yo

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

On 4/22/21 16:55, Brian Turnbow wrote: AFAIK Ripe does not set a default, it is up to the LIR. You can assign geoloc to orgs ans assignments Ripe publishes a list of all allocations made to the provider and lists their country of record. If the address space is unassigned I'm not sure as it

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

On Apr 22, 2021, at 10:23 AM, Matthew Petach wrote: > On Thu, Apr 22, 2021 at 7:12 AM nanoguser100 via NANOG > wrote: >> William, >> >> The plan is to carve out a /24 for "Estonia" and have special servers on it. >> This would be the same /24 I'd have to use if I were to put a legitimate >>

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

Brian Turnbow via NANOG writes: > If the address space is unassigned I'm not sure as it is not listed in the > file of allocations that contains the country , but I would guess NL as the > RIPE country of record. I seem to remember they use ZZ for unknown geographical area. jaap

Cloudflare OCTO RPKI Validator - LACNIC CAs issues

Does anybody else have problems with Cloudflare's RPKI Validator with prefixes from LACNIC? Customers were sending us some reports of issues with LACNIC's IPBlocks using Cloudflare RPKI as source of validation. A friend and I did some checks. And looks like that some issue is happening on the Lac

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

I see a lot of replies about the legality. As mentioned I have legitimate reasons for doing this. I plan on serving customers in country. My questions really are: * Is most geo data simply derived from self reporting? * Do these vendors have verification mechanisms? * Going to the Estonia\German

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

When an RIR asserts geo in Whois, it's derived from the organisational data, but usually/often then self asserted. It was asserted by the delegate, during registration. When an RIR asserts geo in organisational data, it's self-asserted through a filter of things like Dunn & Bradstreet and company

Re: Cloudflare OCTO RPKI Validator - LACNIC CAs issues

Hi Douglas, Not sure about dip in their rpki monitoring page for lacnic, but I could see the VRP here https://rpki.cloudflare.com/rpki.json The daily snapshot taken at 23:47 22-04-2021 using rpki.cloudflare.com shows the prefix. cloudflare# grep 200.160.0.0 2021-04-22-2347-UTC + 200.160.0.0

Re: Submitting Fake Geolocation for blocks to Data Brokers and RIRs

On 4/22/2021 9:30 AM, Tom Beecher wrote: While I agree with the overall sentiment of your message, I am curious ; have there been any instances where an internet provider has been found liable (criminally or civilly) for willfully misrepresenting IP geolocation information? How could there be