All systems are go

Don't agree with this? Please let us know

  • Log Ingestion API

    Receives inbound logs for processing and storage.

  • Client API

    Provides access to account and log data. This provides capabilities for searching logs data as well as managing account details like organizations, team members, and applications.

  • Alerting

    Executes alerts, maintains their states, and triggers notifications.

  • Web Application

    Main web application used to access, search, and view your logs in real-time.

  • Timber.io Site

    Our main site which hosts our documentation and blog. Issues with this site do not affect your access to the application

Previous Incidents

[Resolved] Issue with log collection and API

This incident lasted 3 hours and 25 minutes.
  • Log Ingestion API
  • Web Application
  • Client API
  • Alerting
Thu, 14 Feb 2019
07:59:06 EST

We are currently investigating an issue involving the API and log collection. app.timber.io is currently inaccessible. We will post more information shortly.

08:28:36 EST

We've addressed the issue for log collection API and the client API. Logs are now being collected and are viewable via app.timber.io. We are continuing to investigate the root cause.

09:10:25 EST

We've identified the root cause and are addressing it now. We expect systems to be back to normal within the next 15 minutes.

09:42:05 EST

Log collection and ingestion has returned to normal. It is processing through a small backlog of collected logs, but should be current within 30 minutes.

11:25:04 EST

Thank you for your patience, the issue has been resolved. We apologize for the inconvenience. We are putting together a plan to avoid this sort of outage in the future.

[Resolved] Delay in Log Processing

This incident lasted 4 hours and 25 minutes.
  • Log Ingestion API
Tue, 12 Feb 2019
12:17:56 EST

We are investigating a delay in log processing. Logs may not be viewable in the dashboard but have not been lost. Will update with more information soon.

13:18:12 EST

We're still experiencing a delay in processing and logs are currently still being ingested but there is a delay of about 10 minutes. We will update as we learn more.

16:43:42 EST

Thank you for your patience, the issue has been resolved. We apologize for the inconvenience, and to confirm, no data was lost during the outage.

[Resolved] Delay In Log Processing

This incident lasted 5 hours and 6 minutes.
  • Log Ingestion API
Sat, 9 Feb 2019
11:22:42 EST

We are investigating a delay in log processing. Logs may not be viewable in the dashboard, but have not been lost. Will update with more information soon.

12:26:44 EST

We've identified the issue and are working on a fix. Only a portion of logs are currently being affected by slow ingestion times.

14:22:18 EST

We've resolved the issue causing delay and are processing the backlog of logs. We expect all logs to be viewable within two hours (most applications will be caught up before then).

16:29:17 EST

Thank you for your patience, the issue has been resolved. We apologize for the inconvenience, and to confirm, no data was lost during the outage.

No further notices from the past 7 days.