Tangoe Mobile Outage History

Dear Tangoe User, Tangoe experienced external connectivity issues at the Tangoe Production Data Center impacting our secure file transfer protocol (SFTP) servers and eft.tangoe.com. Any data uploaded to eft.tangoe.com between 2:49 PM Eastern thru 4:17 PM Eastern may need to be uploaded again. There is no risk of incorrect files or wrong data being passed to the SFTP sites. It is highly suggested that all owners re-run / check their processes for accurate results following this interruption. Sincerely, IT Production Support [email protected]

Our secure file transfer protocol (SFTP) servers and eft.tangoe.com are now fully restored. Any data uploaded to eft.tangoe.com between 10:30 AM Eastern thru 2:51 PM Eastern may need to be uploaded again. There is no risk of incorrect files or wrong data being passed to the SFTP sites. It is highly suggested that all owners re-run / check their processes for accurate results following this interruption.

We are pleased to share that Amazon Web Services (AWS) has reported continued recovery across all impacted services, and we are no longer observing any degradation. Our infrastructure and applications remain fully operational, and our ability to scale additional servers has been restored. We will continue to monitor AWS updates closely to ensure full stability and optimal performance across our platforms.

The Amazon Web Services (AWS) service disruption reported yesterday is fully resolved. All AWS services have returned to normal operations.

This has been resolved. When attempting to update or submit an activity with a custom date field of nil, an error page was displayed. This issue was just introduced with a fix to a custom date field display issue. The original fix validated the format of the custom field date value so that it could be parsed correctly. This fix, however, did not account for an empty or nil date. When a nil was encountered, checks failed resulting in the reported error. Note: The custom date field validation change will be included in an upcoming release.

We’re seeing far fewer delays, and the application has stabilized. We’ll continue to monitor backend activity to ensure things remain stable. Marking this incident as resolved. If you encounter any issues, please contact your Customer Success Manager or open an incident in ServiceNow.

Earlier today Tangoe discovered a delay in loading the HRIS files and scheduled reports. We have addressed this issue and if you have not yet received your files they may be still in progress or will be scheduled to run shortly. If you encounter any issues or have questions, please contact your Customer Success Manager or open an incident in ServiceNow.

The system degradation has been resolved. Users are able to perform activities without any issues and is now working as expected.

We're happy to announce the reported sporadic 500 Internal Server Errors on the Mobile platform have been successfully resolved and the system is fully operational. As part of our commitment to transparency and continuous improvement, a Root Cause Analysis will be available within the next 10 business days.