This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] So what happened last night to the DB?
- Previous message (by thread): [db-wg] So what happened last night to the DB?
- Next message (by thread): [db-wg] So what happened last night to the DB?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Wed Jul 3 12:24:52 CEST 2024
Hi Ed On Wed, 3 Jul 2024 at 11:09, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > > Hello Hank, > > > On 2 Jul 2024, at 14:24, Hank Nussbacher via db-wg <db-wg at ripe.net> wrote: > > > > On 02/07/2024 10:44, Miguel Mosquera via db-wg wrote: > > > > Thanks. The initial incident happened on June 17 and a subsequent incident on June 24. Were all your fixes as listed below, performed post June 24? > > > > We implemented two fixes in response to the incidents in June. > > The fix for multiple references was deployed on June 24th in release 1.112.1. What is the fix that you have deployed? Does it have any operational impact? For example a limit on the number of MNTNER objects that can be referenced or changes to the way MNTNERs are referenced. cheers denis > > The fix for handling bounced messages was deployed on Monday July 1st in release 1.113.2. > > Regards > Ed Shryane > RIPE NCC > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [db-wg] So what happened last night to the DB?
- Next message (by thread): [db-wg] So what happened last night to the DB?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]