Muck Rack Outage History
Muck Rack is up right nowPingoru has recorded 35 incidents for Muck Rack: 35 in the last 12 months and 19 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 7 of 720 (1%) |
| May 2026 | 2 | 3 of 744 (0%) |
| June 2026 | 1 | 31 of 720 (4%) |
| July 2026 | 6 | 10 of 744 (1%) |
| August 2026 | 10 | 149 of 744 (20%) |
| September 2026 | 7 | 215 of 720 (30%) |
| October 2026 | 1 | 3 of 566 (1%) |
Incidents, newest first
Minor October 9, 2026 The issue is now resolved. 3h 7m Reporting
Started Oct 09, 2026, 02:53 PM UTC· resolved Oct 09, 2026, 06:01 PM UTC
- investigating Oct 09, 2026, 02:53 PM UTC
We are investigating the issue.
- monitoring Oct 09, 2026, 04:02 PM UTC
We are monitoring the issue.
- resolved Oct 09, 2026, 06:01 PM UTC
The issue is now resolved.
Minor August 28, 2026 The issue is now resolved. We are monitoring for follow-up reports. 53m Reporting
Started Aug 28, 2026, 05:41 PM UTC· resolved Aug 28, 2026, 06:35 PM UTC
- investigating Aug 28, 2026, 05:41 PM UTC
We are investigating the issue.
- resolved Aug 28, 2026, 06:35 PM UTC
The issue is now resolved. We are monitoring for follow-up reports.
Minor August 20, 2026 We implemented a solution and are monitoring for follow-up issues. 59m muckrack.com
Started Aug 20, 2026, 05:40 PM UTC· resolved Aug 20, 2026, 06:39 PM UTC
- identified Aug 20, 2026, 05:40 PM UTC
One of our providers is experiencing an incident that is impacting Muck Rack's loading speed. We are investigating.
- investigating Aug 20, 2026, 06:21 PM UTC
We are investigating the issue on our side.
- resolved Aug 20, 2026, 06:39 PM UTC
We implemented a solution and are monitoring for follow-up issues.
Minor August 13, 2026 We have implemented a solution and the site should be performing as expected. 25m muckrack.com
Started Aug 13, 2026, 02:25 PM UTC· resolved Aug 13, 2026, 02:51 PM UTC
- identified Aug 13, 2026, 02:25 PM UTC
We identified the issue and are working on a solution.
- resolved Aug 13, 2026, 02:51 PM UTC
We have implemented a solution and the site should be performing as expected.
Minor August 6, 2026 We have implemented a fix and are monitoring the issue for further impact. 20m muckrack.com
Started Aug 06, 2026, 03:15 PM UTC· resolved Aug 06, 2026, 03:36 PM UTC
- investigating Aug 06, 2026, 03:15 PM UTC
We are investigating the issue.
- resolved Aug 06, 2026, 03:36 PM UTC
We have implemented a fix and are monitoring the issue for further impact.
Minor February 24, 2026 Our third-party partner has resolved the issue on their end, all is working as expected. 55m Third-Party Services
Started Feb 24, 2026, 08:32 PM UTC· resolved Feb 24, 2026, 09:27 PM UTC
- 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.
- resolved Feb 24, 2026, 09:27 PM UTC
Our third-party partner has resolved the issue on their end, all is working as expected.
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. 11h 31m Content Services
Started Jan 26, 2026, 05:50 PM UTC· resolved Jan 27, 2026, 05:21 AM UTC
- identified Jan 26, 2026, 05:50 PM UTC
Currently users are unable to save Broadcast clips - our team is investigating.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Minor January 22, 2026 The issue is now resolved 17h 5m Third-Party Services
Started Jan 22, 2026, 09:10 PM UTC· resolved Jan 23, 2026, 02:15 PM UTC
- 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/
- resolved Jan 23, 2026, 02:15 PM UTC
The issue is now resolved
Minor January 20, 2026 The issue is now resolved - users should be able to login via SSO as expected. 2h 13m Login / Authentication
Started Jan 20, 2026, 02:23 PM UTC· resolved Jan 20, 2026, 04:36 PM UTC
- investigating Jan 20, 2026, 02:23 PM UTC
We've received reports that users are unable to login with SSO currently - we are investigating.
- identified Jan 20, 2026, 03:30 PM UTC
We identified the issue and are working to implement a solution now.
- resolved Jan 20, 2026, 04:36 PM UTC
The issue is now resolved - users should be able to login via SSO as expected.