AppOptics
Monitoring - We will be disabling support for TLS 1.0 on June 4th.

The vast majority of HTTPS traffic already comes from clients that support TLS 1.2, but a small percentage of users may be affected by this deprecation. On June 4th we will disable TLS 1.0 support for AppOptics which may result in your browser or client no longer being able to interact with the website or the API. To avoid that, please make sure you support TLS 1.2. TLS 1.1 is supported but not recommended.

The following minimum browser versions support TLS 1.2:

Microsoft Internet Explorer 11
Microsoft Edge (all)
Firefox 27
Chrome 30
Safari 7.0 (OS X 10.9)
Mobile Safari 5.1 (iOS 5.1)
Opera 17

Any modern collection agents or libraries that uses SSL are all likely to be supported. You can check the TLS version number on an instance by running the following curl statement from the instance in question.

curl https://www.howsmyssl.com/a/check

There will be a 'tls_version' field to look for.

Or if you have jq:

curl https://www.howsmyssl.com/a/check | jq '.tls_version'

If you have any questions or need assistance in confirming support for your browsers or clients, contact us at support@appoptics.com.
May 14, 15:44 UTC
API   Operational
90 days ago
100.0 % uptime
Today
Web   Operational
Metric Submission   Operational
Traces   Operational
90 days ago
100.0 % uptime
Today
Alerts   Operational
Service-Side Aggregated Metrics   Operational
Metric Integrations Operational
90 days ago
100.0 % uptime
Today
Papertrail Search Alerts   Operational
Papertrail Log Search   Operational
AWS Cloudwatch   ? Operational
90 days ago
100.0 % uptime
Today
Service Integrations Operational
PagerDuty Notification Delivery   Operational
PagerDuty REST API   Operational
PagerDuty Webhooks   Operational
mailgun API   Operational
mailgun Outbound Delivery   Operational
Slack Apps/Integrations   Operational
Flowdock Network   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 25, 2018

No incidents reported today.

May 24, 2018

No incidents reported.

May 23, 2018
Resolved - Data processing has all caught up.
May 23, 16:09 UTC
Identified - The issue has been identified and corrective action taken. The system should be caught up shortly.
May 23, 14:51 UTC
Investigating - Our data processing infrastructure for APM traces is running behind which may be causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.
May 23, 14:46 UTC
May 22, 2018

No incidents reported.

May 21, 2018

No incidents reported.

May 20, 2018

No incidents reported.

May 19, 2018

No incidents reported.

May 18, 2018

No incidents reported.

May 17, 2018

No incidents reported.

May 16, 2018

No incidents reported.

May 15, 2018
Resolved - This incident has been resolved.
May 15, 13:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 15, 12:58 UTC
Investigating - We are currently investigating this issue.
May 15, 12:54 UTC
May 13, 2018

No incidents reported.

May 12, 2018

No incidents reported.

May 11, 2018

No incidents reported.