Type to search
Advanced channel search

Telegram Analytics

Subscribe to stay informed about TGStat news.
img
ad

TGStat Bot

Bot to get channel statistics without leaving Telegram
img
ad

TGAlertsBot

Monitoring of keywords in channels and chats
img
ad

SearcheeBot

Your guide in the world of telegram channels
img
ad

flespi noc (eu)

@flespi_noc
Channel's geo and language: World, English
Category: Technologies

flespi eu region NOC

Related channels
Channel's geo and language
World, English
Category
Technologies
Statistics
Is this your channel? Confirm Канал в реестре блогеров РКН? Confirm Channel history
Posts filter

flespi noc (eu)

20 Feb, 18:15

Open in Telegram Share Report
Today between 11:40-15:00 UTC our webhooks service was partially unavailable. The issue affected only webhooks processing MQTT messages with payloads larger than 512 bytes. Webhooks handling smaller messages continued to operate normally.

The disruption occurred during a gradual rollout of internal MQTT Broker optimizations. While our standard uptime testing procedures include webhook functionality verification, the test cases did not cover processing of large MQTT payloads.

All other platform services remained fully operational during this period. The webhook service has been fully restored to normal operation.

We apologize for any inconvenience this may have caused.
flespi Service Level Agreement: how to guarantee 99.9% uptime
Learn how flespi shows respect to your business by providing a High Availability service.
89 0 0
flespi noc (eu)

1 Feb, 11:01

Open in Telegram Share Report
We detected, mitigated the issue and currently are in the process of completely fixing it. During the issue for a few minutes REST API operations towards the telematics hub (/gw/... endpoint) were partially unavailable.
150 0 0
flespi noc (eu)

1 Feb, 10:53

Open in Telegram Share Report
#eu: downtime ended, period: 77 second(s)
139 0 0
flespi noc (eu)

1 Feb, 10:52

Open in Telegram Share Report
#eu: downtime started, error: Failed to perform https://flespi.io/gw/xxx GET request. Usually this indicates either flespi telematics hub REST API overload or when the hub is in the maintenance mode.
135 0 0
flespi noc (eu)

1 Feb, 10:51

Open in Telegram Share Report
#eu: downtime ended, period: 40 second(s)
131 0 0
flespi noc (eu)

1 Feb, 10:51

Open in Telegram Share Report
#eu: downtime started, error: Failed to perform https://flespi.io/gw/xxx GET request. Usually this indicates either flespi telematics hub REST API overload or when the hub is in the maintenance mode.
129 0 0
flespi noc (eu)

1 Feb, 10:50

Open in Telegram Share Report
#eu: downtime ended, period: 65 second(s)
123 0 0
flespi noc (eu)

1 Feb, 10:49

Open in Telegram Share Report
#eu: downtime started, error: Failed to perform https://flespi.io/gw/xxx GET request. Usually this indicates either flespi telematics hub REST API overload or when the hub is in the maintenance mode.
120 0 0
flespi noc (eu)

16 Jan, 14:20

Open in Telegram Share Report
Dear flespi users!

A 15-hour partial disruption of the webhook service occurred on January 15, 2025, due to internal infrastructure reorganization. The incident affected message delivery for some webhooks. Messages within configured Queue TTL were preserved and delivered after service restoration. Messages that exceeded their Queue TTL during the downtime were not recovered.

We apologize for any inconvenience caused. For optimal webhook configuration, we recommend setting appropriate Queue TTL values based on your use case requirements.
168 0 1
flespi noc (eu)

15 Oct 2024, 09:44

Open in Telegram Share Report
Dear flespi users!

Today we are rolling out the update to the flespi analytics system that will allow it to control geofences assigned directly to devices.
During the update each analytics service will totally refresh accumulated device messages cache which may result in extra intervals updates generated for some unstable configurations of calculators.
On top of this we expect additional load in our MQTT Broker bus and telematics messages storage, but most probably you will not notice it.

During the upgrade for some devices (less than 1% of total amount) there can be delays in intervals detection. Such delays usually are less than a minute but in some rare cases this can introduce up to few minutes latency in interval generation.

The upgrade may take up to 2 days (we have 1M devices and track 2M of realtime events) and we will publish a message in the analytics changelog once it is completed and verified: https://forum.flespi.com/d/16-changelog-flespi-analytics

Thanks for your understanding and have a great Tuesday!
[Changelog] flespi analytics
Here we will post information about flespi analytics new features and bugfixes.
165 0 3
flespi noc (eu)

26 Sep 2024, 11:23

Open in Telegram Share Report
Dear flespi users!

The last downtime was caused by sudden routing changes at one of our TIER 1 upstream providers for both datacenters. Routes recalculation took some time, which was the cause of connectivity loss.

Sorry for any inconvenience.
184 0 0
flespi noc (eu)

26 Sep 2024, 10:42

Open in Telegram Share Report
#eu: downtime ended, period: 167 second(s)
173 0 0
flespi noc (eu)

26 Sep 2024, 10:41

Open in Telegram Share Report
#eu: downtime started, error: Failed to perform https://flespi.io GET request. Usually this indicates either flespi eu datacenter network uplink connection problem or when the platform is in the maintenance mode.
150 0 0
flespi noc (eu)

16 Aug 2024, 16:29

Open in Telegram Share Report
Dear Flespi users,

We experienced a brief downtime that affected the Gateway REST API for a short period. However, device connectivity and the MQTT broker were not impacted.

We apologize for any inconvenience caused.
241 0 0
flespi noc (eu)

16 Aug 2024, 16:10

Open in Telegram Share Report
#eu: downtime ended, period: 90 second(s)
221 0 0
flespi noc (eu)

16 Aug 2024, 16:10

Open in Telegram Share Report
#eu: downtime started, error: Failed to perform https://flespi.io/gw/xxx GET request. Usually this indicates either flespi telematics hub REST API overload or when the hub is in the maintenance mode.
217 0 0
flespi noc (eu)

8 Jul 2024, 21:30

Open in Telegram Share Report
Dear Flespi users,

The recent downtime was caused by a high load on our message database system, which resulted from a hardware failure on one of our disks exhibiting non-standard symptoms. Rebalancing this significant load took enough time for our automated test nodes to detect message storage latency. The faulty hardware has been taken offline. We will work on improving detection for such situations in the future.

We apologize for any inconvenience caused.
285 0 0 4
flespi noc (eu)

8 Jul 2024, 20:52

Open in Telegram Share Report
#eu: downtime ended, period: 21 second(s)
241 0 0
flespi noc (eu)

8 Jul 2024, 20:52

Open in Telegram Share Report
#eu: downtime started, error: Simulated telematics device connected to the channel, sent the packet with message, but channel didn't replied to it. Usually this indicates the problem with flespi Telematics Gateway.
234 0 0
flespi noc (eu)

8 Jul 2024, 20:51

Open in Telegram Share Report
#eu: downtime ended, period: 56 second(s)
221 0 0
20 last posts shown.