Partial System Outage

About This Site

This is the Apify status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here. You can also subscribe to get notified via email or sms.

If you are experiencing any issues with Apify, don't hesitate to get in touch with us at and we'll get back to you as soon as we can.

Web ( ? Operational
Console ( ? Operational
API ( ? Major Outage
Actors ? Operational
Storage Operational
Dataset ? Operational
Request queue ? Operational
Key-value store ? Operational
Proxy Operational
Datacenter ? Operational
Residential ? Operational
SERP ? Operational
Scheduler ? Operational
Webhooks ? Operational
External services Operational
AWS EC2 ? Operational
AWS S3 ? Operational
AWS SQS ? Operational
AWS elb-us-east-1 Operational
AWS elasticache-us-east-1 Operational
AWS dynamodb-us-east-1 Operational
Braintree Payment Gateway API Operational
Braintree Canadian Processing Operational
Braintree APAC Processing Operational
Braintree European Processing Operational
Braintree United States Processing Operational
npm, Inc. Registry Reads Operational
Braintree 3D Secure Operational
AWS ecr-us-east-1 Operational
AWS eks-us-east-1 Operational
Degraded Performance
Partial Outage
Major Outage
Past Incidents
Jul 15, 2024

No incidents reported today.

Jul 14, 2024

No incidents reported.

Jul 13, 2024

No incidents reported.

Jul 12, 2024
Resolved - This incident has been resolved.
Jul 12, 16:44 CEST
Monitoring - One of our integration partners has been experiencing degraded stability of their integrations for the past few hours:
- Gmail
- Gdrive
- Asana
- Trello
- GitHub

Some invocations have not been fired. Everything is recovered at this point. We work with our partner to ensure that this won't happen again, as this is a critical functionality.

Jul 12, 13:35 CEST
Jul 11, 2024

No incidents reported.

Jul 10, 2024

No incidents reported.

Jul 9, 2024

No incidents reported.

Jul 8, 2024

No incidents reported.

Jul 7, 2024

No incidents reported.

Jul 6, 2024

No incidents reported.

Jul 5, 2024
Resolved - The original root cause was discovered. We identified the root cause as a database cluster issue and implemented a successful recovery yesterday. Our systems are now stable and functioning optimally.


As a result of this issue, some users of pay-per-result Actors were charged more than they should have paid if the run was running during one of the following intervals:
- 2024/07/03 15-17 UTC
- 2024/07/04 04-06 UTC

We are currently investigating the full scope of this issue and will issue refunds to affected users within the next week. Based on our initial assessment, the number of impacted users is limited.

Future Prevention:

Over the coming week, our team will prioritize implementing more measures to prevent similar incidents in the future. We consider this issue a high-severity matter and are committed to ensuring the continued reliability of our services.

We sincerely apologize for any inconvenience this caused.

Jul 5, 11:47 CEST
Update - A long-term fix was deployed to the production environment to mitigate another performance drop. We will keep monitoring the system.
Jul 4, 15:25 CEST
Monitoring - We have identified the cause of the issue and implemented a workaround. A proper fix will be deployed later today.

There was no data loss, however the performance of Actors and API operations was degraded between 4 AM and 6 AM UTC 2024-07-04, and some scheduled Actors and tasks might have been triggered twice.

Jul 4, 10:09 CEST
Identified - The incident reappeared. Although the previous fix lessened the impact, we're still facing degraded performance of Actor runs and builds.
Jul 4, 06:30 CEST
Monitoring - A fix has been implemented and we will keep monitoring the results.
Jul 3, 20:33 CEST
Update - The system is operating normally at this point. We are still investigating the issue and will be implementing new measures.
Jul 3, 18:26 CEST
Investigating - The performance of Actor runs and builds is degraded. We are experiencing a slowdown in our internal systems and are investigating the issue.
Jul 3, 17:46 CEST
Jul 4, 2024
Jul 3, 2024
Resolved - We have identified the likely causes of the issue and taken steps to mitigate them.
Jul 3, 14:10 CEST
Monitoring - Runs and builds of Actors were on hold for roughly 7 minutes due to an issue with our internal systems. The incident is now resolved and we are investigating the root causes to prevent it from occurring again. There was no data loss, some runs may have timed out and can be resurrected.
Jul 3, 13:15 CEST
Jul 2, 2024

No incidents reported.

Jul 1, 2024

No incidents reported.