- Detected by Pingoru
- Aug 01, 2025, 06:30 AM UTC
- Resolved
- Aug 01, 2025, 08:13 AM UTC
- Duration
- 1h 43m
Affected: DatasetConsole (console.apify.com)Request queueAPI (api.apify.com)Key-value storeActorsSchedulerWebhooks
Timeline · 4 updates
-
investigating Aug 01, 2025, 06:30 AM UTC
One of our database replicas is currently down. Our engineering team is investigating the root cause and working to restore full redundancy. All core services remain operational, but you may experience slightly degraded performance during this time. We’ll provide an update as soon as we have more information.
-
investigating Aug 01, 2025, 06:50 AM UTC
We are continuing to investigate this issue.
-
monitoring Aug 01, 2025, 07:01 AM UTC
We have identified the root cause of the issue affecting one of our database replicas and have applied a fix. The system remained operational throughout the incident. However, there were a few brief disruptions—lasting only a few seconds—during which running actors were restarted. We are sorry for the inconvenience. We will continue to monitor the system to ensure the situation remains stabilized.
-
resolved Aug 01, 2025, 08:13 AM UTC
This incident has been resolved. We are sorry for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 09:00 AM UTC
- Resolved
- Jun 10, 2025, 09:00 AM UTC
- Duration
- —
Affected: Actors
Timeline · 1 update
-
resolved Jun 10, 2025, 09:00 AM UTC
From 23:30 to 7:20 UTC, the platform experienced a slight increase in Actor failure rates. As of 7:20 UTC, the issue has been resolved. We estimate that approximately 70 Actor runs were affected. If your Actor run failed with the message "We've encountered an unexpected system error.", you can resurrect it. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 05:21 AM UTC
- Resolved
- Jun 03, 2025, 05:21 AM UTC
- Duration
- —
Affected: API (api.apify.com)
Timeline · 4 updates
-
investigating Jun 03, 2025, 12:16 AM UTC
We're experiencing degraded performance on our API due to an increase in load on the API. We're investigating the problem.
-
identified Jun 03, 2025, 12:30 AM UTC
Performance has recovered, and we are investigating the root cause.
-
monitoring Jun 03, 2025, 12:42 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 03, 2025, 05:21 AM UTC
All systems are operational now. Between 1:00 a.m. and 2:00 a.m. (CET), we experienced a high load on our platform, which may have led to degraded performance and slowed down our services during that timeframe. The error caused a data duplication resulting in a ~30 of users being overcharged by 10 USD on average, and some of the storage and run statistics were duplicated. The underlying issue has been addressed and we’ll be contacting and refunding the impacted users.
Read the full incident report →
- Detected by Pingoru
- May 24, 2025, 06:23 AM UTC
- Resolved
- May 24, 2025, 07:57 AM UTC
- Duration
- 1h 34m
Affected: Actors
Timeline · 3 updates
-
investigating May 24, 2025, 06:23 AM UTC
The automated QA system incorrectly flagged some Actors published in the Apify Store as "Under maintenance" due to a system error, causing a false positive test result. No issues were detected in the Actors' actual runtime behavior. As a creator of these Actors, you can ignore the alerts. This only affected Actors published in the Apify Store.
-
identified May 24, 2025, 06:50 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved May 24, 2025, 07:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2025, 04:54 AM UTC
- Resolved
- Apr 22, 2025, 01:48 PM UTC
- Duration
- 8h 53m
Affected: Console (console.apify.com)API (api.apify.com)Actors
Timeline · 4 updates
-
investigating Apr 22, 2025, 04:54 AM UTC
We are experiencing degraded performance of multiple platform services and restarts of various system components. We have just stabilized the system and are looking for the root cause of this slowdown.
-
identified Apr 22, 2025, 04:58 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 22, 2025, 05:28 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 22, 2025, 01:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2025, 01:04 PM UTC
- Resolved
- Apr 10, 2025, 02:39 PM UTC
- Duration
- 1h 35m
Affected: Web (apify.com)DatacenterDatasetConsole (console.apify.com)Request queueResidentialAPI (api.apify.com)Key-value storeSERPActorsSchedulerWebhooks
Timeline · 5 updates
-
monitoring Apr 10, 2025, 01:04 PM UTC
A problem with deploying new services caused a system-wide restart and 5-7 minutes long service disruption. The system has recovered after the restart, and the Actors continue operating but the performance is largely degraded.
-
investigating Apr 10, 2025, 01:28 PM UTC
We are currently investigating this issue.
-
monitoring Apr 10, 2025, 01:41 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 10, 2025, 01:46 PM UTC
We identified the root cause and changed the configuration to prevent this from happening again.
-
resolved Apr 10, 2025, 02:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2025, 01:46 AM UTC
- Resolved
- Mar 16, 2025, 10:55 AM UTC
- Duration
- 9h 8m
Affected: SERP
Timeline · 2 updates
-
identified Mar 16, 2025, 01:46 AM UTC
Since 00:10 UTC, the Google SERP proxy has experienced increased response times. This may cause requests using the proxy to time out. As a temporary workaround, we recommend increasing the request timeout. We apologize for any inconvenience and are working toward a swift resolution.
-
resolved Mar 16, 2025, 10:55 AM UTC
We have implemented a fix, and the response time has been recovering since 09:30 UTC. As of 10:30 UTC, the response time has returned to normal. We will continue to monitor the response time. We apologize for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2025, 08:45 PM UTC
- Resolved
- Mar 06, 2025, 08:53 PM UTC
- Duration
- 7m
Affected: SERP
Timeline · 2 updates
-
investigating Mar 06, 2025, 08:45 PM UTC
We are currently investigating this issue.
-
resolved Mar 06, 2025, 08:53 PM UTC
The incident was swiftly resolved on the side of ur SERP proxy providers. All services are functional again
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2025, 12:10 AM UTC
- Resolved
- Mar 06, 2025, 01:52 PM UTC
- Duration
- 13h 42m
Affected: SERP
Timeline · 4 updates
-
investigating Mar 06, 2025, 12:49 AM UTC
We are currently investigating this issue.
-
identified Mar 06, 2025, 01:48 AM UTC
The incident is caused by issues with our proxy providers. We are actively working with them to resolve the issue and will provide updates as soon as we have more information.
-
monitoring Mar 06, 2025, 02:39 AM UTC
A fix has been implemented to channel most of the traffic through the most reliable proxy providers. However, results for the shopping tab might still return content in unexpected languages due to a geolocation issue. We're aware of this and are working on a solution.
-
resolved Mar 06, 2025, 01:52 PM UTC
The incident has been resolved and SERP is fully functional again.
Read the full incident report →
- Detected by Pingoru
- Feb 28, 2025, 09:45 AM UTC
- Resolved
- Feb 28, 2025, 12:01 PM UTC
- Duration
- 2h 15m
Affected: Console (console.apify.com)
Timeline · 4 updates
-
identified Feb 28, 2025, 09:45 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Feb 28, 2025, 09:59 AM UTC
- Users who subscribe or upgrade their account to a higher tier did not receive invoices for the upgrade, and the subscription plan was not updated. - Subscriptions wasn't upgraded correctly. - There is no service disruption for existing subscriptions. - We are working towards a fix, and invoices will be reissued and subscriptions upgraded once the fix is deployed.
-
monitoring Feb 28, 2025, 10:26 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 28, 2025, 12:01 PM UTC
Invoices issuing and subscribing is fully operational again.
Read the full incident report →
Critical February 24, 2025 - Detected by Pingoru
- Feb 24, 2025, 03:24 PM UTC
- Resolved
- Feb 24, 2025, 04:55 PM UTC
- Duration
- 1h 31m
Affected: API (api.apify.com)ActorsScheduler
Timeline · 5 updates
Read the full incident report →
Critical February 22, 2025 - Detected by Pingoru
- Feb 22, 2025, 10:12 PM UTC
- Resolved
- Feb 22, 2025, 11:38 PM UTC
- Duration
- 1h 26m
Affected: Web (apify.com)DatacenterDatasetConsole (console.apify.com)Request queueResidentialAPI (api.apify.com)Key-value storeSERPActorsSchedulerWebhooks
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2025, 03:34 PM UTC
- Resolved
- Jan 27, 2025, 02:56 PM UTC
- Duration
- 10d 23h
Affected: SERP
Timeline · 5 updates
-
identified Jan 16, 2025, 03:34 PM UTC
SERP proxies' performance has degraded because of problems with external data providers. We are working on a fix to restore the success rate to its original level.
-
identified Jan 17, 2025, 07:56 AM UTC
We are continuing to work on a fix for this issue.
-
identified Jan 17, 2025, 09:03 AM UTC
We have identified the problem and are working towards fixing the performance. For now, we will keep experiencing more retries and degraded performance.
-
monitoring Jan 17, 2025, 10:42 AM UTC
A fix has been implemented, and we are back to the usual performance.
-
resolved Jan 27, 2025, 02:56 PM UTC
This incident has been resolved.
Read the full incident report →
Critical January 16, 2025 - Detected by Pingoru
- Jan 16, 2025, 01:47 PM UTC
- Resolved
- Jan 16, 2025, 01:51 PM UTC
- Duration
- 3m
Affected: SERP
Timeline · 2 updates
-
investigating Jan 16, 2025, 01:47 PM UTC
Google SERP proxy may experiencing outage. We're currently investigating an issue.
-
resolved Jan 16, 2025, 01:51 PM UTC
This incident has been resolved.
Read the full incident report →
Critical January 16, 2025 - Detected by Pingoru
- Jan 16, 2025, 01:15 PM UTC
- Resolved
- Jan 16, 2025, 01:17 PM UTC
- Duration
- 2m
Affected: SERP
Timeline · 2 updates
-
investigating Jan 16, 2025, 01:15 PM UTC
Google SERP proxy may experiencing outage. We're currently investigating an issue.
-
resolved Jan 16, 2025, 01:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2024, 08:49 PM UTC
- Resolved
- Dec 08, 2024, 08:53 PM UTC
- Duration
- 4m
Affected: Web (apify.com)
Timeline · 3 updates
-
identified Dec 08, 2024, 08:49 PM UTC
We have identified an issue on the apify.com website. Every page crashes right after it's loaded, and we're working on fixing this as soon as possible.
-
identified Dec 08, 2024, 08:52 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Dec 08, 2024, 08:53 PM UTC
We successfully deployed the fix and apify.com should be operational now.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2024, 06:36 AM UTC
- Resolved
- Dec 03, 2024, 06:36 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 03, 2024, 06:36 AM UTC
Due to an issue in Apify's status page automation, the false positive outage may have been reported here between 4:45 AM and 6:15 AM UTC. All systems were operational at that time.
Read the full incident report →
Critical November 27, 2024 - Detected by Pingoru
- Nov 27, 2024, 07:38 AM UTC
- Resolved
- Nov 27, 2024, 09:42 AM UTC
- Duration
- 2h 3m
Affected: DatacenterDatasetConsole (console.apify.com)Request queueResidentialAPI (api.apify.com)Key-value storeSERPActorsSchedulerWebhooks
Timeline · 3 updates
-
investigating Nov 27, 2024, 07:38 AM UTC
Due to an internal database issue, the whole platform is overloaded, and most requests are failing.
-
monitoring Nov 27, 2024, 08:10 AM UTC
A fix has been implemented and the platform is recovering. We will do an analysis of the impact and determine the appropriate remediation.
-
resolved Nov 27, 2024, 09:42 AM UTC
The incident has been resolved. It was caused by a bug with database updates under high load. Between 7:30 UTC and 8:10 UTC, the Apify platform was overloaded, and most operations were timing out or failing. This includes API calls, running Actors, proxy requests, or accessing the Console. There has been no data loss. Scheduled Actors were executed with a delay once the platform recovered. The dates of last modifications of request queues might not be fully up-to-date.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2024, 12:21 PM UTC
- Resolved
- Nov 21, 2024, 04:36 PM UTC
- Duration
- 4h 15m
Affected: Scheduler
Timeline · 3 updates
-
identified Nov 21, 2024, 12:21 PM UTC
Some scheduled Actors and tasks are not being triggered. We have identified the bug in the code and we're currently deploying a fix.
-
monitoring Nov 21, 2024, 12:47 PM UTC
A fix has been deployed, and schedules are working again. Any schedule triggered between 12:01 UTC and 12:15 UTC was executed with a delay at 12:16 UTC, when the fix was deployed. There was no data loss, and all delayed schedules were eventually executed.
-
resolved Nov 21, 2024, 04:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 07, 2024, 06:18 PM UTC
- Resolved
- Nov 08, 2024, 08:41 AM UTC
- Duration
- 14h 22m
Affected: Actors
Timeline · 3 updates
-
investigating Nov 07, 2024, 06:18 PM UTC
When you use the apify/send-mail Actor to send e-mails, the e-mails are not sent. We are aware of the issue and are working on a fix.
-
monitoring Nov 07, 2024, 07:37 PM UTC
A fix has been implemented to the issue. The apify/send-mail Actor is now working again. The emails will be temporarily sent from a different domain, until we resolve issues with the original sending domain.
-
resolved Nov 08, 2024, 08:41 AM UTC
This incident has been resolved.
Read the full incident report →
Critical November 6, 2024 - Detected by Pingoru
- Nov 06, 2024, 04:19 PM UTC
- Resolved
- Nov 07, 2024, 09:16 AM UTC
- Duration
- 16h 56m
Affected: API (api.apify.com)
Timeline · 5 updates
-
investigating Nov 06, 2024, 04:09 PM UTC
We are experiencing problems with API performance, causing a high number of retries and an elevated error rate. We are investigating the issue.
-
monitoring Nov 06, 2024, 04:19 PM UTC
We have identified the root cause of the issue and deployed changes to remediate it. Apparently, the performance did not get completely to normal as it still slightly increased along with the error rate. Some Actor runs may have failed due to an increased API error rate. We are sorry for any inconvenience caused.
-
monitoring Nov 06, 2024, 05:12 PM UTC
We deployed the final batch of improvements and the API performance returned to normal.
-
monitoring Nov 06, 2024, 05:13 PM UTC
We are continuing to monitor for any further issues.
-
resolved Nov 07, 2024, 09:16 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2024, 01:24 AM UTC
- Resolved
- Nov 06, 2024, 07:59 AM UTC
- Duration
- 6h 34m
Affected: Actors
Timeline · 2 updates
-
monitoring Nov 06, 2024, 01:24 AM UTC
The problem reappeared, and due to insufficient server capacity, some Actor jobs may have been delayed today from around 00:40 to 1:20 AM UTC. This is caused by server availability within our data centers. A large number of runs started running with delay. Short-running Actors may have timed out due to the delay in a container startup. We are working on stabilizing the availability.
-
resolved Nov 06, 2024, 07:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2024, 07:07 AM UTC
- Resolved
- Oct 15, 2024, 11:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 16, 2024, 07:07 AM UTC
Due to an internal misconfiguration, between October 15, 11:00 UTC and October 16, 6:30 UTC, a small number of Actors were unable to start, either when started via API, or when scheduled to run regularly. We have identified the issue and implemented a fix, and the Actors are now starting normally. There was no data loss, and no excessive charges for the failed Actors. We apologize for the inconvenience, and we will contact the affected users soon.
Read the full incident report →
