The RIPE NCC RPKI repository became inconsistent and outdated starting on 
Saturday, 2 Feb 2013 that lasted for several hours. This was caused by a 
problem in our RPKI system that degraded performance to a point where the 
publication for all 1300+ Member CAs combined took more than 24 hours. This 
meant the CRLs and manifests for some CAs expired before they republished.

The bug that caused the problem has been fixed and we are making sure the 
robustness and monitoring of the system is further improved. We are also taking 
steps to ensure that the scaling of the system keeps pace with the adoption by 
our members. 

In case you notice a problem with one of our services, please check our web 
page with known service and security announcements:
http://www.ripe.net/lir-services/service-announcements

If you suspect a serious incident or outage with a critical RIPE NCC service 
that is not shown here, please contact the RIPE NCC Technical Emergencies 
Hotline:
http://www.ripe.net/contact/technical-emergency-hotline

If you have any questions, please let us know.

Cheers,

Alex
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to