All Systems Operational
Log Ingestion (Agent/REST API/Code Libraries) ? Operational
90 days ago
99.81 % uptime
Today
Log Ingestion (Heroku) ? Operational
90 days ago
100.0 % uptime
Today
Log Ingestion (Syslog) ? Operational
90 days ago
99.99 % uptime
Today
Web App Operational
Search Operational
Alerting Operational
Livetail Operational
90 days ago
99.99 % uptime
Today
Parsing Operational
Filtering Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Average Live Tail Latency ?
Fetching
Past Incidents
Jan 19, 2020

No incidents reported today.

Jan 18, 2020

No incidents reported.

Jan 17, 2020

No incidents reported.

Jan 16, 2020

No incidents reported.

Jan 15, 2020

No incidents reported.

Jan 14, 2020

No incidents reported.

Jan 13, 2020

No incidents reported.

Jan 12, 2020

No incidents reported.

Jan 11, 2020

No incidents reported.

Jan 10, 2020

No incidents reported.

Jan 9, 2020
Resolved - We have released a hot-fix that resolved the export API issue.
Jan 9, 22:32 UTC
Identified - We are currently experiencing an issue with the export API. Our team has identified the issue and is working on a fix.
Jan 9, 18:28 UTC
Jan 8, 2020

No incidents reported.

Jan 7, 2020

No incidents reported.

Jan 6, 2020
Completed - The scheduled maintenance has been completed.
Jan 6, 20:57 UTC
Update - Our newly developed live tail has been released. Resolving this status.
Jan 6, 20:56 UTC
Scheduled - We at LogDNA wanted to notify you of some issues we've been seeing with our Live Tail service. As of recent, our engineering team has discovered a bug within Live Tail that manifests the following behavior for end-users:

- When the live tail is set to live, users might experience what seems to be a lack of logs as they are streaming into the application, e.g., 150 logs are sent to the system and live tail will only display 120 of those logs. This might cause customers confusion and reason to believe that their logs are missing. In actuality, the data is being ingested and is searchable within the application although Live Tail might make you think otherwise.

To properly resolve this bug, it's necessary to entirely re-architect how our live tail works. Over the past month, our backend team was able to successfully able to do this, not only resolving the bug but even making it more efficient and reliable going forward.

As of right now, our newly developed live tail is currently undergoing extensive testing within our staging environment to make sure we deliver a fully developed and thoroughly tested live tail to our end users. We are also ensuring our infrastructure has the necessary resources to it can handle the newly developed service.

There is not a specific ETA for the fix, but we anticipate it will be available to all customers by early January. We will announce when this fix is in place and please rest assured that your feedback has been clearly heard.
Sep 24, 21:03 UTC
Completed - The search issue has been resolved for now. We'll continue to work on the improvements.
Jan 6, 20:44 UTC
Scheduled - Users may experience missing results when searching in logs ingested between 23:15 UTC on Friday, December 13 and 00:45 UTC on Tuesday, December 17. Affected are non-field searches, e.g., "field:value" will produce the expected results, but "value" may not. We refactored our parsing to provide a better user experience when displaying log lines in the UI. Unfortunately, this resulted in searches only searching a subset of some messages. We reverted the change and will ensure this is addressed when we release the improvements early next year. We apologize for any inconvenience this might have caused.
Dec 18, 00:25 UTC
Resolved - The delay has been resolved and our team will continue to monitor for delays.
Jan 6, 19:31 UTC
Investigating - We are currently experiencing indexing, alerting and graphing delays. Customers may experience a small delay in searching logs, receiving alerts, and in using the graphing functionality.
Jan 6, 18:41 UTC
Jan 5, 2020

No incidents reported.