![]() Create Geofeed File and Publish with IP RegistryĪpart from creating geofeed records on, you should also create geofeed file on your website on the below location: Here, as you can see, we have added our IP subnets and manually added their country, region, city, and zip code on the OpenGeoFeed site dashboard. So, if you add your subnet geolocation information on their website, then major GeoIP database websites will crawl this data and correct their database. is a open-source project to help IP subnet holders to update geoinformation on their end, and all major GeoIP databases regularly crawl this website database to correct their geolocation data. That’s why all of the 3 steps mentioned in this documentation are vital to get your IP subnet information corrected. If your provided GeoIP information does not match your BGP announcement, then they may reject/ignore your correction request. ![]() Please note, these GeoIP database sites may take from one week to months to update the correct GeoIP information on their database based on your provided data and BGP information. Below are some major GeoIP database sites, where you can send your IP correction request. The third step is vital if the above two steps are properly resolved by your end, then you need to contact major IP database sites in order to correct your subnet GeoIP information as soon as possible. In such cases, you can contact RADb team to remove such legacy route objects from their site. You may also find multiple legacy route objects on by the previous IP subnet holder, which are not in currently use, but still may affect your network performance by increasing latency and ping drop. ![]() If not, then you need to contact your IP registry to do the route object on your ASN / your data center ASN for you. You need to check on whether your ASN / your data center ASN is showing there like this or not. You need to do the route object before the BGP announcement because all major ISPs verify ROA and IRR during the BGP announcement and propagation. Make sure that, your object route is visible on with your ASN (if you have your own ASN) or your data center ASN (if you don’t have your own ASN). Secondly, you need to ask your upstream provider/data center if they have successfully BGP announced your subnet on their network or not. You can check from the below whois (select once from where the IP subnet has been registered): The very first thing, is you need to make sure that your IP registry shows the right geolocation information or not on their official whois. If you have a newly allocated subnet, and if you have already BGP announced the subnet with your datacenter, but the IP whois still showing wrong GeoIP information, then you need to follow some steps: Update Address Information on IP Registry
0 Comments
Leave a Reply. |