Librato
All Systems Operational
API   Operational
90 days ago
100.0 % uptime
Today
Web   Operational
Metric Submission   Operational
Service-Side Aggregated Metrics   ? Operational
Historical Summaries   Operational
Alerts   Operational
Metric Integrations Operational
AWS Cloudwatch   ? Operational
Heroku Log Metrics   ? Operational
Papertrail   Operational
Service Integrations Operational
AWS SNS   Operational
BigPanda   Operational
Campfire   Operational
Email   Operational
Flowdock   Operational
HipChat   Operational
OpsGenie   Operational
PagerDuty   Operational
Slack   Operational
VictorOps   Operational
Zapier   Operational
AWS Cloudwatch Regions Operational
us-east-1   Operational
us-east-2   Operational
us-west-1   Operational
us-west-2   Operational
ca-central-1   Operational
eu-central-1   Operational
eu-west-1   Operational
eu-west-2   Operational
ap-northeast-1   Operational
ap-northeast-2   Operational
ap-south-1   Operational
ap-southeast-1   Operational
ap-southeast-2   Operational
sa-east-1   Operational
cn-north-1   Operational
Slack Notifications   Operational
Slack Connections   Operational
Slack Messaging   Operational
Slack Apps/Integrations   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 17, 2018

No incidents reported today.

Jan 16, 2018

No incidents reported.

Jan 15, 2018

No incidents reported.

Jan 14, 2018

No incidents reported.

Jan 13, 2018

No incidents reported.

Jan 12, 2018
Resolved - This issue has been resolved on the log provider, log metrics should be consistently flowing again.
Jan 12, 13:01 UTC
Identified - The issue has been isolated as an issue with the log provider. Please see https://status.heroku.com/incidents/1372 for details.
Jan 11, 21:37 UTC
Investigating - We are currently investigating a delay in heroku log metrics.
Jan 11, 17:32 UTC
Jan 11, 2018
Resolved - This incident has been resolved.
Jan 11, 08:03 UTC
Monitoring - Metrics from Heroku logs will be missing while the Heroku incident continues: https://status.heroku.com/incidents/1372
Jan 11, 06:24 UTC
Jan 10, 2018
Resolved - AWS has reported this incident is resolved.
Jan 10, 14:43 UTC
Identified - We are seeing errors talking to the AWS Cloudwatch service in eu-west-1, so certain Cloudwatch metrics from this region may be delayed.
Jan 10, 13:59 UTC
Jan 9, 2018

No incidents reported.

Jan 8, 2018

No incidents reported.

Jan 7, 2018

No incidents reported.

Jan 6, 2018

No incidents reported.

Jan 5, 2018
Resolved - Additional resources have been added, and performance has returned to normal.
Jan 5, 15:41 UTC
Identified - We have identified an issue causing some problems with Heroku metrics. We are deploying a fix to address this.
Jan 5, 15:17 UTC
Postmortem - Read details
Jan 11, 17:28 UTC
Resolved - This incident has been resolved.
Jan 5, 01:25 UTC
Identified - We are working on the backlog.
Jan 4, 22:33 UTC
Update - Metrics, rolled up metric data and alerts are delayed
Jan 4, 21:47 UTC
Investigating - We are currently investigating this issue.
Jan 4, 21:29 UTC
Jan 3, 2018
Resolved - Alerts are functioning normally.
Jan 3, 19:25 UTC
Monitoring - We have found the issue and the affected service is functioning and clearing its backlog.
Jan 3, 19:19 UTC
Investigating - We are investigating the cause of delayed alerts.
Jan 3, 19:02 UTC