All Systems Operational
api.tropo.com (Provisioning) ? Operational
api.tropo.com (Tokens) ? Operational
Tropo.com Website ? Operational
Outbound SMS Operational
Outbound Voice Operational
Inbound Voice Operational
Inbound SMS Operational
ftp.tropo.com ? Operational
Webhosting Operational
api.sl.tropo.com Operational
Transcription ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Scheduled Maintenance
DNS zone change Oct 31, 23:00 - Nov 1, 02:00 EDT
Two weeks ago Tropo.com Operations moved our domain's authoritative name servers to another vendor. This weekend we will be removing reference of the domain from our previous vendor's name servers. We expect no downtime or service interruption from this change. We of course encourage our customers to contact support ( support@tropo.com ) if there are any questions or concerns we can assist with.
Posted on Oct 30, 10:22 EDT
Past Incidents
Oct 30, 2014

No incidents reported today.

Oct 29, 2014
Resolved - This incident has been resolved.
Oct 29, 14:30 EDT
Identified - The last release's change log did not reflect an implemented update to the version of JRuby in use for Tropo Scripting - We are now using JRuby 1.7 which is compliant with Ruby 1.9. One change we have noticed already is that the String class no longer includes enumerable which means certain methods available to users on String prior to Ruby 1.9 will no longer work. The full method list for each class can be found below:

http://www.rubydoc.info/stdlib/core/1.8.7/String
http://www.rubydoc.info/stdlib/core/1.9.2/String

Additional info on that change can be found here https://www.ruby-forum.com/topic/104070.

We have only seen a single instance of that particular issue in our logging thus far, but it is worth noting regardless. We recommend all Ruby users double check their scripts and make sure they're functional, while we also continue to review logs to proactively ensure there are no additional errors. If you tested your application in the development environment prior to this notice, and saw no issues, you're good to go; the JRuby update was present in the development environment for the entire extended soak period, so if you were going to have trouble, you would've seen it during any previous testing. This only applies to applications that were not previously validated against the current build. We of course encourage our customers to contact support ( support@tropo.com ) if there are any questions or concerns we can assist with.

Regards,

John Dyer
Director of Platform Operations
Tropo, Inc
Oct 29, 11:27 EDT
Completed - This change was completed at approximately 5am UTC but unfortunately the status page was not updated. We apologize for any confusion by the task being left as "in progress" over night. If there are any questions please let us know ( support@tropo.com )
Oct 29, 10:41 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 28, 20:00 EDT
Scheduled - During our normal maintenance window on 10/28, we will be updating the production environment to the build currently in the development environment. The build has been soaking in development for over three weeks without incident, though further testing of any production application code ahead of time is worthwhile and recommended.

Please review http://changes.tropo.com/ for a list of the relatively minor changes, including a voicemail detection improvement.
Oct 20, 16:15 EDT
Oct 27, 2014

No incidents reported.

Oct 26, 2014

No incidents reported.

Oct 25, 2014

No incidents reported.

Oct 24, 2014
Resolved - This incident has been resolved.
Oct 24, 10:58 EDT
Monitoring - Our provider has identified an issue with Canadian SMS which briefly impacted inbound and outbound traffic today, and may have had some sporadic impacts last week. Although the issue is now resolved and testing is successful, Tropo support will continue to monitor Canadian SMS. If you experience any trouble with SMS, please contact Tropo Support with your examples and we'll assess if your issue is related. Thank you
Oct 20, 16:46 EDT
Resolved - Chicago maintenance is now complete. If you have any questions or concerns about this notification, please contact Tropo support (support@tropo.com). Thank you
Oct 24, 10:43 EDT
Identified - Our provider has scheduled maintenance for Chicago, IL during the following window.

Date: Thursday, October 23th, 2014
Start Time: 9:00 pm PT/ 10:00 pm MT/ 11:00 pm CT/ 12:00 pm ET
Stop Time: 12:00 pm PT/ 1:00 am MT/ 2:00 am CT/ 3:00 am ET

Customer Impact: During this window customers may experience momentary call failures. If you have any questions or concerns about this notification, please contact Tropo support (support@tropo.com). Thank you
Oct 20, 16:50 EDT
Oct 23, 2014

No incidents reported.

Oct 22, 2014

No incidents reported.

Oct 21, 2014

No incidents reported.

Oct 19, 2014

No incidents reported.

Oct 18, 2014

No incidents reported.

Oct 17, 2014

No incidents reported.

Oct 16, 2014
Completed - This change has been completed and all systems green.
Oct 16, 22:15 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 16, 22:00 EDT
Scheduled - Tomorrow evening Tropo Operations will make a security cipher change to an internal load balancer to mitigate exposure to CVE-2014-3566, aka Poodle. The public API ( api.tropo.com ) does not support SSLv3 so it is not susceptible to this exploit however out internal audit has uncovered a single private load balancer which is possibly susceptible. Since our internal clients use TLS to connect to this API we feel the best course of action is to simply remove SSLv3 and mitigate any potential exposure. Tropo Operations expects no service impact during this change. We of course encourage our customers to contact support ( support@tropo.com ) if there are any questions or concerns we can assist with.
Oct 15, 20:49 EDT