Hi guys Historical queries to the RIPE Database only go back as far as the 'most recent' creation. So you can see changes made to the currently existing INETNUM object. If the object has been deleted and re-created it is not possible to query for the previous incarnation of the object. This was an arbitrary decision made when the historical query feature was introduced. The data is still available in the RIPE Database for all previous incarnations of an object. It has been suggested in the past that this service be extended to show all previous history (excluding personal data). If there is sufficient interest, maybe someone would like to propose such a change and it can be looked into in more detail. cheersdenis co-chair DB-WG On Tuesday, 10 December 2019, 13:16:08 CET, Roland Perry <roland@internetpolicyagency.com> wrote: In message <20191210114312.GJ72330@Space.Net>, at 12:43:12 on Tue, 10 Dec 2019, Gert Doering <gert@space.net> writes
Hi,
On Mon, Dec 09, 2019 at 05:47:26PM +0000, Roland Perry wrote:
My question is this: how can the organisations responsible for that former life be identified (in general terms) so that the end users can at least given a plausible explanation for why their connectivity has been so badly affected.
As far as I know, all the new ISP is prepared to divulge is "we are working on it", and all the users' IT departments are prepared to divulge is "Our new ISP says he's working on it".
If this is ISP-managed space ("provider aggregateable", PA, in RIPE lingo) this is a matter between the end customer and their ISP.
If(!) the ISP has been well-behaving RIPE member and documenting their assignments in the RIPE DB, the historic snapshots of the inetnum records will shed light.
How do I as (nowadays anyway, an outsider) access such historic snapshots of the IP address range, before today's ISP acquired them. Is this a 'service' that RIPE NCC offers (and hence my question in this forum). Sometimes the answer is "we aren't allowed to tell you - because of data protection". But I suspect the dirt was acquired by a user outside the EU, and hence arguably outside the protection of EU DP law.
But I see this as somewhat unlikely, as it seems the ISP is unwilling to fix up the mess they created for their new customer.
I'd just send laywers their way - "you gave us these addresses, they are close to unusable, go fix things or give us clean ones, or we'll change ISPs again and you pay for all costs incurred"...
If I were the admins in this case, I would have (weeks ago) demanded "some new clean ones", seeing as how the process of cleaning the current ones is proving less than adequate. But unfortunately the customer organisation is part of a consortium, and you'd need to get a lot of *other* members on side. Being able to say who attracted the dirt, is my motivation for assisting in an attempt to get a critical mass of consortium members to act. -- Roland Perry