Resolved after 6 hours 35 minutes, affecting section-151244 (LRI General Availability) and section-151244 (API) and 1 more, on March 12, 2025.
Root Cause A bug introduced in our latest release caused database connections to close incorrectly. Around 1:10 am CET on March 12, this triggered a failure in new database connections and led to a crash of our backend services. Resolution All services were fully restored by 8:10 am CET following a manual restart. We deployed an emergency hotfix to resolve the underlying issue and have enhanced our monitoring to detect similar problems more quickly in the future. We appreciate your understanding and apologize for any disruptions caused.
Affected components
Update timeline
- investigating Mar 12, 2025, 12:35 AM UTC
Incident Summary From 1:36 am CET on March 12, our platform experienced an unexpected outage. Services were unavailable during this period. We sincerely regret any inconvenience caused.
- resolved Mar 12, 2025, 07:10 AM UTC
Root Cause A bug introduced in our latest release caused database connections to close incorrectly. Around 1:10 am CET on March 12, this triggered a failure in new database connections and led to a crash of our backend services. Resolution All services were fully restored by 8:10 am CET following a manual restart. We deployed an emergency hotfix to resolve the underlying issue and have enhanced our monitoring to detect similar problems more quickly in the future. We appreciate your understanding and apologize for any disruptions caused.
Your product runs on more than Munich Re Risk Suite
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services