All Systems Operational
api.tropo.com (Provisioning)?
api.tropo.com (Tokens)?
Tropo.com Website?
Outbound SMS
Outbound Voice
Inbound Voice
Inbound SMS
ftp.tropo.com?
Webhosting
api.sl.tropo.com
Transcription?
Scheduled Maintenance
Increase memory on Production runtimes Sep 23, 22:00 - Sep 24, 01:00 EDT
* We will be performing a rolling restart of production runtimes to increase memory on servers
Posted on Sep 19, 14:23 EDT
Saturday September 27th Tropo will be routing away from our Orlando facility from 1am EST until 5am EST. During this window production customer traffic will be routed to our secondary facility. Staging will not be routed away so there will be a service impact for the development platform during this window.
Posted on Sep 19, 14:25 EDT
Past Incidents
Sep 23, 2014

No incidents reported today.

Sep 22, 2014

No incidents reported.

Sep 21, 2014

No incidents reported.

Sep 20, 2014

No incidents reported.

Sep 19, 2014

No incidents reported.

Sep 18, 2014

No incidents reported.

Sep 17, 2014
Resolved - We have seen no additional alerts since increasing capacity of the provisioning cluster.
Sep 17, 21:54 EDT
Monitoring - Our monitoring has detected unusually high load on our provisioning api. This high load did impacted some provisioning request but did NOT impact any service to the Token API. Tropo operations has deployed additional resources to better handle this extra load and at this time all alerts have cleared. Our operations team will continue to monitor the cluster to ensure there are no further interruptions.
Sep 17, 19:25 EDT
Sep 16, 2014
Completed - Maintenance completed.
Sep 16, 23:09 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 16, 22:00 EDT
Update - Additional change:

* We will be performing an arp sysctl config change to one of the DNS servers in LAS.
Sep 12, 13:40 EDT
Scheduled - * Staging SBC config changes and restarts to point at new DNS zones
* Staging runtime config changes and restart to point at new DNS zones
* Production SBC config changes and restarts for logging config change

Upcoming maintenance:

September 27th Tropo will be routing away from our Orlando facility from 1am EST until 5am EST. During this window production customer traffic will be routed to our secondary facility. Staging will not be routed away so there will be a service impact for the development platform during this window.
Sep 12, 12:21 EDT
Sep 15, 2014
Resolved - The ISP is back in routing after fixing their difficulties.
Sep 15, 17:30 EDT
Investigating - Our datacenter provider identified an ISP outage starting at 12:36AM EST - as of 2:01 AM EST, the ISP is out of routing and a fallback provider is in place, so traffic is again flowing smoothly; however, as the original ISP outage does not yet appear to be resolved and back in routing, we are not considering this an all clear. We will update again once our provider indicates the ISP difficulties are fixed, as well as any further information they provide to us. Please email support@tropo.com with any additional questions or concerns in the meantime.
Sep 9, 11:06 EDT
Sep 14, 2014

No incidents reported.

Sep 13, 2014

No incidents reported.

Sep 12, 2014

No incidents reported.

Sep 11, 2014
Completed - This has been completed
Sep 11, 23:13 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 11, 22:00 EDT
Scheduled - Tomorrow Tropo operations will be making two changes to the log4j pattern filter which users may notice:

1. Timestamps will switch from second precision to millisecond precision ( Sep 10 19:36:45 will become Sep 10 19:36:45.031 )
2. The applicationID will be added between accountID and SessionID ( PRISM / will become PRISM // )

Below you will find an example of the new format vs the old format

Old Format:
Sep 10 19:43:54 tropo99 PRISM 29890/d84680ef56d146e5849183c635aae825/d84680ef56d146e5849183c635aae825/1/0/#HTTP#: Invoke HttpServletWrapper[HTTPDriver, com.voxeo.tropo.httpspi.HTTPDriver] for HTTP Request(\stropo\scalls)

New Format:
Sep 10 19:43:19.065 tropo99 PRISM 29890/101914/61bb81607565a7f91ed863fa551c237a/61bb81607565a7f91ed863fa551c237a/1/0/[http-0.0.0.0-8080-exec-37]/#HTTP#: Invoke HttpServletWrapper[HTTPDriver, com.voxeo.tropo.httpspi.HTTPDriver] for HTTP Request(\stropo\scalls)

We expect no downtime for the maintenance, and no restarts are necessary during the rollout.
Sep 10, 15:50 EDT
Resolved - All services to the network have been restored for Abilene, TX .

Start time: 10 September 2014 - 11:30AM ET
Stop time: 11 September 2014 - 12:50AM ET
Responsible Party: LEC / Carrier
Fix / Cause of Outage: Wire / Cable
Sep 11, 12:36 EDT
Investigating - We are experiencing a transport issue on our provider's network affecting your inbound origination service only. We are working with our carrier to restore services.

The following markets are impacted:
550 - Abilene, TX - Down Hard

If you determine you are having any issues, please open a ticket with Tropo support and we will assess and determine if it is related to this outage. (support@tropo.com)
Sep 10, 11:59 EDT