BCycle incident

3.0 dock reauthorization/repairing issue

Minor Resolved View vendor source →

BCycle experienced a minor incident on April 29, 2025 affecting IoT Hub and Service Fabric, lasting 6h 19m. The incident has been resolved; the full update timeline is below.

Started
Apr 29, 2025, 03:05 PM UTC
Resolved
Apr 29, 2025, 09:24 PM UTC
Duration
6h 19m
Detected by Pingoru
Apr 29, 2025, 03:05 PM UTC

Affected components

IoT HubService Fabric

Update timeline

  1. investigating Apr 29, 2025, 03:05 PM UTC

    We are currently investigating an issue with 3.0 dock reauthorization/repairing. The steps to recover any docks that did not migrate properly overnight are not working as expected in most cases. Please stay tuned for updates, potentially including a hot fix and updated recovery procedures.

  2. investigating Apr 29, 2025, 05:12 PM UTC

    We are continuing to investigate. At this time, we recommend pausing 3.0 dock reauthorizations while we troubleshoot this issue. Please stay tuned for further updates.

  3. monitoring Apr 29, 2025, 07:26 PM UTC

    A fix has been implemented and we are monitoring the results. Revised instructions for bringing 3.0 docks back to full functionality are available in the BCycle Help Center: https://bcycle.zendesk.com/hc/en-us/articles/40781845636883-3-0-Dock-Recovery-Post-Azure-Migration Please go ahead with field visits to affected 3.0 docks, and submit a ticket with any questions or ongoing issues.

  4. resolved Apr 29, 2025, 09:24 PM UTC

    The issue has been resolved. Please go ahead with field visits to 3.0 docks that need manual intervention to start communicating with our new Azure resources. Instructions are here: https://bcycle.zendesk.com/hc/en-us/articles/40781845636883-3-0-Dock-Recovery-Post-Azure-Migration. Please submit a ticket with any questions or ongoing issues. Thank you for your patience as we worked through this issue.