Cogent Communications
BGP Questionnaire

I.  CUSTOMER INFORMATION

    Company Name:  
    BGP Order Number:
    Tech Contact 1:  
    Tech Contact 2:  

II.  BGP SERVICE - All requests for BGP peering must have a valid BGP4 and/or BGP6 order ID.

 ##########################################################################################################

                                                    NOTE                          
 This ASN must be registered to the same company with the Regional Internet Registry as the company named on    
 the Cogent Communications contract.  If it is not, you will be required to provide an LOA from the owner
 of the registered resources.

 ###########################################################################################################

 1. Please provide the Cogent port/LAG bundle order ID(s) that require BGP routing:



 2. Autonomous System Number (ASN) - Please check the appropriate box for your network.

    [   ]  I will be announcing my routes to you via ASN(s):  

    [   ]  I need a private ASN to speak BGP at more than one Cogent location, but to no other ISP.
	   Indicate the Cogent Port order numbers for your other locations:


           Customers needing private AS BGP will only be allowed to announce out Cogent IP space.


 3. BGP session password (Optional):  

 4. If you have an AS-Set registered in a routing database and wish to have Cogent use it to automatically 
    update our prefix database, provide it here:



##########################################################################################################
                      NOTE
    Cogent does not automatically push out these prefixes to our routers.  You will need to notify our 
    Support department to push out the changes to your prefix filters.

    Cogent uses RADB to pull prefixes, if you have provided us with an AS-Set.  

    For a complete list of the databases RADB mirrors, visit - http://www.irr.net/docs/list.html#RADB
##########################################################################################################

 5.  IP Address Blocks to Announce:
     








    Cogent will automatically add 'le 24' tags on IPv4 prefixes, and ‘le 48’ tags on IPv6 prefixes.

 6. BGP Peering Requirements – Select one of the following:

       [   ]  Full
       [   ]  Full (detailed)
          --OR--
       [   ]  Cogent Backbone & Cogent Customer routes
       [   ]  Cogent Backbone & Cogent Customer routes (detailed)
       
          --AND/OR--
       [   ]  Default Route

              Detailed routes are de-aggregated announcements within the Cogent network.
              
              Cogent recommends at least 3gig of DRAM for a full route table.


 7.  Black Hole Server (Optional)

       [   ]  Please set up a BGP peer on the Cogent Black Hole server

       Black Hole server password (REQUIRED):  
       Black Hole server peer IP:  

       North American IPv4 Black Hole Peer:  66.28.8.2
       European Union IPv4 Black Hole Peer:  130.117.20.2

       North American IPv6 Blackhole Peer:   2001:550:0:1000::421c:802
       European Union IPv6 Blackhole Peer:   2001:550:0:1000::8275:1402

   #########################################################################################################
   
   The Cogent Black Hole server will allow customers to announce a /32 IPv4 route and a /128 IPv6 route to 
   Cogent and have all traffic to that network blocked at Cogent's backbone.  

   All peers on the Cogent black hole server require a password.                                                                                               
   ##########################################################################################################

III.  ADDITIONAL COMMENTS (add additional sheets as necessary)




View Cogent forms at http://www.cogentco.com/Guide/
View Cogent's IP Allocation Policy at http://www.cogentco.com/Guide/IP_Allocation_Policy.txt


http://www.cogentco.com/Guide/BGPQ.txt                                               BGPQ-v6.6 12/16/2015