Hi @mstanley, this wasn’t during the scheduled hours, it was well before.
Per status.particle: "Particle will be conducting scheduled maintenance on Sunday May 31st from 18:00-19:00 UTC (11am - 12pm PDT) "
For those playing at home, that is:
Epoch timestamp : 1590948000
Timestamp in milliseconds: 1590948000000
Date and time (GMT) : Sunday, May 31, 2020 18:00:00
Date and time (your time zone): Monday, June 1, 2020 4:00:00 GMT+10:00
Any of our customers who rebooted their device during this period could not connect:
Sunday, May 31, 2020 15:00:00 to 5:15:00 GMT+10:00
- Devices would simply not connect per the original rapid blue and single red flash symptom
- Later towards the end some devices would also go online into limbo and be orphaned and unable to call their functions without a physical reset after the resolution around 5:15 AEST.
I fundamentally don’t agree with your statement: “Based on preliminary investigations, not all devices were experiencing difficulties, thus this was not determined to be a cloud outage.”. That’s like saying the person who just lost a leg in a car accident is perfectly healthy unless they’re dead.
Your testing should have identified that new connections were failing. If that wasn’t apparent, and no one in the support team tried turning on physical devices and connecting them, then that’s an area worth investigating. Presuming you did see all the devices fail to connect and publish functions for over 2 hours, that to me warrants an update on status.particle even if previously registered devices were still working. Status.particle is where I check first as then it saves me the effort of carefully testing with physical devices myself.
You’re welcome to jump onto my customer forum and see their opinions on having their afternoon cooks for dinner time interrupted by Particle’s “it’s not butter” outage. One customer even suggested changing providers. https://www.facebook.com/groups/smartfireowners/permalink/2329137957382892/