AppOptics
Update - The TLS configuration has been reverted.

We will be disabling support for TLS 1.0 on June 25th.

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 25th we will disable TLS 1.0 support for Librato 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 --silent "https://www.howsmyssl.com/a/check" | grep -o -e '"tls_version":"[a-zA-Z0-9\ \.]*"'
There will be a 'tls_version' field to look for.

If you have any questions or need assistance in confirming support for your browsers or clients, contact us at support@librato.com.
Jun 18, 20:07 UTC
Update - The new TLS configuration is now in place.
Jun 18, 19:15 UTC
Update - We are starting a brown out for TLS 1.0 deprecation for approximately 1 hour starting at 12pm Pacific. If you are receiving high rates of HTTP status 500s during this period, the agents forwarding messages may be using TLS 1.0. We will be completing the deprecation process on June 25th.

If you have any questions or need assistance in confirming support for your browsers or clients, contact us at support@librato.com.
Jun 18, 18:57 UTC
Monitoring - We will be disabling support for TLS 1.0 on June 25th.

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 25th 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.

There will be a one hour test on June 18th at 12pm PST.

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 --silent "https://www.howsmyssl.com/a/check" | grep -o -e '"tls_version":"[a-zA-Z0-9\ \.]*"'

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

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
99.88 % 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
Jun 21, 2018

No incidents reported today.

Jun 20, 2018
Resolved - Between 17.44 and 17:55 UTC there was a brief period where a delay in measurement processing may have caused alerts that used composites to trigger unwarranted. The situation quickly resolved itself as the delayed service continued normal operation.
Jun 20, 18:18 UTC
Jun 19, 2018

No incidents reported.

Jun 17, 2018

No incidents reported.

Jun 16, 2018

No incidents reported.

Jun 15, 2018

No incidents reported.

Jun 14, 2018
Resolved - This incident has been resolved.
Jun 14, 06:53 UTC
Investigating - We are currently investigating this issue.
Jun 14, 06:35 UTC
Jun 13, 2018
Resolved - This incident has been resolved.
Jun 13, 17:16 UTC
Identified - There is an ongoing AWS event that is resulting in increased errors.
Jun 13, 16:50 UTC
Jun 12, 2018

No incidents reported.

Jun 11, 2018
Resolved - We have seen an increase in error rates in metrics ingestion and trace ingestion and have rebalanced the affected service.
Jun 11, 10:44 UTC
Jun 10, 2018

No incidents reported.

Jun 9, 2018

No incidents reported.

Jun 8, 2018

No incidents reported.

Jun 7, 2018
Resolved - Between 08:51 and 09:13 UTC there was an increase in the number of errors when submitting metrics and traces.
Jun 7, 13:37 UTC
Resolved - Traces were delayed and Metric Submission had higher than normal errors between 08:51 and 09:13 UTC
Jun 7, 09:43 UTC