Hi Hank! Apologies for the delayed response. I'd like to provide you with an update on the current status.
On one hand, we have deployed features to mitigate issues related to making updates with multiple references (#1486). This prevents the creation of an RPSL with a lot of references. We are continuing to investigate ways to further improve this process. On the other hand, the second round of notification you received was due to some notifications bouncing back and being incorrectly handled as mail updates instead of bounced messages. We have addressed this issue by correctly handling these messages as Multipart/mixed Bounced and Auto-submitted Messages (#1490). We are actively monitoring the situation to ensure the issue is resolved and to determine if additional features are necessary. We will publish a post-mortem once we are confident the issues raised have been mitigated. Thank you for your patience and understanding. Regards Miguel Herrán RIPE NCC On Mon, 1 Jul 2024 at 18:39, Hank Nussbacher via db-wg <[email protected]> wrote: > > > Dear colleagues, > > > > We are aware of an incident affecting Whois updates yesterday > > evening, which we are continuing to investigate. We will keep > > the DB-WG informed. > > > > Regards > > Ed Shryane > > RIPE NCC > > Hi. > > It has been 2 weeks. Did I miss an email on the matter? > > Regards, > Hank > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg >
-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
