All Systems Operational
Voice / Messaging API's Operational
Inbound Voice Operational
Outbound Voice Operational
Inbound SMS Operational
Outbound SMS Operational
Transcription ? Operational
api.tropo.com (Tokens) ? Operational
Provisioning / Hosting Operational
api.tropo.com (Provisioning) ? Operational
Webhosting Operational
ftp.tropo.com ? Operational
Tropo.com Website ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
WHAT?
* For Tropo.com U.S. text messaging, our team will enable support for concatenation on outbound delivery.
* Installing new TLS certificates on the Tropo.com Production runtimes.
* Revising a rule that is inadvertently blocking attempts to an area in Greece.

WHEN?
* Tuesday 1/24/2017, scheduled from 9:00pm -et through 11:45pm.

IMPACT:
* No impact, concatenation feature may be enabled without a system restart.
* There will be no downtime while applying the new certs; work will be conducted on redundant systems removed from availability.
* The forbidden destinations rule has been validated, and may be applied without a system restart.

WHY?
* This is a highly requested feature, and we're now ready to open it up in Production.
* The current certs will be expiring soon.
* A handful of legitimate call attempts were blocked, and we intend to fix that.
Posted on Jan 20, 18:33 EST
Past Incidents
Jan 22, 2017

No incidents reported today.

Jan 21, 2017

No incidents reported.

Jan 20, 2017

No incidents reported.

Jan 19, 2017

No incidents reported.

Jan 18, 2017

No incidents reported.

Jan 17, 2017
Completed - Work is complete, have a great evening!
Jan 17, 22:06 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 17, 21:00 EST
Scheduled - WHAT?
* Deploying the latest build (15.6.1) of the Tropo Provisioning API, which is leveraged by both the Tropo.com and Tropo.eu environments.
* Installing new certificates (updated expire date) to the Tropo.com Production Gateways.

WHEN?
* Tuesday 1/17/2017, scheduled from 9:00pm -et through 11:45pm.

IMPACT:
* There will be no downtime; work will be conducted on redundant systems removed from availability.

WHY?
* This update contains permanent fixes for multiple patches currently in place, and corrects an isolated issue seen when creating a WebAPI app via REST.
* The current certs will be expiring soon.
Jan 13, 22:05 EST
Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017

No incidents reported.

Jan 13, 2017

No incidents reported.

Jan 12, 2017

No incidents reported.

Jan 11, 2017

No incidents reported.

Jan 10, 2017
Completed - This is complete. All tests are passing, and monitoring is GREEN. Have a great evening!
Jan 10, 23:19 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 10, 21:00 EST
Scheduled - WHAT?
* Our team will deploy the most recent Production accepted build (15.5.1) to the Tropo.com dedicated environments. A comprehensive list of enhancements and corrections may be found at http://changes.tropo.com/

WHEN?
* Tues 1/10/2017, scheduled from 9:00pm -et through 11:45pm.

IMPACT:
* There will be no downtime; work will be conducted on redundant systems removed from availability.

WHY?
* By design, releases will always be deployed to Dedicated Environments several weeks after Shared Production. This version has been live in Shared Production since 12/6/2016.
Jan 6, 19:39 EST
Resolved - This has been resolved.
Jan 10, 17:05 EST
Monitoring - We have since routed away from the connection experiencing the instability, and functionality should be restored. We will leave this open as we continue to monitor the service.
Jan 10, 12:02 EST
Investigating - Monitoring has alerted our team to the possibility of Tropo.com service degradation impacting text message delivery beyond North America. We are working with our vendor to determine the root cause and restore service as soon as possible. We apologize for any inconvenience, and are available it you have any questions (support@tropo.com).
Jan 10, 11:14 EST
Jan 9, 2017
Resolved - This incident has been resolved.
Jan 9, 21:41 EST
Monitoring - Operations removed a deprecated environment ID, but due to a DNS sync issue, some tokens and applications were still expecting that environment ID and failed as a result. This only impacted certain environments that have intentional delayed build accessibility and did not impact the shared environments (which no longer rely on legacy application routing ).

Operations returned the environment ID to immediately fix the issue and are working on an account sync for all Super Production accounts to fix permanently.
Jan 9, 12:50 EST
Resolved - This incident has been resolved.
Jan 9, 21:41 EST
Identified - Our Operations team has been alerted to delays in the network, which may result in app changes propagating slower than expected expected - this should only be a factor for new apps, or new phone numbers that were recently added to existing apps. Though the impact should be limited, we're available if you have any questions (support@tropo.com).
Jan 9, 17:52 EST
Jan 8, 2017

No incidents reported.