<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> </head> <body style="background-color: rgb(255, 255, 255); color: rgb(0, 0, 0); font-family: Tahoma; font-size: 16px;" text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 24/Nov/16 11:26, Angel Martinez Sanchez wrote: </div> <blockquote type="cite" cite="mid:E1c9qIE-0003Ae-JH@www-apps-1.ripe.net" style="border-left: 2px solid #009900 !important; border-right: 2px solid #009900 !important; padding: 0px 15px 0px 15px; margin: 8px 2px; background-color: null !important; color: null !important;"> <pre wrap="">Hello, We are going to migrate from our actually datacenter to another one. We have /22 IPs block and not have AS number, our datacenter announce them. Our plan is as follows: - We already add new route objects before migration and will remove old after migration. - At dawn on Sunday, November 27 about 3:00 AM, we will shut down all our servers from the current data center. - At that point we will delete the current route ASXXXX in RIPE DB from inetnum XXX.XXX.XX.0/22 and only the route object corresponding to new datacenter will remain. - We will contact new datacenter to activate our IP block on their router and configure the requested gateway. - We will dismantle the entire rack from old datacenter and move it to the new datacenter where we will start up all our servers again. We need to know if the procedure is correct and very important, the time it takes to propagate the new route of our IP block since we delete the current ASXXXXX and the new ASXXXX is activated by new datacenter. We also need to know if we depend on any action by the current data center to complete this procedure. For example, if they have to remove our block from their AS or their router and that would happen in case they refused to do so on the date indicated for the migration.</pre> </blockquote> Provided your new provider creates a route object that maps to their ASN beforehand, you need a minimum of 24hrs (and at most 72hrs) for networks around the world that filter based on RPSL to pick up the changes. It's not an issue if both route objects exist for the transition. So I'd take down the old one after you've completed the migration. The main thing is to ensure the new route object has time to bake in before you move over. Mark. </body> </html>