# MQTT routing issues (Outage ?)

**URL:** <https://discuss.blues.com/t/mqtt-routing-issues-outage/610>\
**Category:** Uncategorized\
**Created:** [January 14, 2022, 9:05am UTC](https://discuss.blues.com/t/mqtt-routing-issues-outage/610 "2022-01-14T09:05:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssozonoff](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@ssozonoff](https://discuss.blues.com/u/ssozonoff)\
**Post date:** [January 14, 2022, 9:05am UTC](https://discuss.blues.com/t/mqtt-routing-issues-outage/610/1 "2022-01-14T09:05:51Z")

</div>

Hi All,

Anyone else experiencing an issue with route forwarding via MQTT from Notehub ? Was working fine until about 23:24 CET on the 13.01.2022. I have made no changes on my end and so far have been unable to find an error anywhere.

Thanks,  
Serge

---

<div class="post-metadata">

**Author:** ![ssozonoff](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@ssozonoff](https://discuss.blues.com/u/ssozonoff)\
**Post date:** [January 14, 2022, 12:59pm UTC](https://discuss.blues.com/t/mqtt-routing-issues-outage/610/2 "2022-01-14T12:59:55Z")

</div>

So looks like the problem is simple after having spent a couple of hours hunting around and making sure the other services in the data pipeline are running correctly.

Simple !! I hit the quota for routed events…

That there is zero indication on the Notehub Dashboard or an email indicating this is simply poor UX. Something for our friends at Blues to address.

---

<div class="post-metadata">

**Author:** ![bsatrom](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/bsatrom/32/3_2.png) [@bsatrom](https://discuss.blues.com/u/bsatrom)\
**Post date:** [January 14, 2022, 1:36pm UTC](https://discuss.blues.com/t/mqtt-routing-issues-outage/610/3 "2022-01-14T13:36:44Z")

</div>

Serge, so sorry for the trouble, and I agree this is poor UX on our part to provide little indication of where you are with Routed events in a month. We’ve logged this to our internal backlog and will get it resolved in short-order. Thanks for bringing this to our attention.

---

<div class="post-metadata">

**Author:** ![ssozonoff](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@ssozonoff](https://discuss.blues.com/u/ssozonoff)\
**Post date:** [January 14, 2022, 2:55pm UTC](https://discuss.blues.com/t/mqtt-routing-issues-outage/610/4 "2022-01-14T14:55:54Z")

</div>

Thanks @bsatrom and have a good weekend.

---

<div class="post-metadata">

**Author:** ![Arnold208](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@Arnold208](https://discuss.blues.com/u/Arnold208)\
**Post date:** [October 10, 2025, 5:58pm UTC](https://discuss.blues.com/t/mqtt-routing-issues-outage/610/5 "2025-10-10T17:58:31Z")

</div>

How did you fix that?