All Systems Operational

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 support@apify.com and we'll get back to you as soon as we can.

Web (apify.com) ? Operational
Console (console.apify.com) ? Operational
API (api.apify.com) ? Operational
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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Dec 3, 2024
False positive alert at status page
Resolved - 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.
Dec 3, 07:36 CET
Dec 2, 2024

No incidents reported.

Dec 1, 2024

No incidents reported.

Nov 30, 2024

No incidents reported.

Nov 29, 2024

No incidents reported.

Nov 28, 2024

No incidents reported.

Nov 27, 2024
System outage
Resolved - 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.
Nov 27, 10:42 CET
Monitoring - A fix has been implemented and the platform is recovering. We will do an analysis of the impact and determine the appropriate remediation.
Nov 27, 09:10 CET
Investigating - Due to an internal database issue, the whole platform is overloaded, and most requests are failing.
Nov 27, 08:38 CET
Nov 26, 2024

No incidents reported.

Nov 25, 2024

No incidents reported.

Nov 24, 2024

No incidents reported.

Nov 23, 2024

No incidents reported.

Nov 22, 2024

No incidents reported.

Nov 21, 2024
Partial outage of schedules
Resolved - This incident has been resolved.
Nov 21, 17:36 CET
Monitoring - 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.
Nov 21, 13:47 CET
Identified - Some scheduled Actors and tasks are not being triggered. We have identified the bug in the code and we're currently deploying a fix.
Nov 21, 13:21 CET
Nov 20, 2024

No incidents reported.

Nov 19, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage