From amanda.galligan at workday.com Thu Oct 2 17:59:04 2014 From: amanda.galligan at workday.com (Amanda Galligan) Date: Thu, 2 Oct 2014 15:59:04 +0000 Subject: Updating import policy Level3 issues Message-ID: 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 at 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 at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bigpumo at gmail.com Mon Oct 13 11:12:32 2014 From: bigpumo at gmail.com (Enzo Ghinazzi) Date: Mon, 13 Oct 2014 11:12:32 +0200 Subject: Fwd: [ripe.net #1140111] AutoReply: API Country resource incongruency In-Reply-To: References: Message-ID: Not sure if right place here and followed notification procedure to stat at ripe.net [ticket #1140111]... I've found some *missing prefix/asn* returned from query to COUNTRY RESOURCE https://stat.ripe.net/data/country-resource-list/data.json?resource=it It seems that response list is missing all those ipv4 resource lines that before were returned as RANGE instead of CIDR, and obviously related asn. For example 151.3.0.0/16 is related to country IT ( https://stat.ripe.net/data/whois/data.json?resource=151.3.0.0/16) but* this prefix and its ASN is missing in response country resource list* of above query. Earlier ,sure at 13 JUL 2014, this prefix was in response as contained in range 151.3.0.0-151.84.255.255. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stephen.Barker at virtual1.com Fri Oct 24 12:11:55 2014 From: Stephen.Barker at virtual1.com (Stephen Barker) Date: Fri, 24 Oct 2014 10:11:55 +0000 Subject: previous registration for 217.33.191.128/27 Message-ID: <1EB2FB40A1E25A48883E0CE248457ADE0137A97CA7@PDC001.virtual1.local> Good Morning, I have a customer that is requesting a large block of IPs and has advised that they are/ have returned the below address block. They did state that they believe it has been re-assigned. Would anyone be able to advise how I can check the history of the allocations of this range? The customer is Brightside Group. 217.33.191.128/27 Current DB information; inetnum: 217.33.191.128 - 217.33.191.159 netname: EDEVELOPMENT descr: FTIP003191590 eDevelopment Ltd country: GB admin-c: CG5480-RIPE tech-c: CG5480-RIPE status: ASSIGNED PA mnt-by: BTNET-MNT mnt-lower: BTNET-MNT mnt-routes: BTNET-MNT remarks: Please send abuse notification to abuse at bt.net remarks: Please send delisting issues to btnetdns at bt.net remarks: This range is statically assigned source: RIPE # Filtered Thanks Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From kazakevichilya at gmail.com Fri Oct 24 12:50:57 2014 From: kazakevichilya at gmail.com (Ilya Kazakevich) Date: Fri, 24 Oct 2014 14:50:57 +0400 Subject: previous registration for 217.33.191.128/27 In-Reply-To: <1EB2FB40A1E25A48883E0CE248457ADE0137A97CA7@PDC001.virtual1.local> References: <1EB2FB40A1E25A48883E0CE248457ADE0137A97CA7@PDC001.virtual1.local> Message-ID: https://stat.ripe.net/217.33.191.128-217.33.191.159?sourceapp=ripedb#tabId=at-a-glance * Last updated on *2011-05-05* at *13:33:25 UTC*. * RIPE NCC members can access historical information by signing in with their LIR's RIPE NCC Access account. On Fri, Oct 24, 2014 at 2:11 PM, Stephen Barker wrote: > Good Morning, > > > > I have a customer that is requesting a large block of IPs and has advised > that they are/ have returned the below address block. They did state that > they believe it has been re-assigned. > > > > Would anyone be able to advise how I can check the history of the > allocations of this range? The customer is Brightside Group. > > > > 217.33.191.128/27 > > > > Current DB information; > > > > inetnum: 217.33.191.128 - 217.33.191.159 > netname: EDEVELOPMENT > descr: FTIP003191590 eDevelopment Ltd > country: GB > admin-c: CG5480-RIPE > tech-c: CG5480-RIPE > status: ASSIGNED PA > mnt-by: BTNET-MNT > mnt-lower: BTNET-MNT > mnt-routes: BTNET-MNT > remarks: Please send abuse notification to abuse at bt.net > remarks: Please send delisting issues to btnetdns at bt.net > remarks: This range is statically assigned > source: RIPE # Filtered > > > > > > Thanks > > Steve > > > > > Any prices quoted in this email are for indicative purposes only and are > subject to further technical appraisal. Additional installation charges may > apply and all orders are subject to survey. Unless otherwise specified, > prices are in GB Pounds and exclude VAT (or equivalent taxes). Acceptance > of any proposal contained in this email is subject to formal contract. Any > views or opinions expressed are solely those of the author and do not > necessarily represent those of Virtual1. > > Virtual1 is registered in England and Wales with company number 6177891. > Our registered address is: 8 Angel Court, London, EC2R 7HP > > This communication may contain confidential information. It may also be > the subject of legal professional privilege and/or under copyright. If you > are not an intended recipient, you must not keep, forward, copy, use, save > or rely on this communication, and any such action is unauthorised and > prohibited. If you have received this communication in error, please reply > to this e-mail to notify the sender of its incorrect delivery, and then > delete both it and your reply. > -------------- next part -------------- An HTML attachment was scrubbed... URL: