Muck Rack Outage History

Muck Rack is up right now

Muck Rack had 5 outages in the last 2 years totaling 62h 36m of downtime — averaging 0.2 incidents per month.

There were 5 Muck Rack outages since January 20, 2026 totaling 62h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.muckrack.com

Minor June 15, 2026

The issue is now resolved.

Detected by Pingoru
Jun 15, 2026, 10:06 AM UTC
Resolved
Jun 16, 2026, 04:58 PM UTC
Duration
1d 6h
Affected: muckrack.com
Timeline · 8 updates
  1. investigating Jun 15, 2026, 10:06 AM UTC

    We are investigating reports of overall site slowness. Some users may experience delayed page loads or reduced responsiveness. We will provide updates as we learn more.

  2. identified Jun 15, 2026, 10:59 AM UTC

    We identified the issue and have implemented some solutions to reduce load times. We are seeing improvement across the site, but are still investigating.

  3. monitoring Jun 15, 2026, 11:46 AM UTC

    We implemented solutions to improve performance of the platform. We are monitoring the platform for further issues and will update if we notice anything change.

  4. monitoring Jun 15, 2026, 04:51 PM UTC

    Overall platform performance remains stable – the team is now investigating issues with content pulling into the platform due to these changes.

  5. monitoring Jun 15, 2026, 06:28 PM UTC

    We are still monitoring the platform stability and continuing to reallocate resources to backfill content.

  6. monitoring Jun 15, 2026, 07:57 PM UTC

    The platform continues to remain stable, with the primary issue now being new content pulling into the platform. The team is investigating ways to speed this process up. We will update as we learn more.

  7. monitoring Jun 16, 2026, 01:13 PM UTC

    We are currently seeing delays in article content being available in the platform. The team is investigating how to accelerate this process.

  8. resolved Jun 16, 2026, 04:58 PM UTC

    The issue is now resolved.

Read the full incident report →

Minor February 24, 2026

Our third-party partner has resolved the issue on their end, all is working as expected.

Detected by Pingoru
Feb 24, 2026, 08:32 PM UTC
Resolved
Feb 24, 2026, 09:27 PM UTC
Duration
55m
Affected: Third-Party Services
Timeline · 2 updates
  1. monitoring Feb 24, 2026, 08:32 PM UTC

    We are experiencing an issue from one of our external providers. This is causing users attempting to connect their emails to be impacted. Our team is actively monitoring the situation in the case we can help on our side. We will update as we have more information.

  2. resolved Feb 24, 2026, 09:27 PM UTC

    Our third-party partner has resolved the issue on their end, all is working as expected.

Read the full incident report →

Minor January 26, 2026

The primary issue is now resolved - users are able to save new clips, add to Coverage Reports, and the majority of content has been backfilled. The Saved Broadcast Clips page is now working as expected, though we are seeing some remnants on the Coverage Reports clips page. We expect to have this resolved as soon as we are able.

Detected by Pingoru
Jan 26, 2026, 05:50 PM UTC
Resolved
Jan 27, 2026, 05:21 AM UTC
Duration
11h 31m
Affected: Content Services
Timeline · 7 updates
  1. identified Jan 26, 2026, 05:50 PM UTC

    Currently users are unable to save Broadcast clips - our team is investigating.

  2. identified Jan 26, 2026, 06:53 PM UTC

    The team has identified the issue and is working toward the best path for resolution - we will update as we learn more.

  3. identified Jan 26, 2026, 07:35 PM UTC

    We’re currently implementing a fix, but full resolution may take a few more hours while the solution is being tested and implemented.

  4. identified Jan 26, 2026, 08:31 PM UTC

    We currently expect users to be able to save and update new clips within the next hour (looking at around 4:30pm ET). Old clips (clips saved prior to this incident) will take longer to be accessible - we will provide a more concrete ETA on this as soon as we are able.

  5. identified Jan 26, 2026, 09:40 PM UTC

    We're finalizing a couple of changes before users are able to save new clips - we will update once this is available.

  6. identified Jan 26, 2026, 10:20 PM UTC

    Users can now create new clips + update new clips, as well as add them to Coverage Reports successfully. We're still working on an ETA for restoring access to clips prior to this incident, with a more concrete timeline to be shared once we have one available.

  7. resolved Jan 27, 2026, 05:21 AM UTC

    The primary issue is now resolved - users are able to save new clips, add to Coverage Reports, and the majority of content has been backfilled. The Saved Broadcast Clips page is now working as expected, though we are seeing some remnants on the Coverage Reports clips page. We expect to have this resolved as soon as we are able.

Read the full incident report →

Minor January 22, 2026

The issue is now resolved

Detected by Pingoru
Jan 22, 2026, 09:10 PM UTC
Resolved
Jan 23, 2026, 02:15 PM UTC
Duration
17h 5m
Affected: Third-Party Services
Timeline · 2 updates
  1. monitoring Jan 22, 2026, 09:10 PM UTC

    Microsoft Outlook is having an incident that may impact email sending within Muck Rack, including Pitching, Newsletters, and Export emails. We're monitoring: https://status.cloud.microsoft/

  2. resolved Jan 23, 2026, 02:15 PM UTC

    The issue is now resolved

Read the full incident report →

Minor January 20, 2026

The issue is now resolved - users should be able to login via SSO as expected.

Detected by Pingoru
Jan 20, 2026, 02:23 PM UTC
Resolved
Jan 20, 2026, 04:36 PM UTC
Duration
2h 13m
Affected: Login / Authentication
Timeline · 3 updates
  1. investigating Jan 20, 2026, 02:23 PM UTC

    We've received reports that users are unable to login with SSO currently - we are investigating.

  2. identified Jan 20, 2026, 03:30 PM UTC

    We identified the issue and are working to implement a solution now.

  3. resolved Jan 20, 2026, 04:36 PM UTC

    The issue is now resolved - users should be able to login via SSO as expected.

Read the full incident report →