All Systems Operational
Highfive Service Operational
AWS Operational
AWS ec2-us-east-1 Operational
AWS s3-us-standard Operational
AWS route53 Operational
AWS rds-us-east-1 Operational
AWS elasticache-us-east-1 Operational
AWS cloudFront Operational
Integrations Operational
Slack Operational
3rd Party Operational
Twilio Phone Numbers ? Operational
Twilio REST API ? Operational
Twilio TwiML ? Operational
Twilio PSTN ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 25, 2017

No incidents reported today.

May 24, 2017

No incidents reported.

May 23, 2017
Completed - The scheduled maintenance has been completed.
May 23, 22:41 PDT
Verifying - Verification is currently underway for the maintenance items.
May 23, 21:35 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 21:00 PDT
Scheduled - We'll be undergoing regular maintenance tonight to bring you new features and bug fixes!
May 23, 11:33 PDT
May 22, 2017

No incidents reported.

May 21, 2017

No incidents reported.

May 20, 2017

No incidents reported.

May 19, 2017

No incidents reported.

May 18, 2017

No incidents reported.

May 17, 2017

No incidents reported.

May 16, 2017

No incidents reported.

May 15, 2017

No incidents reported.

May 14, 2017

No incidents reported.

May 13, 2017

No incidents reported.

May 12, 2017

No incidents reported.

May 11, 2017
Resolved - This incident has been resolved.
May 11, 17:21 PDT
Monitoring - During routine maintenance today, we experienced an issue that resulted in some devices being unable to reconnect to our service, leaving them on a "Cannot connect to Highfive servers" error message on the screen, even after service connectivity was restored.

All Highfive devices reboot themselves automatically at 2 AM local time when an update check is performed, which resolves the issue. However, due to the timing of our maintenance window, some devices in Europe and Asia may still be offline during local business hours today and will need to be manually rebooted. If you have a device in this state, to reboot it, briefly press the button on the back of the device, or power cycle it. Again, any devices not manually rebooted will automatically reboot at 2 AM local time.

The engineering team worked through many scenarios overnight in an attempt to find a remote fix or workaround, but ultimately could not find a method to force the devices to reconnect remotely. In 3 years, this is the first time we've systematically "bricked" (albeit temporarily) production customer devices in the field as a result of scheduled maintenance or software updates. Our team is committed to investing in improvements in the device safeguards that will prevent this scenario in the future, and apologizes for the inconvenience this causes.
May 10, 02:32 PDT