Resolved after 1 hour 59 minutes, affecting API and Mobile App and 1 more, on February 11, 2025.
The operations team received internal alerts about periodic service restarts in our infrastructure. The affected service was the primary backend API server that serves traffic to all of the Jeenie applications. This was investigated immediately, but no clear signals of resource constraints in our monitoring systems were found that could explain the service restarts. During this time frame, the affected system also looked to be automatically recovering quickly. Occasional internal service restarts are expected and don’t typically affect the end-user experience on the platform. As there was no clear signal to investigate, and affected systems looked to have recovered as expected, the team opted not to make any infrastructure changes, but to continue monitoring the situation instead. During this time, users would have intermittently experienced some slowness in the platform, or occasional errors when logging in and attempting to create calls.
Affected components
Update timeline
- investigating Feb 11, 2025, 11:04 PM UTC
Jeenie's services had increased response. Users may intermittently have experienced delays when attempting to log in or create calls.
- resolved Feb 11, 2025, 11:07 PM UTC
Jeenie's services had increased response. Users may intermittently have experienced delays when attempting to log in or create calls.
- postmortem Feb 12, 2025, 10:01 PM UTC
The operations team received internal alerts about periodic service restarts in our infrastructure. The affected service was the primary backend API server that serves traffic to all of the Jeenie applications. This was investigated immediately, but no clear signals of resource constraints in our monitoring systems were found that could explain the service restarts. During this time frame, the affected system also looked to be automatically recovering quickly. Occasional internal service restarts are expected and don’t typically affect the end-user experience on the platform. As there was no clear signal to investigate, and affected systems looked to have recovered as expected, the team opted not to make any infrastructure changes, but to continue monitoring the situation instead. During this time, users would have intermittently experienced some slowness in the platform, or occasional errors when logging in and attempting to create calls.
Your product runs on more than Jeenie
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