We’ve begun advertising a new subnet to our Level3 transit and were required to setup a route object for our prefix which is now in place. 

route:           37.0.5.0/24
descr:           Workday Limited
origin:          AS198993
mnt-by:          MNT-WORKD-EU
changed:         amanda.galligan@workday.com 20141001
source:          RIPE

 


We have a pre-existing as-set object that is being used by Level3 import policy to update their filters with our advertised routes 


as-set:          AS-Workday-AMS-L3peer
descr:           Workday Limited
members:         AS198993
tech-c:          VAZ28-RIPE
admin-c:         VAZ28-RIPE
mnt-by:          mnt-workd-eu
source:          RIPE # Filtered

When we use the following whois check we only see our existing subnet 37.0.4.0/24 listed and not 37.0.5.0/24 

bash-4.1$ whois -h filtergen.level3.net RIPE::AS-Workday-AMS-L3peer
Prefix list for policy RIPE::AS-Workday-AMS-L3peer =
RIPE::AS198993

37.0.4.0/24

However this prefix is clearly available below. 

arg@$ whois AS-Workday-AMS-L3peer | grep members |awk '{print $2}' | xargs whois -i origin  | grep route
route:          37.0.4.0/24
route:          37.0.5.0/24
arg@Ubuntu02:~/code/tools$


Level3 are saying that we need to associate 37.0.5.0/24 with AS198993 which is already in place an wait two days for update but its been over two days and this still hasn’t been updated. 
Upon contacting Level3 they informed us that we need to do following but I’m not clear on what they are actually looking for us to do here? 


***************************************************
[CUSTOMER UPDATE]   EMEA Technical Service Centre
[SUMMARY OF WORK]
To update the prefix-list, you need to update your  RIPE::AS-Workday-AMS-L3peer import policy  RIPE::AS-Workday-AMS-L3peer  with all the prefixes you are advertising. Once done, our prefix-list will be automatically updated from RIPE (this process takes up to 48 hours).
Please do keep your import policy up to date for more flexibility and allow up to 48 hours to our automatic process to complete once your routing registry is updated.


Any advise on where I’m going wrong here greatly appreciated.. I’ve done this previously for 37.0.4.0/24 and didn’t need to do anything additional to what I’ve already done above. 

Amanda