Jeenie Outage History
Jeenie is up right nowPingoru has recorded 21 incidents for Jeenie: 4 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 4 of 572 (1%) |
Incidents, newest first
Minor October 19, 2026 Jeenie TeleJeenie and add a Participant Intermittently Working 3h 52m PSTN Dial Out, TeleJeenie
Started Oct 19, 2026, 05:27 PM UTC· resolved Oct 19, 2026, 09:20 PM UTC
- identified Oct 19, 2026, 05:27 PM UTC
We are aware of increased reports regarding issues with the TeleJeenie service and the add participant function. Jeenie has identified the root cause as an issue with an upstream vendor. We escalated the matter to urgent status with the vendor, and their team is actively troubleshooting. We will provide another update as soon as we receive information from the upstream vendor.
- identified Oct 19, 2026, 07:14 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 19, 2026, 07:16 PM UTC
TeleJeenie calls, including adding a participant, are connecting and completing normally again. We’re monitoring closely and will send an update once it’s fully resolved.
- resolved Oct 19, 2026, 09:20 PM UTC
We've seen sufficient evidence of call activity that we believe this issue is resolved.
Major December 18, 2025 Intermittent Connection Issues 1h 45m Mobile App, Web App, PSTN Dial Out, TeleJeenie
Started Dec 18, 2025, 09:43 PM UTC· resolved Dec 18, 2025, 11:28 PM UTC
- investigating Dec 18, 2025, 09:43 PM UTC
Jeenie is currently investigating an issue that is intermittently preventing interpreters from connecting to calls on certain platforms.
- investigating Dec 18, 2025, 09:59 PM UTC
Clients are experiencing connection issues when placing TeleJeenie calls. Jeenie is still investigating the root cause of the TeleJeenie issue. We are working with our upstream vendor to quickly resolve this issue.
- resolved Dec 18, 2025, 11:28 PM UTC
We've seen sufficient evidence of call activity to confirm this issue is resolved.
Major November 29, 2025 Jeenie TeleJeenie and add a Participant Inaccessible 2h 41m API, Mobile App, A/V Sessions, Web App and 3 more
Started Nov 29, 2025, 05:27 PM UTC· resolved Nov 29, 2025, 08:09 PM UTC
- identified Nov 29, 2025, 05:27 PM UTC
We are aware of increased reports regarding issues with TeleJeenie service and the add participant function. Jeenie has identified the root cause as an issue with an upstream vendor. The matter has been escalated to urgent status with the vendor, and their team is actively troubleshooting. We will provide another update as soon as we receive information from the upstream vendor.
- resolved Nov 29, 2025, 08:09 PM UTC
We've seen sufficient evidence of call activity that we believe this issue is resolved.
Critical October 15, 2025 Jeenie TeleJeenie and add a Participant Temporarily Inaccessible 5h 11m API, PSTN Dial Out
Started Oct 15, 2025, 06:05 PM UTC· resolved Oct 15, 2025, 11:16 PM UTC
- identified Oct 15, 2025, 06:05 PM UTC
We are aware of increased reports regarding issues with TeleJeenie service and the add participant function. Jeenie has identified the root cause as an issue with an upstream vendor. The matter has been escalated to urgent status with the vendor, and their team is actively troubleshooting. We will provide another update as soon as we receive information from the upstream vendor.
- resolved Oct 15, 2025, 11:16 PM UTC
We've seen sufficient evidence of call activity that we believe this issue is resolved.
Minor September 2, 2025 Jeenie Running in Downgraded State 2h 9m API, Mobile App, A/V Sessions, Web App and 3 more
Started Sep 02, 2025, 03:02 PM UTC· resolved Sep 02, 2025, 05:11 PM UTC
- investigating Sep 02, 2025, 03:02 PM UTC
Jeenie's services had increased response times. Users may intermittently experience delays when attempting to log in or create calls.
- monitoring Sep 02, 2025, 04:28 PM UTC
The issue that was causing the downgraded state has been fixed. We are actively monitoring the fix we implemented.
- resolved Sep 02, 2025, 05:11 PM UTC
After monitoring the fix, we have put in all systems are functioning normally. This issue has been resolved. If you are experiencing any new issues, please reach out to [email protected].
Critical August 21, 2025 Jeenie TeleJeenie Services are Temporarily Inaccessible 5h 13m TeleJeenie
Started Aug 21, 2025, 11:53 AM UTC· resolved Aug 21, 2025, 05:07 PM UTC
- investigating Aug 21, 2025, 11:53 AM UTC
We have received reports of increased instances of incoming calls via TeleJeenie calls ending before connecting to an interpreter. We are investigating this issue with upstream providers and will provide an update within 1 hour.
- monitoring Aug 21, 2025, 02:13 PM UTC
Jeenie deployed a fix that restored TeleJeenie to an operating state. We'll continue to monitor it over the next couple of hours to ensure no further issues arise.
- resolved Aug 21, 2025, 05:07 PM UTC
After a couple of hours of monitoring, we've confirmed the issue is resolved. Please reach out to [email protected] if you have any questions.
Major August 5, 2025 Inbound TeleJeenie service degradation 4h 27m PSTN Dial Out, TeleJeenie
Started Aug 05, 2025, 07:29 PM UTC· resolved Aug 05, 2025, 11:56 PM UTC
- monitoring Aug 05, 2025, 07:29 PM UTC
We have identified an issue with our TeleJeenie services, and our upstream vendor has confirmed the issue is on their side. The upstream vendor is continuing to troubleshoot and resolve the issue. We will send an update once our upstream vendor has resolved the issue.
- resolved Aug 05, 2025, 11:56 PM UTC
We've seen sufficient evidence of call activity that we believe this issue is resolved
Major February 11, 2025 Partial Outage 30m API, Mobile App, A/V Sessions, Web App and 3 more
Started Feb 11, 2025, 08:00 PM UTC· resolved Feb 11, 2025, 08:30 PM UTC
- investigating Feb 11, 2025, 11:11 PM UTC
Jeenie's services had significantly increased response times and increased error rates for approximately 30 minutes. Users would have experienced significant delays, or failures when attempting to log in, and when initiating calls.
- resolved Feb 11, 2025, 11:13 PM UTC
We identified the source of the increased response times and error rates, and made adjustments to our resource allocations to address the latency.
- postmortem Feb 12, 2025, 10:15 PM UTC
**Impact description** The operations team had been monitoring a period of intermittent degraded performance from earlier in the day, and began receiving a significantly increased rate of alerts about internal service restarts. It quickly became clear that the affected service was not automatically recovering as it typically would. At this time, the team was still unable to see any clear clear signs of resource constraints that would explain the inability of the service to recover. Recent changes to infrastructure, or service code, had also already been ruled out earlier in the day, as there were no significant changes of relevance. The team was ultimately able to correlate the increase in service restarts with an increase in log messages from the affected service that demonstrated an internal failure to communicate with the primary database service. That was initially confusing because it did not align with any clearly visible resource constraints that would explain it, as the upstream database service was performing nominally. **Initial response** Understanding that there must be a resource constraint somewhere that would impair the service’s ability to communicate with the primary database, the team opted to make some immediate infrastructure adjustments to mitigate the situation: * doubled the number of service instances available * doubled the amount of memory, and memory limits, allocated to each service instance The combinations of these updates allowed the service to have enough operating headroom to recover once it was redeployed. After deploying these changes, service returned to normal within a couple of minutes. During this time, customers would have experienced widespread slowness, and frequent errors preventing logins and creating calls on the platform. While some calls were still being fulfilled during this time, many customers would have experienced a significant impact. **Root cause** With the service returned to normal operations, the team continued to investigate possible root causes. After a very thorough review, the team ultimately determined the following: * the maximum number of database connections internally allowed per service instance had become an invisible bottleneck that triggered a cascading series of failures * as one service instance exhausted the number of database connections it was allowed to have, traffic would begin to rapidly pile up on that instance, causing a very quick spike in memory usage. This spike was often too quick to clearly distinguish in our monitoring systems, and so it was not clear from monitoring tools that this was a recurring cause for service restarts * the infrastructure would then respond as expected and restart the affected service instance, as it was exceeding the amount of memory it was allowed to use * as the service instance was restarting, the traffic it was handling would be redistributed onto the other service instances * the immediate increased load in the other service instances would then trigger the same saturation of database connections, and resulting memory use, causing the infrastructure to restart those instances as well * as individual service instances restarted, they would very quickly become overloaded due to traffic being redistributed from other overloaded instances, thus leading to a loop of service restarts **Response plan** The team has a number of near term changes planned to mitigate the risk of this type of failure in the future. Those upcoming changes include: * Significant increase in number of active database connections allowed per service instance * Reconfigure internal services that manage the connection between the affected service and the primary database, which should reduce latency between the two and be simpler to monitor * Make a series of updates to the database that will improve the performance of frequently used queries * Review areas where improved internal instrumentation and monitoring could provide a leading indicator for this type of issue in the future These changes, when taken together, will significantly reduce the risk of a similar situation in the future.
Minor February 11, 2025 Jeenie Degraded Service 1h 59m API, Mobile App, A/V Sessions, Web App and 3 more
Started Feb 11, 2025, 06:00 PM UTC· resolved Feb 11, 2025, 08:00 PM UTC
- 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.
Critical February 11, 2025 Brief Maintenance Outage 29m API, Mobile App, A/V Sessions, Web App and 3 more
Started Feb 11, 2025, 03:15 AM UTC· resolved Feb 11, 2025, 03:45 AM UTC
- investigating Feb 11, 2025, 11:15 PM UTC
During our off-hours maintenance window, Jeenie experienced an issue with services returning to normal.
- resolved Feb 11, 2025, 11:17 PM UTC
Jeenie experiences an unexpected 30-minute outage during a regularly scheduled off-hours maintenance window. Some services did not fully restart as expected during maintenance operations and required manual intervention to bring them back online.
- postmortem Feb 12, 2025, 09:55 PM UTC
A weekly, off-hours automated maintenance update resulted in a critical internal caching service not fully restarting as expected. The operations team was notified within minutes and intervened to restore the affected internal component to service. Our team is evaluating mitigating future risk by moving the affected service out of the infrastructure that receives these automated maintenance updates, so that it is managed independently.
Major November 20, 2024 IOS Mobile App Connection Working Intermittently 6h 15m Mobile App
Started Nov 20, 2024, 02:30 PM UTC· resolved Nov 20, 2024, 08:45 PM UTC
- investigating Nov 20, 2024, 06:41 PM UTC
We are currently investigating an issue with our iOS app that is affecting the ability to log in and make calls.
- identified Nov 20, 2024, 07:27 PM UTC
The issue has been identified and a fix has been submitted for review to the Apple App Store. We will resolve this incident once the new version is available for download.
- resolved Nov 20, 2024, 08:45 PM UTC
A new version of the iOS app that resolves this issue is available for download on the Apple App Store. Users of the iOS app may continue to see inconsistent call history until the end of the month, but this will be reconciled. Please reach out to support if you have further questions.
Critical November 14, 2024 Jeenie Services Temporarily Inaccessible 18m API, Mobile App, A/V Sessions, Web App and 3 more
Started Nov 14, 2024, 05:43 PM UTC· resolved Nov 14, 2024, 06:01 PM UTC
- identified Nov 14, 2024, 05:43 PM UTC
Clients are not able to reach Jeenie's services. We've identified the issue and are in the process of resolving it. We will update here once the resolution is in place.
- resolved Nov 14, 2024, 06:01 PM UTC
Jeenie has implemented the fix that caused the outage. Please reach out to [email protected] if you have any questions.