Portia and Scrapinghub Dashboard unavailable
Portia and Scrapinghub Dashboard was unavailable for 30 minutes on 29th November 2016, between 12:40 UTC and 13:10 UTC. The issue was found to be because of an internal server issue. This has been resolved and the services are back to normal.
Nov 29, 12:52-13:43 UTC
api.crawlera.com is currently down
On November 3rd 2016, one of the API end points for Crawlera (api.crawlera.com) was unavailable between 14:29 and 14:35 UTC. The issue has been resolved by restarting the service. We are continuing the investigate the underlying cause to prevent future recurrence. This issue did not affect other API end points for Crawlera.
Nov 3, 14:33-14:38 UTC
api.crawlera.com was briefly down
api.crawlera.com was unavailable on November 2nd 2016 between approximately 10:10 and 10:30 UTC This issue has been resolved.
Nov 2, 11:22 UTC
Crawlera temporary issue
Crawlera API was unreachable on 31st October 2016 between 15:36 and 15:56 UTC.
Some Crawlera users were affected. The issue was solved by our team.
Oct 31, 21:37 UTC
On October 8th, 2016, Portia services were unavailable and experienced problems with job execution. The root cause was within a node of our database servers. This issue has been fully resolved by 16:30 UTC.
Oct 8, 10:21-16:40 UTC
Performance issue with Scrapy Cloud
Between 20:56 UTC and 23:30 UTC on October 7th, 2016, Scrapy Cloud experienced problems with job scheduling, execution and deployment. This may have caused some degraded performance in Dashboard as well. The root cause was within a node of our database servers. This issue has been fully resolved
Oct 7, 20:56 - Oct 8, 02:41 UTC
Crawlera services Impacted.
Crawlera services were impacted from 11.40 UTC to 12.26 UTC. There were some server issues which have been resolved and Crawlera services are up and working.
Oct 7, 12:03-12:31 UTC
Scrapinghub platform unavailable
Scrapinghub platform was unavailable on 4th October 2016 from 09:10 UTC till 10:30 UTC due to a networking issue. All services have been fully restored. We regret the extended downtime and we are taking steps to prevent recurrence for this type of issue.
Oct 4, 09:17-10:35 UTC
Dashboard and deployment issues
On September 26, 2016, Scrapinghub Dashboard services were experiencing issues between 18:20 UTC and 20:40 UTC, due to network connectivity issues. This issue has been fully resolved. The issue was identified and rectified by 20:40 UTC and monitored after that until all operations were confirmed to be working fine by 20:50 UTC.
Sep 26, 20:01-21:14 UTC
Scrapy Cloud platform temporary unavailable
Between 5:45 and 10:15 UTC on September 23rd, 2016, Scrapy Cloud experienced intermittent problems with job scheduling, execution and deployment. This may have caused some timeouts in Dash as well. The root cause was a problem with one of the backend storage servers. This issue has been fully resolved.
Sep 23, 08:06-10:31 UTC
Crawlera overview history temporarily unavailable
Crawlera Recent Requests were unavailable from Scrapinghub Dashboard between 15:50 and 16:00 UTC on Sept 6th 2016 due to a back end failure. This has been fully resolved, this did not affect active jobs and no data was lost.
Sep 6, 15:51-16:47 UTC
Scrapy Cloud Platform temporarily unavailable
On Aug 30th, 2016, at approximately 23:00 UTC, Scrapy Cloud experienced issues with job scheduling, execution and deploying. This may have affected your ability to run your jobs in the Dashboard. We have identified it as a network incident with our providers. First attempt to workaround it helped restore scheduler throughput at approximately 04:08 AM UTC. The final workaround that helped reduce jobs failing and deployments due to timeouts on docker pull, was at 06:22 AM UTC. All services are back to normal now.
Aug 31, 06:51-07:27 UTC
Scrapy Cloud Jobs Issue
Even though we are still waiting for a final confirmation from our network provider, our diagnosis show that issue has been resolved.
Aug 24, 18:34-21:46 UTC
On July 15, 2016, Scrapinghub Dashboard and API services were unavailable between 7:00 UTC and 9:00 UTC, due to network connectivity issues. This issue has been fully resolved. The issue was identified and rectified by 8:00 UTC and monitored after that until all operations were confirmed to be working fine by 9:00 UTC.
Jul 15, 08:02-09:27 UTC
On July 12, 2016, Scrapinghub Dashboard and API services were unavailable between 10:50 UTC and 12:23 UTC. This issue has been fully resolved. The recovery started at around 12:23 UTC and all services were fully operational by 13:30 UTC.
Jul 12, 11:49-15:03 UTC
There was a configuration related bug in Monday's Crawlera release that resulted in 500 "request failed" errors for a number of spiders. We identified the cause and deployed a fix at 10:20 UTC this morning.
Dec 23, 12:44 UTC
Failed Scrapy Cloud jobs
Between 4:00 UTC and 09:30 UTC today, some of our Scrapy Cloud users experienced jobs finishing with a "failed" outcome and a (rather cryptic) outcome "Process terminated with exit code 1, signal None, status=0x0100"
We have identified the root cause (it was related to the size of the deployed projects) and the issue is now resolved.
Dec 3, 17:22 UTC