Reincubate
All Systems Operational
Reincubate Cloud Data API master service (asmaster)   ? Operational
Reincubate Cloud Data API control service (asapi)   ? Operational
90 days ago
100.0 % uptime
Today
Reincubate Cloud Data API worker clusters (asworker)   ? Operational
Reincubate Cloud Data API stream service (aschannel)   ? Operational
Reincubate Cloud Data API bucket service (asstore)   ? Operational
Legacy iCloud API emulation layer (api.icloudextractor.com)   ? Operational
Google Cloud Platform Google Cloud Storage   ? Operational
Amazon S3 EU West   ? Operational
Amazon S3 US Standard   ? Operational
Microsoft Azure (https://azure.microsoft.com/en-us/status/)   ? Operational
Apple Cloud Services (https://www.apple.com/support/systemstatus/)   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
All systems check response time (North America)
Fetching
Reincubate Cloud Data API control service (asapi) uptime
Fetching
Reincubate Cloud Data API stream service (aschannel) uptime
Fetching
Legacy iCloud API emulation layer uptime
Fetching
Reincubate Cloud Data API control service (asapi) Apdex
Fetching
Reincubate Cloud Data API bucket service (asstore) Apdex
Fetching
Past Incidents
Feb 19, 2018

No incidents reported today.

Feb 18, 2018

No incidents reported.

Feb 17, 2018

No incidents reported.

Feb 16, 2018

No incidents reported.

Feb 15, 2018

No incidents reported.

Feb 14, 2018
Resolved - We're overdue in updating the status of this incident; we've been in communication with clients directly. In the interests of completeness, we're closing this incident and updating here.

Apple made a series of changes to the iCloud early and mid 2017, primarily in response to a widely reported hacking / extortion event. The changes made were unhelpful as they had the effect of making regular, transparent iCloud backup access more challenging. There were two key changes: account access could lead to accounts being temporarily locked, and authentication tokens for backup access were required to be fresher than 24 hours old. Whilst the former change attracted the most attention, the second was more profound.

Our response was four-fold:

1. Firstly, we worked to ensure that our real-time iCloud data access was unaffected by either of these changes.

2. Secondly, we rapidly released our asmaster product which handled poll frequency for our clients. A number of client scheduler implementations were leading to overly aggressive polls of the iCloud, which contributed negatively to locking. We made asmaster freely available to all clients, simplifying their own integrations.

3. Thirdly, we shipped our asrelay technology to enable clients to work with iOS backup data directly, bypassing the storage limits and change risk of the iCloud. asrelay is available for users with iOS running Windows or macOS, and provides access to another segment of iOS users.

4. Finally, we continued our investment in R&D to enable us to continue helping clients access iCloud backups in a transparent, ethical, secure and scalable manner. We will be announcing more in this space in the coming months.

On this latter point, transparency and security were of utmost importance to us. We have always directly identified our interactions with Apple's servers as coming from Reincubate. We don't operate in the shadows, or in an environment that lacks robust data protection regulation. Consequently rearranging our networking stack to anonymise or somehow mask our traffic was not the right course of action. We met with the team at Apple and continued our work, and were able to structure our iCloud backup access mechanism in such a way as to satisfy the criteria we had: no anonymous access, and no locking of iCloud accounts as a consequence of facilitating legitimate access.

It is still possible for clients to encounter locked iCloud accounts whilst working with iCloud backups. End-user accounts may be locked prior to signing up, or may be accessing their data through other mechanisms which lock. Our API attempts to rate-limit clients that aggressively poll the API beyond our best practises, but behaviour like this can increase the risk of locking. In practise, our rate limiting does a pretty good job of protecting against this. Additionally, lower-priced client services may be more susceptible to attempts at fraudulent account access which can lead to locking for security reasons: this is entirely correct and appropriate.

As we have done consistently, we strongly encourage all clients to promote use of Apple's secure 2FA (two factor authentication) mechanism. This mechanism is a win/win technology for all involved, as it goes further to reinforce legitimacy and consent of access.
Feb 14, 14:13 GMT
Update - We have been communicating with affected API clients directly and implemented a solution. We are continuing to monitor this.
Mar 28, 19:34 BST
Update - We have observed another set of locks today at 1230 UTC. Please do report any instances of this directly to us: ent-support@reincubate.com or via the Slack channel.
Mar 21, 13:17 GMT
Update - We have observed another set of locks affecting a small number of end-users on March 18th, and we are continuing to monitoring this. Please do report any instances of this directly to us: ent-support@reincubate.com or via the Slack channel.
Mar 19, 16:10 GMT
Monitoring - We have not seen any reports of locked accounts since those observed prior to 1700 UTC yesterday. We are continuing to monitor this. Please do report any instances of this directly to us: ent-support@reincubate.com or via the Slack channel.
Mar 14, 19:00 GMT
Update - We have confirmed seeing a number of other locked iCloud accounts today. The two locking periods we have observed at 0300 UTC 4rd March and 1700 UTC today, 13th March. We are still collecting data on this. The prior locking event did not uniformly affect clients or accounts, and we do not believe it related to use of the API.
Mar 13, 18:10 GMT
Investigating - We've received reports today on further account locking and are investigating the issue now to confirm this. We have not seen this reflected in our canary accounts, and it is not clear whether this relates to the activity on the 4th. Please do report any instances of this directly to us: ent-support@reincubate.com or via the Slack channel.
Mar 13, 17:31 GMT
Feb 13, 2018

No incidents reported.

Feb 12, 2018

No incidents reported.

Feb 11, 2018

No incidents reported.

Feb 10, 2018

No incidents reported.

Feb 9, 2018

No incidents reported.

Feb 8, 2018

No incidents reported.

Feb 7, 2018

No incidents reported.

Feb 6, 2018

No incidents reported.

Feb 5, 2018
Completed - The scheduled maintenance has been completed.
Feb 5, 11:30 GMT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 11:15 GMT
Scheduled - Updates to the iCloud API will take place. We do not expect any downtime.
Feb 5, 11:12 GMT