Is Librato Down Right Now? Check if there is a current outage ongoing.

Librato is currently Degraded

Last checked 2025-06-14T13:52:48.326Z from Librato's official status page

Historical record of incidents for Librato

Apr 14, 2025

Report: "Some alerts are delayed"

Last update 2025-04-14T22:39:32.758Z

resolved2025-04-14T22:39:32.743Z

This incident has been resolved.

investigating2025-04-14T21:50:02.159Z

We are currently investigating this issue.

Mar 7, 2025

Report: "Hourly summarizations are delayed."

Last update 2025-03-07T03:12:54.871Z

resolved2025-03-07T03:12:54.851Z

This incident has been resolved.

monitoring2025-03-07T02:06:03.535Z

We are continuing to monitor for any further issues. Next update in 3 hours.

monitoring2025-03-06T19:27:29.000Z

A fix has been implemented and we are monitoring the results. Next update in 6 hours.

Jan 1, 2025

Report: "Increased error rate on Web and API"

Last update 2025-01-01T07:47:01.292Z

resolved2025-01-01T07:47:01.279Z

This incident has been resolved.

monitoring2025-01-01T07:22:27.546Z

A fix has been implemented and we are monitoring the results.

investigating2025-01-01T06:55:28.444Z

We are currently investigating this issue.

Nov 21, 2023

Report: "Major outage from 18:03 to 18:40 UTC"

Last update 2023-11-21T21:24:23.910Z

resolved2023-11-21T21:24:23.891Z

This incident has been resolved.

monitoring2023-11-21T20:24:05.904Z

We are continuing to monitor for any further issues.

monitoring2023-11-21T19:02:23.868Z

We are continuing to monitor for any further issues.

monitoring2023-11-21T18:50:16.290Z

We are currently investigating this issue.

Jul 10, 2023

Report: "Increased error rates and delayed alerts for composite metrics"

Last update 2023-07-10T10:35:22.561Z

resolved2023-07-10T10:35:22.544Z

This incident has been resolved.

monitoring2023-07-10T10:07:02.510Z

Starting at 09:00 UTC On Monday Composite Metrics had increased error rates and delays in processing alerts on Composite Metrics.

May 31, 2023

Report: "Increased error rates from 02:38 - 02:42 UTC"

Last update 2023-05-31T03:19:14.640Z

resolved2023-05-31T02:30:00.000Z

Increased error rates from the API and other services for several minutes.

Mar 22, 2023

Report: "SSL error connecting to api.heroku.com"

Last update 2023-03-22T16:00:15.986Z

resolved2023-03-22T16:00:14.969Z

This incident has been resolved.

monitoring2023-03-22T15:05:45.411Z

A fix has been implemented and we are monitoring the results.

investigating2023-03-22T14:32:16.520Z

We are currently investigating this issue.

Mar 15, 2023

Report: "Alert or Screenshot integrations with slack are not delivered"

Last update 2023-03-15T18:14:14.514Z

resolved2023-03-14T15:00:00.000Z

We are currently investigating this issue.

Dec 17, 2022

Report: "Alert processing errors"

Last update 2022-12-17T02:23:46.185Z

resolved2022-12-17T02:23:46.176Z

From 01:33 to 02:17 UTC Alerts and metric ingestion were disrupted. Metrics sent by some agents may have gaps during that time and Absent Alerts may have fired incorrectly.

investigating2022-12-17T01:45:38.445Z

We are currently investigating this issue.

Oct 21, 2022

Report: "Delayed historical summaries when viewing spans of time 3 days long or longer"

Last update 2022-10-21T05:00:35.096Z

resolved2022-10-21T05:00:35.081Z

This incident has been resolved.

monitoring2022-10-19T17:50:46.826Z

A fix has been implemented and we are monitoring the results.

Oct 18, 2022

Report: "Delayed metrics"

Last update 2022-10-18T21:42:40.744Z

resolved2022-10-18T21:42:40.732Z

This incident has been resolved.

identified2022-10-18T16:49:39.564Z

We continue to work on the metric processing pipeline.

monitoring2022-10-18T14:13:56.135Z

We continue to process the backlog. Most metrics and alerts should be back to normal behavior.

monitoring2022-10-18T12:30:39.781Z

We continue to process the backlog. Most metrics and alerts should be back to normal behavior.

identified2022-10-18T10:40:55.864Z

The issue has been identified and a fix is being implemented.

Oct 17, 2022

Report: "Increased Error rates"

Last update 2022-10-17T13:30:44.993Z

resolved2022-10-17T13:30:44.980Z

This incident has been resolved.

investigating2022-10-17T11:41:41.875Z

We are continuing to investigate this issue.

investigating2022-10-17T11:41:27.710Z

We are currently investigating this issue.

Sep 26, 2022

Report: "Delays in processing metrics"

Last update 2022-09-26T18:10:43.218Z

resolved2022-09-26T18:10:43.201Z

This incident has been resolved.

monitoring2022-09-26T17:33:47.071Z

The backlog has been processed and Alerts and Service Side Aggregated Metrics have returned to normal performance.

identified2022-09-26T16:30:40.297Z

The issue has been identified and a fix is being implemented.

investigating2022-09-26T15:52:16.510Z

We are continuing to investigate this issue.

investigating2022-09-26T15:13:15.349Z

We are currently investigating this issue.

Jul 21, 2022

Report: "Metric ingestion is delayed"

Last update 2022-07-21T23:55:30.334Z

resolved2022-07-21T23:55:30.318Z

This incident has been resolved.

monitoring2022-07-21T23:29:28.394Z

We are working on the backlog of ingested metrics.

identified2022-07-21T22:36:04.246Z

The issue has been identified and a fix is being implemented.

Report: "Service Side Metric Aggregation is delayed"

Last update 2022-07-21T18:08:42.992Z

resolved2022-07-21T16:00:00.000Z

This incident affected: Service-Side Aggregated Metrics.

Jun 11, 2022

Report: "Delayed metrics from AWS Cloudwatch"

Last update 2022-06-11T02:00:24.827Z

resolved2022-06-11T02:00:24.813Z

This incident has been resolved.

monitoring2022-06-11T01:44:11.449Z

A fix has been implemented and we are monitoring the results.

May 11, 2022

Report: "The marketing site is down. Users can log in to Librato using https://metrics.librato.com/sign_in."

Last update 2022-05-11T21:59:11.041Z

resolved2022-05-11T21:59:11.024Z

This incident has been resolved.

investigating2022-05-11T14:27:46.907Z

The marketing site is down. Users can log in to Librato using https://metrics.librato.com/sign_in.

Report: "Increased Errors on https://my.appoptics.com/"

Last update 2022-05-11T01:43:04.484Z

resolved2022-05-11T01:43:04.469Z

This incident has been resolved.

investigating2022-05-11T00:57:47.683Z

We are currently investigating this issue.

Feb 24, 2022

Report: "The home page is not accessible, use https://metrics.librato.com/users/sign_in"

Last update 2022-02-24T17:28:31.214Z

resolved2022-02-24T17:28:31.193Z

This incident has been resolved.

monitoring2022-02-24T17:17:23.654Z

The provider we use for the home page had an incident, https://status.heroku.com/incidents/2402 that appears to now be resolved.

investigating2022-02-24T17:04:02.807Z

We are currently investigating this issue.

Dec 22, 2021

Report: "Alerts, and metrics were delayed from 12:10PM UTC - 2:20PM UTC"

Last update 2021-12-22T18:52:21.330Z

resolved2021-12-22T18:52:21.310Z

This incident has been resolved.

monitoring2021-12-22T14:56:51.062Z

Traces, alerts, and metrics have returned to normal operation.

Dec 15, 2021

Report: "Metrics and Alerts processing is delayed"

Last update 2021-12-15T01:36:32.172Z

resolved2021-12-15T01:36:32.158Z

This incident has been resolved.

monitoring2021-12-15T01:03:09.472Z

Alert processing has returned to normal.

identified2021-12-15T00:30:29.380Z

We are working on restoring full functionality to alerts.

identified2021-12-15T00:08:48.596Z

We are continuing to work on a fix for this issue.

identified2021-12-15T00:06:24.290Z

The issue has been identified and a fix is being implemented.

investigating2021-12-14T23:34:23.983Z

We are continuing to investigate this issue.

investigating2021-12-14T23:10:26.011Z

We are continuing to investigate this issue.

investigating2021-12-14T22:59:29.550Z

We are currently investigating this issue.

Apr 23, 2021

Report: "Delayed alerts for small number of metrics (23:30 UTC on 22Apr2021 to 21:15 UTC 23Apr2021)"

Last update 2021-04-23T22:00:57.504Z

resolved2021-04-23T22:00:57.490Z

This incident has been resolved.

monitoring2021-04-23T21:27:32.229Z

"A small number of alerts were delayed starting at 23:30 UTC on 22Apr2021. As of 21:15 UTC 23Apr2021 all delayed alerts have been delivered and alert processing has returned to normal."

Apr 2, 2021

Report: "Increased Error rates when viewing data in a 3 day window or longer"

Last update 2021-04-02T09:56:38.616Z

resolved2021-04-02T09:56:38.603Z

This incident has been resolved.

identified2021-04-02T09:27:33.477Z

The issue has been identified and a fix is being implemented.

investigating2021-04-02T08:59:26.252Z

We are continuing to investigate this issue.

investigating2021-04-02T08:57:30.080Z

We are currently investigating this issue.

Jun 9, 2020

Report: "CloudWatch Message Ingestion Issue"

Last update 2020-06-09T16:30:09.223Z

resolved2020-06-09T16:30:08.845Z

This incident has been resolved.

monitoring2020-06-09T15:36:02.051Z

We are continuing to monitor for any further issues.

monitoring2020-06-09T13:45:19.841Z

A fix has been implemented and we are monitoring the results.

investigating2020-06-09T12:29:38.907Z

We are continuing to investigate this issue.

investigating2020-06-09T12:27:50.896Z

We are investigating an issue with delayed metric ingestion for our CloudWatch integration. We will update here when more details are available.

May 1, 2020

Report: "A Fraction of Alerts Delayed"

Last update 2020-05-01T00:23:37.848Z

resolved2020-05-01T00:23:37.456Z

This incident has been resolved.

monitoring2020-04-30T23:58:42.972Z

A fix has been implemented and we are monitoring the results.

investigating2020-04-30T23:31:22.884Z

We are continuing to investigate the root cause of the issue. Alerts continue to be delayed.

investigating2020-04-30T22:24:45.429Z

We are continuing to investigate the root cause of the issue. Alerts continue to be delayed.

investigating2020-04-30T21:34:07.157Z

Alerts are delayed. We are investigating the root cause of the issue.

investigating2020-04-30T21:22:37.568Z

Alerts may be delayed. We are investigating the root cause of the issue.

Mar 16, 2020

Report: "Heroku outage affecting Librato"

Last update 2020-03-16T20:05:00.062Z

resolved2020-03-16T20:04:59.306Z

This incident has been resolved.

investigating2020-03-16T20:01:11.000Z

This issue will also cause lower throughput of logs from Heroku

investigating2020-03-16T19:53:27.509Z

An issue with Heroku is causing the site www.librato.com to be inaccessible. We are investigating.

Report: "Heroku outage affecting Librato"

Last update 2020-03-16T16:32:06.929Z

resolved2020-03-16T16:32:06.503Z

This incident has been resolved.

investigating2020-03-16T16:26:39.384Z

An issue with Heroku is causing the site www.librato.com to be inaccessible. We are investigating.

Jan 30, 2020

Report: "Heroku Log Metrics disruption"

Last update 2020-01-30T21:12:26.774Z

resolved2020-01-30T21:12:26.210Z

This incident has been resolved.

monitoring2020-01-30T20:18:28.420Z

We are now receiving Heroku logs at the expected volume. Heroku customers may see a gap in log coverage. The Heroku incident is still open so we'll continue to monitor.

monitoring2020-01-30T19:14:36.691Z

A fix has been implemented and we are monitoring the results.

investigating2020-01-30T19:13:32.141Z

We are currently investigating this issue.

Dec 27, 2019

Report: "database issue"

Last update 2019-12-27T22:30:36.475Z

resolved2019-12-27T22:30:35.993Z

This incident has been resolved.

monitoring2019-12-27T22:02:58.151Z

Normal operations have resumed and we continue to monitor the situation.

investigating2019-12-27T21:30:48.514Z

We are continuing to investigate this issue.

investigating2019-12-27T21:23:23.638Z

There is an identified issue with the database that is affecting performance. We are currently investigating. Please check back for updates.

Sep 27, 2019

Report: "spurious absent alerts and delayed alerts"

Last update 2019-09-27T15:55:33.643Z

resolved2019-09-27T15:55:33.097Z

This incident has been resolved.

investigating2019-09-27T15:55:04.984Z

A database performance issue was identified and we have resolved it. We are working on scaling the database to avoid this problem in the future.

investigating2019-09-27T15:14:53.797Z

We are aware of an issue causing spurious absent alerts and delayed alerts. We are currently investigating this issue.

Sep 20, 2019

Report: "false alerts being generated"

Last update 2019-09-20T01:14:37.746Z

resolved2019-09-20T01:14:37.731Z

This incident has been resolved.

investigating2019-09-20T00:36:59.661Z

We are currently investigating this issue.

Sep 11, 2019

Report: "delayed AWS metrics"

Last update 2019-09-11T22:16:51.049Z

resolved2019-09-11T22:16:51.034Z

This incident has been resolved.

investigating2019-09-11T22:16:26.485Z

We've recovered from the delay in CloudWatch metrics processing. You should see up-to-date metrics in Appoptics/Librato. Please contact support if you need further help.

investigating2019-09-11T21:51:56.441Z

We are continuing to investigate this issue.

investigating2019-09-11T21:50:42.015Z

We are currently investigating this issue.

Sep 6, 2019

Report: "Delays in processing metrics and metric alerts."

Last update 2019-09-06T04:01:32.794Z

resolved2019-09-06T04:01:31.524Z

This incident has been resolved.

monitoring2019-09-06T03:54:58.585Z

Any spurious absent alerts should now be resolved and we continue to monitor the recovery.

investigating2019-09-06T03:52:57.242Z

Any spurious absent alerts should now be resolved and we continue to monitor the recovery.

investigating2019-09-06T03:26:30.874Z

Investigating Alerts service issue that is resulting in spurious absent alerts.

investigating2019-09-06T03:20:02.094Z

We are currently investigating this issue.

Aug 31, 2019

Report: "Issues with metric ingestion from Heroku"

Last update 2019-08-31T14:53:38.233Z

resolved2019-08-31T14:53:33.756Z

This incident has been resolved.

investigating2019-08-31T13:38:28.813Z

We are currently investigating this issue.

Aug 19, 2019

Report: "Alerts processing delayed"

Last update 2019-08-19T19:44:20.519Z

resolved2019-08-19T19:44:20.506Z

This incident has been resolved.

investigating2019-08-19T19:24:08.979Z

We are currently investigating this issue.

May 8, 2019

Report: "Delayed Alerts"

Last update 2019-05-08T23:28:16.484Z

resolved2019-05-08T23:28:14.748Z

resolved, absent alerts did not fire from 22:57 to 23:23 UTC

monitoring2019-05-08T23:25:04.856Z

A fix has been implemented and we are monitoring the results.

investigating2019-05-08T23:18:09.690Z

We are currently investigating this issue.

Apr 1, 2019

Report: "Site issue"

Last update 2019-04-01T21:14:03.272Z

resolved2019-04-01T21:14:02.571Z

This incident has been resolved.

monitoring2019-04-01T20:43:33.755Z

A fix has been implemented and we are monitoring the results.

investigating2019-04-01T20:33:08.671Z

We are aware of an issue and are investigating

Mar 27, 2019

Report: "Cloudwatch metrics delayed for us-west-2"

Last update 2019-03-27T20:06:59.399Z

resolved2019-03-27T20:06:58.276Z

Cloudwatch metrics for us-west-2 are no longer delayed.

identified2019-03-27T18:16:48.727Z

Cloudwatch metrics from us-west-2 are delayed since 17:45 UTC due to an AWS API outage. Metrics will be backfilled when the API is accessible again.

Mar 4, 2019

Report: "Delayed Alerts"

Last update 2019-03-04T01:48:09.910Z

resolved2019-03-04T01:48:09.898Z

Between 00:30 UTC and 01:45 UTC there were processing issues with the alerting pipeline that may have resulted in some alerts being accidentally triggered and/or delayed.

Mar 1, 2019

Report: "Investigating issues with page loading"

Last update 2019-03-01T15:45:25.617Z

resolved2019-03-01T15:45:25.602Z

This incident has been resolved.

investigating2019-03-01T14:41:45.257Z

We are continuing to investigate the issue. Composite alerts may be delayed.

investigating2019-03-01T13:45:30.089Z

We are continuing to investigate the issue. Composite alerts may be delayed.

investigating2019-03-01T13:29:06.625Z

Some customers may be experiencing increased API latency or error rate at this time. We're continuing to work on this issue.

investigating2019-03-01T13:08:08.488Z

We are currently investigating issues with page loading

Feb 27, 2019

Report: "API Latency"

Last update 2019-02-27T22:38:50.210Z

resolved2019-02-27T22:38:50.193Z

This incident has been resolved.

investigating2019-02-27T21:14:47.863Z

We have noticed a higher than normal latency when using the API. We are currently investigating the root cause.

Report: "API Latency"

Last update 2019-02-27T21:02:02.322Z

resolved2019-02-27T21:02:02.304Z

API latency has returned to normal.

monitoring2019-02-27T20:57:40.882Z

API Latency appears to be returning to normal.

investigating2019-02-27T20:45:19.091Z

We have noticed a higher than normal latency when using the API. We are currently investigating the root cause.

Feb 14, 2019

Report: "Delayed collectd metrics"

Last update 2019-02-14T19:22:03.974Z

resolved2019-02-14T19:22:03.580Z

This incident has been resolved.

identified2019-02-14T19:19:04.928Z

We are currently experiencing some delays in processing collectd metrics. Some users may experience delays in seeing metrics that have been posted via collectd.

Dec 20, 2018

Report: "Intermittent Heroku data ingestion"

Last update 2018-12-20T18:57:31.141Z

resolved2018-12-20T18:57:30.505Z

Heroku data ingestion impacted by intermittent log parsing failures between 18:25-18:45 UTC; some measurements may be missing or partially-aggregated during this time. Service has been fully restored as of 18:45 UTC.

Dec 13, 2018

Report: "API calls failing"

Last update 2018-12-13T23:36:55.111Z

resolved2018-12-13T23:36:54.489Z

At 22:38 UTC we experienced a database failover which briefly caused some API calls to fail. Within a few minutes the writer recovered, and all API resumed functioning as normal. Reading some data could have been delayed as replicas caught up. All effects appear to have resolved as of 22:55.

Oct 17, 2018

Report: "Increased error count"

Last update 2018-10-17T19:23:00.128Z

resolved2018-10-17T19:22:59.406Z

This incident has been resolved.

monitoring2018-10-17T19:16:13.505Z

A fix has been implemented and we are monitoring the results.

investigating2018-10-17T18:43:47.262Z

We are currently investigating this issue.

Jul 3, 2018

Report: "Metrics Processing Delays"

Last update 2018-07-03T17:15:21.856Z

resolved2018-07-03T17:15:21.837Z

This incident has been resolved.

identified2018-07-03T17:08:48.909Z

Metrics processing is currently delayed.

Jun 25, 2018

Report: "TLS 1.0 Deprecation"

Last update 2018-06-25T19:10:54.407Z

resolved2018-06-25T19:10:53.854Z

TLSv1 support has been disabled. All public endpoints will require TLSv1.1 or greater. If you have any questions or need assistance in confirming support for your browsers or clients, contact us at support@librato.com.

monitoring2018-06-18T20:08:02.632Z

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.

monitoring2018-06-18T19:16:03.558Z

The new TLS configuration is now in place.

monitoring2018-06-18T18:57:12.356Z

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.

monitoring2018-05-14T15:43:39.826Z

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. 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@librato.com.

Jun 20, 2018

Report: "Composite Alerts - False Positives"

Last update 2018-06-20T18:19:24.797Z

resolved2018-06-20T18:19:24.782Z

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 14, 2018

Report: "Increased API errors"

Last update 2018-06-14T06:53:15.190Z

resolved2018-06-14T06:53:14.693Z

This incident has been resolved.

investigating2018-06-14T06:36:09.067Z

We are currently investigating this issue.