Is Jenji Down Right Now? Check if there is a current outage ongoing.

Due to a bug in the Billing subsystem running our monthly invoicing, databases have been saturated. The bug has been fixed and traffic has gone back to normal. We are evaluating how to spot these regressions in the future without draining capacity.

We're experiencing an elevated level of API latency affecting Web traffic and are currently looking into the issue.

This incident has been resolved.

Dear Jenji user, our preferred partner, KPMG, is currently experiencing technical issues on its platform. Indeed, Jenji Vault, our e-archiving feature is facing an elevated level of errors in the following countries: Luxembourg, Netherlands, Belgium, UK, Poland, Austria and Germany. France and Switzerland are not affected. We are currently in contact with KPMG in order to have the latest news. KPMG will inform us as soon as the service is again available. During that time, if you e-archive, Jenji is keeping the data safely. They will be automatically synchronized as soon as the service is fully available.

September 6th, 13:57pm - degradation detected in the API responses of our supplier for legal e-archiving in France \(“500 Internal Server Error” and “401 Non autorisé“\). September 6th, 15:37pm - A ticket was opened by the Jenji Engineering team, with supplier number INC-23287. September 6th, 16:05pm - the errors were acknowledged by our supplier, and work started on their end on the analysis. September 7th, 17:35pm - the queued files were successfully all synced and traffic went back to normal. September 9th, 13:59pm - our supplier increased the resources allocated to the service to prevent further outages.

We're experiencing an elevated level of Vault France errors and are currently looking into the issue. No data is at risk.

December 28th, 7:00pm - our supplier for legal e-archiving in France deployed a security fix to prevent log4shell exploitation, and the fix wrongly flagged a large number of uploads that resulted in “Connection reset by peer \(Write failed\)“ errors. December 28th, 7:35pm - A ticket was opened by the Jenji Engineering team, with supplier number INC-27857. December 28th, 8:04pm - the errors were acknowledged by our supplier, and work started on their end on reworking the security fix. December 30th, 2:00pm - the updated security fix was successfully deployed in production to their systems. December 30th, 11:23pm - the queued files were successfully all synced and traffic went back to normal.

We're experiencing an elevated level of Vault France errors and are currently looking into the issue. No data is at risk.

May 25th, 9:54am - our monitoring showed elevated latency on the iOS signup API calls, in p95 and p99 latencies. Users clicking the Signup \(not Login\) button on iOS have a longer wait time than normal. May 25th, 10:02am - we identified the root cause, hitting the AWS service limit on concurrent lambda execution in this specific AWS account, making some of those calls timeout or take up to 10-15 seconds. May 25th, 10:18am - a fix has been pushed to production, the iOS signups are back to normal.

We're experiencing an elevated level of API latency affecting iOS signups and are currently looking into the issue.