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/[email protected]/
[routing-wg] network failed, was re: Notification of RIPE Database changes
- Previous message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
- Next message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Sat Jun 15 16:11:29 CEST 2013
> This morning we experienced downtime but we managed to recover within > a few hours due to a last minute warning issued to our upstream > provider Cybersmart (original message pasted below bottom). > > From what I can gather I can hypothesise that our previous upstream > provider Frogfoot, had created a route object in your database without > our knowledge or authority. Subsequently they relinquished control of > this object to their new upstream (AfricaINX in the email below) > without our knowledge or authority. And subsequently AfricaINX deleted > this object from your database without our authority or knowledge. > And finally our new upstream created a route object in your database > without our knowledge or authority. [ aside from a side rant about rpki certificates ] has anyone at the ncc looked into this and can give us a post mortem? it is a bit scary. randy
- Previous message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
- Next message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]