Störungsverlauf von Apify

1. 20. August 2026 um 14:05 UTCinvestigating

   Wir erleben derzeit eine verschlechterte Plattformleistung. Schauspieler können langsamer starten oder aussteigen. Wenn deine Schauspieler Zeit verlieren, kannst du sie wiederbeleben. Wir untersuchen die Ursache dieser Verschlechterung und werden das Update so schnell wie möglich veröffentlichen.

2. 20. August 2026 um 14:49 UTCidentified

   Wir haben das Problem erkannt und arbeiten an der Erholung. Die Leistung des Akteurs ist immer noch beeinträchtigt, bis wir das zugrunde liegende Problem gelöst haben.

3. 20. August 2026 um 15:20 UTCmonitoring

   Wir haben das zugrunde liegende Problem gelöst und die Leistung des Schauspielers hat sich erholt, wir überwachen jetzt die Situation. Wenn dein schauspieler ausläuft, kannst du sie wiederbeleben.

4. 20. August 2026 um 16:14 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. August 2026 um 15:38 UTCidentified

   We are seeing elevated error rates on the SHADER proxy group connected with issues with one of our upstream providers. If you use this proxy group directly (not through the virtual AUTO proxy group), please switch to using another group (such as BUYPROXIES94952) temporarily.

2. 13. August 2026 um 20:08 UTCmonitoring

   A fix has been implemented upstream and the SHADER proxy group has recovered. We continue monitoring the situation for any further disruption.

3. 14. August 2026 um 14:05 UTCresolved

   This incident has been resolved.

1. 7. August 2026 um 21:00 UTCinvestigating

   Der Google SERP-Proxy erlebt erhöhte Reaktionszeiten und erhöhte Fehlerraten. Wir untersuchen das Problem.

2. 8. August 2026 um 10:18 UTCidentified

   The performance problems are caused by issues with our upstream providers. We are in contact with them to find a solution.

3. 8. August 2026 um 10:19 UTCidentified

   We have applied partial fixes to improve the situation and lower the error rate. We are still seeing an elevated error rate and are continuing to work on reaching a full resolution.

4. 8. August 2026 um 13:36 UTCidentified

   The success rate and latency is continuing to improve to almost normal levels, we expect full recovery soon.

5. 8. August 2026 um 18:58 UTCmonitoring

   We have seen a full recovery of the SERP proxy success rates. We will continue monitoring for any future degradation.

6. 8. August 2026 um 18:59 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. August 2026 um 23:56 UTCinvestigating

   Wir erleben eine langsame Bearbeitung von Anfragen für den Google SERP-Proxy. Wir untersuchen das Problem.

2. 4. August 2026 um 00:43 UTCinvestigating

   Der google serp proxy verarbeitet fast keine anfragen oder ist sehr langsam. Wir untersuchen das Problem.

3. 4. August 2026 um 11:05 UTCidentified

   The Google SERP proxy is working, but with slower-than-usual response times. We continue to investigate the issue.

4. 5. August 2026 um 13:30 UTCresolved

   The Google SERP Proxy is stabilized, and we continue to monitor its performance.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. Juli 2026 um 06:53 UTCinvestigating

   Der Actor-Standby-Modus hat eine höhere Fehlerrate und erfordert möglicherweise mehr Wiederholungen als üblich. Wir untersuchen die Ursache. https://docs.apify.com/actors/running/standby

2. 26. Juli 2026 um 07:57 UTCresolved

   Das Problem ist gelöst. Auswirkung war eine erhöhte Fehlerrate bei der Actor Standby API, nicht andere Komponente war betroffen. Es gab keine Ausfallzeiten während der Zeit des Vorfalls.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 14:49 UTCidentified

   Wir untersuchen derzeit Timing-Out-Operationen auf unserer API, die durch langsame Datenbankoperationen aufgrund von Clusteränderungen verursacht werden.

2. 21. Juli 2026 um 16:43 UTCidentified

   Langsame Datenbankvorgänge wirken sich weiterhin auf unsere Systeme aus. Die API-Performance hat sich verbessert, aber Actor-Läufe laufen derzeit aufgrund der reduzierten Mitarbeiterkapazität.

3. 21. Juli 2026 um 17:11 UTCmonitoring

   Wir beobachten jetzt die Situation. Die Arbeitskapazität wurde verbessert und ist nun in der Lage, den Start von Actor zu bewältigen.

4. 21. Juli 2026 um 17:47 UTCinvestigating

   Unsere Datenbank-Cluster-Leistung hat sich weiter verschlechtert, und die gesamte Plattform steht vor einem großen Ausfall. Wir werden Sie weiterhin informieren, wenn die Situation voranschreitet.

5. 21. Juli 2026 um 20:33 UTCidentified

   Wir haben das Problem erkannt und arbeiten auf eine Erholung hin. Das System ist betriebsbereit, aber die Kapazität ist gedeckelt, was dazu führt, dass Actor-Läufe im "bereiten" Zustand gepuffert werden und ein großer Teil von ihnen ausläuft.

6. 21. Juli 2026 um 20:34 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

7. 21. Juli 2026 um 20:52 UTCidentified

   Schauspieler sind jetzt voll funktionsfähig, und das System verarbeitet alle Läufe rechtzeitig.

8. 21. Juli 2026 um 21:28 UTCmonitoring

   Alle Systeme sind funktionsfähig. Wir erwarten, dass sich die Datenbank in 4 Stunden (1 Uhr UTC) vollständig erholt. Wir überwachen die Performance der Plattform. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte.

9. 22. Juli 2026 um 02:38 UTCresolved

   Die Datenbank ist vollständig wiederhergestellt und alle Systeme sind funktionsfähig. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Wir setzen derzeit neue Maßnahmen um, um sicherzustellen, dass sich dies nicht wiederholt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 06:52 UTCinvestigating

   Eine überdurchschnittlich hohe Anzahl von Actor-Läufen wird zwischen Servern migriert, was bei einigen Läufen zu kurzen Unterbrechungen oder Neustarts führen kann. Wir untersuchen derzeit das Problem.

2. 21. Juli 2026 um 06:57 UTCidentified

   Die Ursache für die erhöhten Actor Run Migrationen wurde identifiziert. Wir sind dabei, die Sache zu lösen.

3. 21. Juli 2026 um 07:21 UTCmonitoring

   Ein Fix wurde angewendet und die Migrationen von Actor Runs kehren zum Normalzustand zurück. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte. Wir nehmen dieses Problem ernst und werden Schritte unternehmen, um solche Probleme in Zukunft zu vermeiden.

4. 21. Juli 2026 um 11:53 UTCresolved

   Alle Systeme sind in Betrieb, und wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juli 2026 um 14:04 UTCinvestigating

   Wir sehen eine verschlechterte Leistung von Google SERP-Anfragen. Antworten können länger dauern als gewöhnlich. Wir untersuchen das Problem.

2. 17. Juli 2026 um 20:08 UTCresolved

   Das Problem ist gelöst. Sowohl die Reaktionszeit als auch die Erfolgsrate sind auf ein normales Niveau zurückgekehrt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. Juni 2026 um 15:07 UTCinvestigating

   We're investigating the issue.

2. 4. Juni 2026 um 15:29 UTCidentified

   The issue has been identified, and we are resolving it.

3. 4. Juni 2026 um 15:34 UTCmonitoring

   We have identified and resolved the root cause of the issue. No data loss occurred, as all webhooks are automatically retried. A backlog of pending webhooks remains and is currently being processed. We are monitoring the situation closely.

4. 4. Juni 2026 um 17:07 UTCresolved

   Webhooks are operational, and we apologize for any inconvenience this might have caused.

1. 15. Mai 2026 um 11:48 UTCinvestigating

   We're investigating the issue.

2. 15. Mai 2026 um 11:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 15. Mai 2026 um 12:19 UTCmonitoring

   We have identified and resolved the current problems with our in-memory cache. We're monitoring the situation.

4. 16. Mai 2026 um 05:28 UTCresolved

   This incident has been resolved.

1. 14. Mai 2026 um 08:21 UTCresolved

   We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users. The issue lasted approximately 5 minutes and has been fully resolved. All systems are now operating normally. We apologize for the inconvenience.

1. 6. Mai 2026 um 20:08 UTCidentified

   OAuth sign-in to mcp.apify.com from clients using CIMD with loopback redirects (currently Claude Code) is failing due to a regression. Existing connections and other clients (claude.ai, Cursor, Codex) are unaffected (the later use DCR). We are sorry for the inconvenience and working on a fix.

2. 7. Mai 2026 um 08:27 UTCresolved

   We have implemented a fix for the OAuth flow, and the connections are now working normally.

1. 5. Mai 2026 um 13:50 UTCinvestigating

   We're experiencing outage of key-value store. We're investigation the cause of the issue

2. 5. Mai 2026 um 14:19 UTCmonitoring

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

3. 5. Mai 2026 um 14:34 UTCresolved

   We've resolved an issue where a key-value store API update caused some Actor runs to time out. If your Actor run timed out you can get it back by resurrecting it. There was no data loss. We sincerely apologize for any inconvenience this may have caused.

1. 1. Mai 2026 um 11:23 UTCidentified

   We have identified an issue causing degraded performance in the Console UI and in some API requests. We have implemented a fix, and the performance should stabilize soon.

2. 1. Mai 2026 um 11:29 UTCmonitoring

   Console UI and API performance should be back to standard levels. We will monitor the situation while we investigate the incident's root cause.

3. 1. Mai 2026 um 11:57 UTCresolved

   This incident has been resolved.

1. 29. April 2026 um 12:35 UTCinvestigating

   We're experiencing degraded performance. We're investigation the cause of the issue

2. 29. April 2026 um 13:07 UTCinvestigating

   We're experiencing a full outage of Actors and API. Actors might not be starting. Our engineering team is investigating the root cause of the issue.

3. 29. April 2026 um 13:35 UTCinvestigating

   We've identified the root cause of the issue, and our engineering team is monitoring the metrics. Console, Actors, and API should be stable now.

4. 29. April 2026 um 15:13 UTCresolved

   This incident has been resolved.

1. 8. April 2026 um 10:01 UTCinvestigating

   We are investigating slow API response times due to underlying database issues.

2. 8. April 2026 um 18:25 UTCidentified

   We’ve identified the root cause and have resolved a part of the issue, but the system has not yet fully stabilized. The Actor Runs list endpoint (https://api.apify.com/v2/acts/:actorId/runs) remains the most impacted, along with related views in the Apify Console, where we are still actively working on a fix. Additional endpoints may also experience degraded performance. At this time, we cannot provide an estimate for full resolution.

3. 8. April 2026 um 20:35 UTCinvestigating

   Our systems are currently experiencing a major disruption. We sincerely apologize and are actively investigating the root cause. We will provide updates as more information becomes available.

4. 8. April 2026 um 21:16 UTCidentified

   Service has partially recovered, and we are currently experiencing degraded performance. We are actively investigating the issue and working on a fix. We will continue to provide updates as more information becomes available.

5. 8. April 2026 um 22:24 UTCmonitoring

   The Apify platform is fully recovered. The incident followed a database cluster sharding procedure that resulted in a performance impact on some operations. There was no data loss. The Actor run list API endpoint experienced performance issues between 10:00 and 20:30 UTC, followed by a partial outage of all services from 20:30 to 21:10. Now everything is back to normal, and we are monitoring the situation. We are sorry for any inconvenience caused.

6. 9. April 2026 um 09:15 UTCresolved

   All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.

1. 11. März 2026 um 12:48 UTCmonitoring

   We are informing you about a security incident that occurred on March 6, 2026. Based on our investigation to date, there is no indication that any customer data was affected or compromised. However, we want to share the information we have with you as part of our ongoing commitment to transparency. What happened At approximately 21:52 UTC on March 6, 2026, we detected that the GitHub account of one of our employees had been compromised as part of a broader, known malware campaign. The attacker used this access to inject malicious code into multiple branches across our GitHub repositories via force-pushed commits. Thanks to branch protection rules in place on our repositories, no changes were merged into any default or protected branches. How we responded Upon detection, we immediately suspended the affected account and blocked all associated access across our internal systems. Our engineering team then identified all affected branches and reverted every malicious commit. Full cleanup was completed by approximately 00:32 UTC on March 7, 2026. What we have investigated We have since conducted a thorough review of our GitHub audit logs, AWS CloudTrail logs, Google Workspace logs, and all other important resources. All activity reviewed was consistent with expected patterns — no unauthorized access, no suspicious logins, and no signs of data exfiltration were identified beyond the GitHub repository commits, which have been fully reverted. Despite no signs of malicious access, we also completed the rotation of secrets and the scan of all working machines used by Apify employees. Impact on your data Based on our investigation to date, there is no evidence that any customer data was accessed or affected by this incident. The attack was limited to source code repository branches, all of which were protected and have been restored. We take the security of your data seriously and will continue analyzing the impact of the issue and monitoring for any further indicators of compromise. We will provide an update if our ongoing investigation reveals any new findings. Please don't hesitate to reach out to [email protected] if you have any questions. Sincerely, The Apify security team

2. 12. März 2026 um 09:34 UTCresolved

   This incident has been resolved.

1. 6. März 2026 um 17:27 UTCidentified

   We are currently experiencing degraded performance of the datacenter proxy. The root cause has been identified and we are working on a fix.

2. 6. März 2026 um 19:05 UTCresolved

   Datacenter proxy performance has been fully restored. We apologize for any inconvenience this may have caused.

1. 27. Januar 2026 um 04:10 UTCinvestigating

   We are currently investigating an issue affecting residential proxies. Some requests are failing or timing out. Our team is actively working to identify the root cause and restore normal operation. Further updates will be provided as we learn more.

2. 27. Januar 2026 um 05:45 UTCmonitoring

   The issue has been identified and a fix has been implemented. We are monitoring the system for further issues.

3. 27. Januar 2026 um 09:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 27. Januar 2026 um 09:37 UTCresolved

   This incident has been resolved.

1. 21. Januar 2026 um 15:17 UTCidentified

   Apify Console is temporarily unavailable. We have identified the issue and are rolling out the fix. There is no data loss associated with this outage and Actor runs should not be affected.

2. 21. Januar 2026 um 15:19 UTCresolved

   All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.