flespi noc (eu)
84 members
56 links
flespi eu region NOC
Download Telegram
to view and join the conversation
Dear flespi users!

We're going to simplify the development of streaming protocols. Thus, we decided to move the protocol from a stream configuration to an independent entity. This entailed small changes in the REST API, which you can see here:
https://forum.flespi.com/d/25-changelog-flespi-telematics-hub/35
#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.
#eu: downtime ended, period: 153 seconds
Dear flespi users!
We observed an uplink network connectivity issues.
We're investigating this case.
Sorry for any inconvenience
Dear flespi users!
It was a short DDoS attack on the data center where our services are located.
It was filtered by the automatic triggers on the uplink provider side.
Sorry for any inconvenience.
#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.
#eu: downtime ended, period: 6 seconds
flespi noc (eu)
#eu: downtime ended, period: 6 seconds
Dear flespi users!

The last downtime message was caused by a human error during the Telematics Gateway services maintenance process.
We always try to automate everything we can to avoid issues like this.

Sorry for any inconvenience.
For those who are using flespi analytics services (calculators) - we are performing maintenance of one server which will result for 5 minutes delay for automatic analytics operations for 15% of assigned devices. After that delay affected devices will automatically synchronize to remaining analytics servers, which usually take up to 15 minutes. After a while, when we finish operations with the server and put it back online, some devices will automatically synchronize back.

In general you should expect some delays for some devices in analytics events generation. Also you may receive bunch of updates for assigned device properties via MQTT during recalculation.

Sorry for any inconvenience, we plan to repeat this operation with one more server later this week.

If you are interested, you may read more about flespi analytics architecture here: https://flespi.com/blog/flespi-analytics-architecture
Hi flespi users,

The new REST API for streams was announced a few months ago, and the new and old format were available until mid-December.
The obsolete format has now been removed and is no longer supported.

Please let us know if you have any problems with streaming.
#eu: downtime started, error: Timeout occurred while waiting for channel messages via MQTT API. Usually this indicates performance problems due to high load for either flespi Telematics Gateway (channels) or MQTT Broker itself.
#eu: downtime ended, period: 30 seconds
Dear flespi users,

We currently experience short time network connectivity issues in our datacenter due to a DDoS attack. These problems are short terms - 5-30 seconds of connections unavailability at the moment and our provider is figuring out how to shield it.

Sorry for any inconveniences.
#eu: downtime started, error: Telematics Gateway failed to accept incoming connection from simulated device. Usually this indicates that channel's IP:port is unavailable for devices.
#eu: downtime ended, period: 30 seconds
#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.
#eu: downtime ended, period: 62 seconds
Over the past few weeks, we have moved the device REST API methods to a new engine. The methods and their result remain unchanged.
Today we plan to smoothly upgrade our services. But if you notice any incorrect behavior, please contact us.

Thank you for being with us.