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

We are currently experiencing degraded performance in Radarly API. Users may experience a delay in receiving data. Our Engineering team is aware of this issue and currently investigating. We apologize for the inconvenience and appreciate your patience.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The Radarly API is currently available for users. We will continue to monitor the application and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused and we will provide updates accordingly.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Our Engineering team will be performing a system upgrade of our backend search system on Monday, June 2nd, beginning at 07:00 UTC (03:00am ET). The maintenance is expected to last approximately 2 days. During this time, we do not expect any user impact.Thank you for your patience as we continue to enhance our platform's performance and reliability.

The Radarly API is currently available for users. We will continue to monitor the application and provide updates accordingly.Thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix.We apologize for any inconvenience caused and we will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The Radarly API is currently available for users. We will continue to monitor the application and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused and we will provide updates accordingly.

After a period of monitoring, this issue is now resolved. Document streams are functioning as expected.

Engineering has resolved the issue and document streams are currently up to date. We will continue to monitor the application and provide updates accordingly. We apologize for the inconvenience and thank you for your patience.

We are currently experiencing a delay in receiving the latest content. Engineering has resolved the underlying issue, and processing is recovering. We will continue to provide updates as the backlog clears. We apologize for the inconvenience and thank you for your patience.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The Radarly API is currently available for users. We will continue to monitor the application and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused and we will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The issue that caused data delays within the Radarly API has now been fully resolved. Our Engineering team has processed the backlog, and the platform is functioning as expected.

We are currently experiencing degraded performance in the Radarly API. Users may experience a delay in receiving the latest data. Our Engineering team is aware of this issue and is currently investigating.  We apologize for the inconvenience and appreciate your patience.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The Radarly API continues to function as expected. We will continue to monitor and provide updates accordingly.

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

The Radarly API continues to function as expected. We will continue to monitor and provide updates accordingly.

The Radarly API has stabilized and loading issues should not persist. Our engineering teams continue to investigate the root cause. We will continue to monitor the Radarly API and provide updates accordingly. We apologize for the inconvenience and appreciate your patience.

Some users of the Radarly API may experience loading issues as our engineering teams continue to investigate the root cause. We will continue monitoring and will provide updates accordingly. We apologize for the inconvenience and appreciate your patience.

The Radarly API is currently functioning as expected. Our engineering team is still investigating the root cause. We will continue monitoring the platform and will provide updates accordingly. We apologize for the inconvenience and appreciate your patience.

Our Engineering team continues to investigate the issues affecting the Radarly API. We are actively working on a fix and will continue to monitor the situation. We apologize for the inconvenience and appreciate your patience.

We are currently experiencing an issue where the Radarly API is inaccessible for users. Our Engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused, and we will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The issue that caused possible data delays within the Radarly API, has now been fully resolved. Our Engineering team has processed the backlog, and the platform is functioning as expected.

We are currently experiencing degraded performance in the Radarly API. Users may experience slowness and delay in receiving the latest data. Our Engineering team is aware of this issue and is currently investigating. We apologize for the inconvenience and appreciate your patience.

After a period of monitoring, this issue is now resolved. The API continues to function as expected.

The issue affecting the API has been addressed by our Engineering team and it continues to operate as expected. We will continue to monitor the application and provide updates accordingly.

Our Engineering team has identified the issue affecting the Explore searches. They have applied a fix and we will continue to monitor and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue affecting Explore searches, which is impacting API exports and analytics. Our Engineering team is actively investigating and working on a resolution. We apologize for the inconvenience and appreciate your patience. We will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

The issue affecting the Radarly API latency has been addressed by our Engineering team. However, some backfilling of data is continuing. We will continue to monitor the application and provide updates accordingly.

Our Engineering team continues to investigate the cause of the Radarly API latency. We will continue to monitor and provide updates accordingly. We apologize for the inconvenience and appreciate your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix. We apologize for the inconvenience and appreciate your patience.

After a period of monitoring, this issue is now resolved. X/Twitter content continues to flow into the Meltwater API as expected.

X/Twitter content flow into the platform as expected. We will continue to monitor the application and provide updates accordingly. Thank you for your patience.

X/Twitter content is partially flowing into the Meltwater platform at this time. Users may still experience delays through the Meltwater API. We will provide updates accordingly.

We have an ongoing service disruption from X/Twitter, which is causing a delay in receiving tweets. API results may be affected due to this outage. Our engineering team is aware of the issue and are working to resolve it. We will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Meltwater API continues to function as expected.

Our Engineering team has located the issue affecting the Meltwater API and system functionality has been restored. We'll continue to monitor and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue with the Meltwater API where some customers may be hitting rate limits earlier than expected. Our Engineering team is aware of the issue and is actively working on a resolution. We apologize for any inconvenience this may cause and appreciate your patience.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

Our Engineering team has identified the root cause of this issue and the Radarly API continues to function as expected. Thank you for your patience.

The Radarly API is currently available for users. We will continue to monitor the application and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused and we will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Meltwater API continues to function as expected.

The Meltwater API continues to function as expected. We'll continue to monitor and provide updates accordingly.

Our Engineering team has located the issue affecting the Meltwater API and system functionality is currently being restored. We'll continue to monitor and provide updates accordingly. Thank you for your patience.

Our Engineering team is currently investigating issues affecting the Meltwater API. We apologize for any inconvenience caused and we will provide updates accordingly.

After a period of monitoring, this issue is now resolved. The Radarly API continues to function as expected.

Our Engineering team has resolved the issue affecting the Radarly API. We will continue to monitor and provide updates accordingly. Thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our Engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused and we will provide updates accordingly.

Our Engineering teams have resolved the issue, restoring core functionality to the Radarly API. However, as a result of this incident, some Social Performance and Engagement/Scores updates may be unavailable. Some Engagement metrics for posts published before November 15, 2024, may no longer be updated. We apologize for any inconvenience caused and appreciate your understanding.

Our Engineering team has resolved the issue affecting the Radarly API. However, some influencer data may still be unavailable. We will continue to monitor and provide updates accordingly.

The Radarly API continues to function as expected. We will continue to monitor and provide updates accordingly.

Our Engineering team has resolved the issue affecting the Radarly API. Some influencer data backfill continues and we will provide status updates on their progress.

Our Engineering team continues to investigate the issue affecting the Radarly API. We apologize for the inconvenience and thank you for your patience.

We are currently experiencing an issue where the Radarly API is unavailable for users. Our engineering team is currently investigating and working on a fix. We apologize for any inconvenience caused and we will provide updates accordingly.

After a period monitoring this issue is now resolved. The API usage requests data is only available from 16th September 2024 onward. Thank you for your patience.

The latest API usage data is now available in the Meltwater platform. We will continue to monitor and keep you updated. Thank you for your patience.

Our Engineering team is actively working to resolve the issue affecting the retrieval of the latest API Usage data on the Meltwater platform. Users may continue to experience difficulties accessing this data. We are closely monitoring the situation and will provide updates accordingly.

We are currently experiencing issues in getting the latest API Usage data on the Meltwater platform. Our Engineering team is aware of this issue and working on restoring the historical data on the Usage tab.  We apologize for any inconvenience this may cause and appreciate your patience.

After a period of monitoring, this issue is now resolved. The Meltwater API continues to function as expected.

We continue to retrieve the latest editorial and broadcast content. We will monitor the application and share updates as necessary.

The issue with retrieving the latest editorial and broadcast content has been resolved. Content is now flowing into the platform as expected. We will continue to monitor the application and share updates as necessary.

We are currently experiencing delays in retrieving the latest data for editorial and broadcast. This impacts the Earned Streaming, Earned Exports, and Earned Analytics components of the API. Our engineering team is aware of the issue and is actively investigating. We will provide updates as soon as more information becomes available. We apologize for any inconvenience this may cause and appreciate your patience.

After a period of monitoring, this issue is now resolved. Recent data continues to flow into the Radarly platform as expected.

Our Engineering team has completed clearing the backlog and all documents should now be available through the Radarly API. Users should no longer experience time-outs. We will continue to monitor the situation closely and provide updates as needed.

Our Engineering team is actively working to reduce the data delay. We will continue to monitor the situation closely and provide updates accordingly.

Engineering has resolved the issue affecting the Radarly performance. This incident induced a data delay which our team is working to reduce in a timely manner. We will continue to monitor and provide updates accordingly.

Engineering continues to investigate the issue impacting performance in the Radarly platform. We will continue to provide updates accordingly. We apologize for the inconvenience and appreciate your patience.

We are currently experiencing degraded performance in Radarly. Users may experience time-outs on their API requests and delay in receiving the latest data. Engineering team is aware of this issue and is currently investigating. We apologize for the inconvenience and appreciate your patience.

After a period of monitoring, this issue is now resolved. The Meltwater API continues to function as expected.

Our Engineering team has completed processing the backlog. We will continue to monitor and thank you for your patience.

Our engineering team has deployed a fix and live engagement data is being captured. We will continue to work through the backlog and provide updates accordingly.

We are currently experiencing delays in retrieving the latest engagement data for all content. This affects the Earned Streaming, Earned Exports and Earned Analytics components of the API. Engineering is aware of the issue and is currently investigating. We will continue to provide updates accordingly. We apologize for the inconvenience and thank you for your patience.

After a period of monitoring, the issue is now resolved.

Content has now been updated and the platform is working as expected. We will continue to monitor the status of the application. Thank you for your patience.

New content continues to flow into the application. Some users may still experience delayed results. We will continue to monitor and provide updates accordingly. Thank you for your patience.

Content has started to flow into the application, though some users may still experience delayed results. Our Engineering team continues to investigate the root cause and impact. We will continue to monitor and provide updates accordingly. Thank you for your patience.

We are currently experiencing issues in retrieving the latest editorial, social, and broadcast content since 11:55 UTC. Engineering is aware of the issue and is currently investigating.  We apologize for the inconvenience and thank you for your patience.

After a period of monitoring, this issue is now resolved. The Streaming API continues to function as expected. Thank you for your patience.

Engineering has processed the backlog, and processing speed has returned to normal. We will continue to monitor the status of the Streaming API. Thank you for your patience.

Engineering continues to process the Streaming backlog. We will continue to monitor the status of the Meltwater API and provide updates accordingly.

We are currently experiencing delays in processing documents for delivery via the Meltwater Streaming API. Customers can expect delayed delivery as we work to process the backlog. We do not expect to lose any documents.

After a period of monitoring, this issue is now resolved. The Meltwater API continues to function as expected. Thank you for your patience.

Engineering has processed the Exports backlog, and processing speed has returned to normal. We will continue to monitor the status of the Meltwater API. Thank you for your patience.

There is a delay in exports being completed. We're investigating the issue currently.

After a period of monitoring, this issue is now resolved. Thank you for your patience.

Streamed Twitter data is no longer delayed, Exports and Analytics are expected to have current Twitter content. We continue to monitor the status of the application.

Streamed Twitter data is no longer delayed, Exports and Analytics are expected to have current Twitter content. We will monitor the status of the application.

Streamed Twitter data is currently delayed, similarly Exports and Analytics may not have up to date Twitter content. Investigation is ongoing.

After a period of monitoring, this issue is now resolved. Content continues to flow into the application as expected.

Engineering has now processed the content backlog, and all endpoints are working as expected. We will monitor the status of the application.

The engineering team continues to work on the backfills. Delays may be observed for some Streamed Editorial data. In addition, Exports and Analytics may not reflect the latest information due to these delays. Investigations are ongoing.

Backfills are in progress. Delays may be observed for some Streamed Editorial data. In addition, Exports and Analytics may not reflect the latest information due to these delays. Investigations are ongoing.

Streamed Editorial data is currently delayed, similarly Exports and Analytics may not have up to date data. Investigation is ongoing.

Twitter has resolved the issue on their system, and Twitter content is now flowing into the API.

Requests for recent Twitter data for exports, analytics and streaming will be missing due to Twitter outage

This incident has been resolved.

We are currently experiencing elevated 500s across all of the Meltwater API, and delayed processing of streams and exports. We are investigating the causes.

This incident has been resolved.

A fix has been implemented, data flow has been restored and we are monitoring the results. We apologize for any inconvenience caused and will continue to provide updates accordingly.

Streamed Editorial data is currently delayed, similarly Exports and Analytics may not have up to date data. Investigation is ongoing.

After a period of monitoring, this issue is now resolved. All endpoints continue to function as expected. Thank you for your patience.

All endpoints continue working as expected. We will continue to monitor the status of the application. Thank you for your patience.

All endpoints are now working as expected. We will continue to monitor the status of the application. Thank you for your patience.

The Meltwater API Earned Analytics endpoints continue to occasionally return error responses. Other endpoints continue to work as expected. Engineering is actively investigating the issue.

We are continuing to investigate this issue.

The Meltwater API Analytics endpoints are occasionally returning error responses. Other endpoints are currently working as expected. Engineering is actively investigating the issue.

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.

We are continuing to investigate this issue.

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.

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.

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

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

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

This incident has been resolved.

A fix has been implemented, data flow has been restored and we are monitoring the results. We apologize for any inconvenience caused and will continue to provide updates accordingly

Streamed data is currently delayed, similarly Exports and Analytics may not have up to date data. Investigation is ongoing.

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

Engineering has resolved the issue. We will continue to monitor the status. We apologize for any inconvenience caused and thank you for your patience.

There is a delay in exports being completed. We're investigating the issue currently.

This incident has been resolved.

All delayed export jobs have been processed.

Our services are now healthy and missed exports are being backfilled.

We are currently experiencing elevated 500s across all of the Meltwater API, and delayed processing of streams and exports. We are investigating the causes.

This incident has been resolved.

Our services are now healthy and missed exports are being backfilled.

We are currently experiencing elevated 500s across all of the Meltwater API, and delayed processing of streams and exports. We are investigating the causes.

This incident has been resolved.

Our services are now healthy and missed exports are being backfilled.

We are currently experiencing elevated 500s across all of the Meltwater API, and delayed processing of streams and exports. We are investigating the causes.

This incident has been resolved.

We continue to see data delivery delays in the region of 2-2.5 hours, We expect this to continue for the next few hours We apologize for the inconvenience and thank you for your patience.

We are currently experiencing issues retrieving the latest editorial, social, and broadcast content. As a result data delivery is expected to be delayed for streaming delivery and exports with a timeframe covering the last 1-2 hours may see reduced data. We apologize for the inconvenience and thank you for your patience.

This incident has been resolved.

Data delivery is now recovering and we do not expect there to be any missing data.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented, data flow has been restored and we are monitoring the results. We apologize for any inconvenience caused and will continue to provide updates accordingly

We are currently investigating reports of missing or delayed streaming data. We apologize for any inconvenience caused and will continue to provide updates accordingly.

This incident has been resolved. Thank you for your patience.

We continue to monitor the performance of the platform. Limits on date ranges in Analytics API have now been restored to normal. Export and Analytics content is currently available from February 2020 to the current time. Thank you for your patience.

We are continuing to monitor for any further issues.

We continue to progress restoring API features. * The Export jobs backlog has now been cleared. * Export and Analytics content is now available from February 2020 to the current time. * Analytics queries can now have a maximum range of 180 days, this limitation will be increased soon. We apologize for any inconvenience caused and thank you for your patience.

We are continuing to monitor performance of the platform. The backlogs for the majority of customers have now been cleared Please note that we have temporarily limited analytics queries to a maximum time window of 120 days.

We have made progress restoring API features. Streaming is now fully operational. Analytics and Exports are now operational, but please be aware that: * Data is only currently available from January 1st 2021. * We are working through customers' export queues. If you'd like to clear your export queue please use the API or reach out to support. We apologize for any inconvenience caused and thank you for your ongoing patience.

Our Engineering Team continues to investigate the root cause of the issue. Streaming content should start being available again. We apologize for any inconvenience caused and thank you for your patience.

Our Engineering Team continues to investigate the root cause of the issue. We apologize for any inconvenience caused and thank you for your patience.

Our Engineering Team continues to investigate the root cause of the issue. The Analytics API has been disabled to reduce load on backend systems. We apologize for any inconvenience caused and thank you for your patience.

Our Engineering Team continues to investigate the root cause of the issue. We apologize for any inconvenience caused and thank you for your patience.

Our Engineering Team continues to investigate the root cause of the issue. The analytics API is now allowing some calls through to test the system as it comes back up. We apologize for any inconvenience caused and thank you for your patience.

Our Engineering Team continues to investigate the root cause of the issue. The analytics API has been disabled to reduce load on the system. We apologize for any inconvenience caused and thank you for your patience.

Engineering continues to investigate the root cause of this issue. Streaming and Export APIs are impacted by this, Analytics API may also produce some errors. We apologize for any inconvenience caused and thank you for your patience.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

The backlog has been processed and we have returned to normal operations. Once again we apologize for any inconvenience caused.

Data backfill has now been completed following the incident and we are reenabling export jobs processing at this time. We are processing the backlog of export jobs however during this time customers can expect to see delays in data delivery as we work through the backlog of jobs. Additional updated will be provided once the backlog of exports has been cleared. We apologize for any inconvenience caused and will continue to provide updates accordingly.

We continue to monitor the situation with the Export API. As soon as our internal systems are fully recovered, export jobs will be resumed. Streaming API is operational. Thank you for your patience.

Our engineering teams are continuing to make progress towards restoring our services. We are starting to deliver data via Streaming API, Export API will resume when our internal systems are fully recovered. We apologize for any inconvenience caused and will continue to provide updates accordingly.

Our engineering teams are continuing to make progress towards restoring our services. However, we are still unable to delivery new data via the Export and Streaming API. We apologize for any inconvenience caused and will continue to provide updates accordingly.

Due to the ongoing data issues exports spanning today are reporting lower than expected documents counts, in order to mitigate issues and ensure we are delivering all data we are pausing exports processing at this time. You can continue to create exports on the export api and we will process them once the issues have been resolved. We apologize for any inconvenience caused and thank you for your patience.

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

Engineering continues to investigate the root cause of this issue. Users may experience delays or errors with streaming data delivery. We apologize for any inconvenience caused and thank you for your patience.

We are currently seeing delays in data delivery for the streaming API, this is due to an upstream data issue.

This incident has been resolved.

The issue has been resolved. It only affected the Meltwater API v3 export endpoint.

We are currently investigating an issue with creating exports using the Export API.

This incident has been resolved.

A fix has been implemented and we are monitoring and processing the backlog of export jobs.

We are currently experiencing issues processing export jobs for customers in specific regions, we are working to fix the issue and reprocess the backlog, we apologies for the inconvenience.

This incident has been resolved. However, there is a backlog of export jobs waiting to be processed. We will continue to monitor this.

We are continuing to monitor for any further issues.

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

We are currently investigating the issue

This incident has been resolved.

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

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

We are having an intermittent connectivity issue on the Streaming API. We are currently investigating.

We've been monitoring the fix applied yesterday and are happy to confirm the issue is fully resolved.

A fix has been implemented and we are monitoring the results, thanks for your patience.

We've identified some problems for calls to create, update and retrieve Streaming API webhooks. Streaming content for existing webhooks are unaffected. We're working on a fix.

This incident has been resolved.

After a period of monitoring, this issue is now resolved. We apologize for any inconvenience caused and thank you for your patience.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We are currently experiencing some delays in processing export jobs for some customer accounts, a fix has been implemented however effected customers may see an increase delay in export jobs while we process the backlog. Apologies for the inconvenience.

The API briefly had connectivity issues with internal services between 2246 UTC and 2251 UTC causing most requests to return a 500 Internal Server error. This connectivity issue recovered and the API is now operating normally.

This incident has been resolved.

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

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

We are currently investigating this issue.

After a period of monitoring, this issue is now resolved. We apologize for any inconvenience caused and thank you for your patience.

Engineering has located and corrected the issue. We will continue to monitor the situation and provide updates accordingly.

Export processing speed is degraded at the moment. We are investigating the issue.

This incident has been resolved.

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

We've identified the issue and are working on a resolution.

We are continuing to investigate the issue, thank you for your patience.

We're having some issues with our Export API currently. Export jobs cannot be processed - we're working it.

We have been monitoring our systems for the last few hours and can confirm the incident is fully resolved. Thank you for your understanding.

Network issues caused by an upstream provider have stabilised. We are now monitoring our systems, the backlog of data has been processed.

We're currently investigating the issue, please bear with us.