Blues Outage History

Blues is up right now

Pingoru has recorded 25 incidents for Blues: 2 in the last 12 months and 1 in the last 90 days.

Source: status.notehub.io

25incidents recorded
2last 12 months
1last 90 days
3 hourstypical duration

Incidents, newest first

Notice September 29, 2026 Placeholder incident for maintenance longer than expected 33m Cellular Notecards, Notehub UI, Satellite Notecards, Notehub API and 3 more

Started Sep 29, 2026, 05:37 PM UTC· resolved Sep 29, 2026, 06:11 PM UTC

  1. identified Sep 29, 2026, 05:37 PM UTC

    We have created this incident to ensure that our overall uptime metrics are accurate. Our status page service doesn't allow for creating incidents in arrears. During the maintenance period today our event routing was offline for a total of 13 minutes while our API and UI were offline for 31 minutes.

  2. identified Sep 29, 2026, 05:39 PM UTC

    Note that this is NOT a current outage. This notification is to insure we are correctly representing our uptime

  3. identified Sep 29, 2026, 05:52 PM UTC

    Event routing was offline for 13 minutes.

  4. resolved Sep 29, 2026, 06:11 PM UTC

    Total API and UI outage was 31 minutes. Again, this is NOT a current outage. We are making this announcement to accurately represent the impact of our maintenance earlier in the day. Our statuspage system does not let us backdate events.

Read the full incident report →

Minor March 3, 2026 LoRa Notecards failing to sync with Notehub 4h 35m LoRaWan Notecards

Started Mar 03, 2026, 08:06 PM UTC· resolved Mar 04, 2026, 12:42 AM UTC

  1. identified Mar 03, 2026, 08:06 PM UTC

    We have identified an issue that is preventing some LoRa Notecards from syncing with Notehub. In addition, those Notecards may not respond to requests via USB and likely UART and I2C. The issue began at 12:18pm Eastern Time today (March 3rd). Restarting or rebooting the LoRa Notecard fixes the issue. We are investigating options for customers who are unable to restart their LoRa Notecards.

  2. monitoring Mar 03, 2026, 10:07 PM UTC

    We are now seeing the majority of LoRaNotes return to service without needing to be rebooted.

  3. resolved Mar 04, 2026, 12:42 AM UTC

    As of 4:00pm, the incident was resolved and LoRa Notecards returned to service.

Read the full incident report →

Minor July 31, 2025 Notehub Routing Log not currently accessible 41m Notehub UI

Started Jul 31, 2025, 07:59 PM UTC· resolved Jul 31, 2025, 08:41 PM UTC

  1. identified Jul 31, 2025, 07:59 PM UTC

    Due to a systems issue, the Notehub routing log is not currently being updated. In addition, the Route Log tab in the UI is showing a 500 Internal System Error page. We are deploying a fix for this issue and it should be corrected in ~30 minutes.

  2. identified Jul 31, 2025, 08:03 PM UTC

    Routing itself is not impacted. Only storing the status in the route log.

  3. resolved Jul 31, 2025, 08:41 PM UTC

    The issue has been corrected. Event routing itself was not impacted; only storing the route status in the route log.

Read the full incident report →

Critical July 15, 2025 notehub.io and Notehub API down; other services may be degraded 41m Notehub UI, Notehub API

Started Jul 15, 2025, 07:52 AM UTC· resolved Jul 15, 2025, 08:33 AM UTC

  1. investigating Jul 15, 2025, 07:52 AM UTC

    Notehub.io and the Notehub API are currently unavailable. Event routing appears to be working. The incident started at 2:41AM. We will publish further updates as we learn more.

  2. investigating Jul 15, 2025, 07:56 AM UTC

    Services appear to be returning to normal, but we are continuing to investigate.

  3. resolved Jul 15, 2025, 08:33 AM UTC

    The incident was resolved as of 3:43AM ET. Event routing was not impacted. Only access to notehub.io and api.notefile.net

  4. postmortem Jul 15, 2025, 08:55 PM UTC

    Last night’s outage was caused by a default OS upgrade automation. While each Notehub infrastructure service is supported by multiple, redundant server instances, the automated upgrade incorrectly impacted multiple servers at the same time. This caused some key services used by the UI and API to go offline. To insure the issue doesn’t recur, we have disabled this default automation. Then, to ensure we still maintain our OS, we will implement a custom OS upgrade automation to prevent redundant server instances going offline at the same time.

Read the full incident report →