Great question. I was not made ware of any issues on the 13th in regards to mesh connectivity, so I cannot say for certain. With that said, a comprehensive post-incident write up is still being worked on by our engineering team and as they are able, will be sharing this with the community at large. This will get much more comprehensive insight into the issues that occurred.
I’m not aware of any specific Github issues in regards to devices not reconnecting after cloud outages. However, I do know there’s active chatter internally about this issue. So it is certainly a high priority one.
We do recognize this can have an impact on trust to our customers and this is why we aim to learn from these types of incidents to prevent the causes that lead to them from occurring again in the future.
With that said, one consideration in regards to this is that this issue was explicitly isolated to Mesh devices, and did not impact our gen 2 line of devices.
Mesh is new and exciting. It has a lot of new tools and integrations not found previously at Particle. But like anything else, it’s bound to come with its share of bugs. As such, we have been working actively since Mesh’s release to ensure we iterate and knock out issues as quickly as they have come up.
With efforts such as the Gen 3 Community Council, I’d say we’ve done a good job on making sure this feedback loop is a fast and active one.
But with that in mind, we are still working on issues in this feedback loop, as well as developing out tools to help make mesh more reliable and at scale. Until these goals are met, I’d still say that mesh should be considered for more prototyping purposes and would be hesitant to use it for high stake, high volume, or remote deployments just yet. Mesh is in a great stage for prototyping right now, and we will ensure parity with our gen 2 line of devices (and then some, in terms of new features). However, until it reaches that point, I’d be cautious about the use cases in which its deployed for now.