Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Jenji and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Jenji.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
View the latest incidents for Jenji and check for official updates:
Description: 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.
Status: Postmortem
Impact: Critical | Started At: Feb. 1, 2023, 7:30 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 25, 2022, 12:21 p.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: May 25, 2022, 7:30 a.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: Dec. 28, 2021, 6 a.m.
Description: 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.
Status: Postmortem
Impact: Minor | Started At: July 26, 2021, noon
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.