conductor Outage History
20 incidents recorded over the last 365 days, 18 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded conductor Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | CI - Ask Conductor UnavailableThe issue affecting Ask Conductor has been resolved and it is working normally again for all accounts. We apologize for any inconvenience this may have caused. | 1h 18m | Resolved |
| Oct 8, 2026 | CM - Login and settings issuesBetween 08:19 and 08:37 UTC, some users of Conductor Website Monitoring were unable to log in. Users who were already logged in could not access several settings sections, including Account, Team members and… | 0 min | Resolved |
| Oct 8, 2026 | testtest | 11 min | Resolved |
| Aug 10, 2026 | CI - Analytics Data DelayThe issue causing a delay in analytics data publishing for the past week has been resolved. Missing data has been restored and analytics should now reflect accurately across all accounts. If you continue to experience… | 18h 37m | Resolved |
| Jul 20, 2026 | Unable to login CM PlatformThe issue has been fully resolved and login functionality is operating normally for all users. We apologize for any inconvenience this may have caused. | 1h 34m | Resolved |
| Jul 15, 2026 | CM - Crawling ImpactedCrawling was briefly impacted by an external outage earlier today but has since been fully restored. We apologize for any inconvenience. | 0 min | Resolved |
| May 27, 2026 | CI - Keyword Groups Filter — Disruption in Market Share, Rank Comparison & Result TypeThis issue has been resolved. The Keyword Groups filter is now functioning as expected across Market Share, Rank Comparison, and Result Type. We apologize for any inconvenience this may have caused and thank you for… | 1h 53m | Resolved |
| May 22, 2026 | CI - Unable to upload keywordsResolution: engineers were doing an infra update, that caused the error. All is back up and running We're not able to upload any keywords on the Platform. Also not in bulk. Immediate error pop up showing > sorry error… | 32 min | Resolved |
| May 21, 2026 | Writing Assistant Insights Not LoadingThe fix has been deployed and the issue has been resolved. Writing Assistant Insights are now operational in all accounts. | 27 min | Resolved |
| May 20, 2026 | Search Console Analytics report missing dataThe root cause has been identified and the issue has been resolved. | 21 min | Resolved |
| May 20, 2026 | CI - Search Intent column missingThe fix has been deployed and confirmed working. | 54 min | Resolved |
| May 19, 2026 | CI - Keywords feature redirecting to HomepageSeems that for non-conductor users, clicking on the Keywords Feature redirects them to the accounts/Home page | 29 min | Resolved |
| May 15, 2026 | AI Search Performance Service OutageAI Search Performance features in Conductor Intelligence were momentarily unavailable | 0 min | Resolved |
| May 7, 2026 | Production Infrastructure MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| May 5, 2026 | Production Infrastructure MaintenanceWe will be undergoing scheduled maintenance during this time. | 30 min | Scheduled |
| May 4, 2026 | Website Monitoring DegradedPerformance across Conductor Website Monitoring is currently degraded. We are actively investigating. | 1h 37m | Resolved |
| Apr 30, 2026 | External Network Disruption Due to Cloudflare BYOIP OutageOn February 20, 2026, we experienced a service disruption caused by an external outage within Cloudflare’s Bring Your Own IP (BYOIP) infrastructure. During the incident, a configuration change in Cloudflare’s network… | -99369 min | Resolved |
| Apr 30, 2026 | Conductor monitoring crawling disruption due to expired TLS certificatesWe experienced a service disruption caused by expired internal TLS certificates, which impacted crawling functionality and led to delays in data processing. The issue was identified and resolved by redeploying updated… | -84543 min | Resolved |
| Apr 30, 2026 | SEMrush API Outage Impacting Explorer ReportsWe experienced an incident affecting the SEMrush API, which resulted in degraded performance and intermittent failures for Explorer reports. This led to disruptions for clients relying on these reports. The issue was… | -133728 min | Resolved |
| Feb 10, 2026 | Research Feature Outage Due to Front-End ChangesWe experienced an outage affecting the Research feature, which resulted in failed or incomplete data retrieval for users. Initial investigation focused on errors from the Google Trends API (HTTP 429 rate limiting)… | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next conductor incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This conductor Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before conductor acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single conductor outage in this window ran 18h 37m, against a mean recovery of 1h 42m. If you depend on conductor in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.