Meltwater API incident

Investigating increased error rates and timeouts

Minor Resolved View vendor source →

Meltwater API experienced a minor incident on February 14, 2022 affecting API endpoints and Content Stream and 1 more component, lasting 7d 6h. The incident has been resolved; the full update timeline is below.

Started
Feb 14, 2022, 09:04 AM UTC
Resolved
Feb 21, 2022, 03:50 PM UTC
Duration
7d 6h
Detected by Pingoru
Feb 14, 2022, 09:04 AM UTC

Affected components

API endpointsContent StreamMeltwater API Listening AnalyticsMeltwater API Listening ExportsMeltwater API Listening Search ManagementMeltwater API Account Management

Update timeline

  1. investigating Feb 14, 2022, 09:04 AM UTC

    We are currently investigating and monitoring an increased number of timeout errors causing issues for some api requests.

  2. investigating Feb 14, 2022, 09:06 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 14, 2022, 10:06 AM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 14, 2022, 03:21 PM UTC

    We are continuing to investigate this issue. Some API users may experience timeouts or failed exports during this time.

  5. investigating Feb 14, 2022, 06:30 PM UTC

    We are continuing to investigate this issue. Some API users may experience intermittent timeouts or failed exports during this time.

  6. investigating Feb 15, 2022, 05:13 AM UTC

    The API continues to operate normally. Our Engineering team continues towards determining the root cause. We apologize for any inconvenience caused and we will continue to provide updates accordingly.

  7. investigating Feb 15, 2022, 11:12 AM UTC

    The API continues to operate normally. We will continue to monitor the system and keep you updated on the status. We apologize for any inconvenience caused.

  8. investigating Feb 16, 2022, 10:56 AM UTC

    We are continuing to investigate this issue.

  9. resolved Feb 21, 2022, 03:50 PM UTC

    After a period of monitoring, this issue is now resolved. The API continues to function as expected. We apologize for any inconvenience caused and thank you for your patience.