flespi noc (eu)

2021-06-18 12:11:35 We are currently observing high load on the flespi storage system which may result to the larger then average latency on your operations related to messages access and manipulation. We are looking into the issue at the moment and will update you later. Open / Comment

2021-06-11 15:51:40 We are currently provisioning a set of additional servers for our analytic system. It means that within few next hours you may experience some delays in intervals calculation processing or extra update events generation during the automatic re-balancing process of calculations to new servers. Open / Comment

2021-06-11 11:29:06 For those who are using flespi from AWS: currently we are observing some issues accessing flespi from aws-us-west-1 region. They are related to the connectivity on the path from aws-us-west-1 to flespi eu region. Duration of these interruptions is short - up to 2 minutes each, frequency - 1-2 times per hour.
If your infrastructure is located there we recommend to contact AWS regional support team with a dump of mtr or traceroute to flespi.io. According to our information packets drop is occurring on the very first hop. Open / Comment

2021-05-12 20:48:07 A little update on the issue with network: recently we detected 101 seconds of flespi unavailability from AWS at 17:18 UTC. All symptoms are very similar to what we had yesterday night(in EU timezone). The problem currently is diagnosed up to the Cogentco tier provider, somewhere on their EU<=>US link. Our uplink connectivity provider has already switched the route to another path, but still we may be affected.

So if you are located in America and have any issues please be informed that we keep eye on it and do our best together with our uplink provider. Once we have more detailed report we will update. Open / Comment

2021-05-12 14:15:07 Dear flespi users!

Today we've faced a few network failures. The first one affected the American users, the second - all users of the flespi EU datacenter.

Both of them were caused by the planned maintenance operations by the backbone link providers. Those operations caused BGP and OSPF/MPLS failures between the users and the flespi datacenter.

We hope that these short interrupts did not influence a lot your experience with flespi and of course backbone link provider maintenance operations is out of our scope of control. Open / Comment

2021-05-12 05:21:46 Dear flespi users!
We observed an uplink network connectivity issues.
We're investigating this case.
Sorry for any inconvenience Open / Comment

2021-05-12 05:06:18 #eu: downtime ended, period: 27 seconds Open / Comment

2021-05-12 05:05:51 #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. Open / Comment

2021-04-16 17:46:27 We are declaring the future upgrade for filter expression format in various REST API calls. The most important and popular are the GET /devices/XXX/messages, GET /calcs/XXX/devices/YYY/intervals API calls. But also all calls for logs and statistics retrieval are affected as well as GET /channels/XXX/messages API call in serial mode together with containers and cdns in storage system. Take special care to the filter field in your API call. If you are using this field - you may be affected, if not - just be informed.

Once the whole upgrade is finished it will be possible to use extended expressions in requests with math functions, arithmetic operations, brackets for operations priority and so on. But so far we made simple compatibility mode that you need to adjust your requests to.

Please read the whole changelog post here with dates and stages: https://forum.flespi.com/d/25-changelog-flespi-telematics-hub/56
We will further publish all updates about this process on the forum under the link above and you may subscribe with email to keep yourself updated. Open / Comment

2021-04-12 11:08:03 We have two important updates.
The first refers to flespi users who have their own solutions that work with device telemetry via the REST API. We're going to replace the old telemetry request with a more flexible request.
More details here: https://forum.flespi.com/d/25-changelog-flespi-telematics-hub/55
Before replacing, we'll make sure no one else is using the deprecated method.

The second one is an error in the Wialon retranslator streams. Due to an implementation error, the stream correctly sent only the first message in the packet, the rest of the messages were garbled.
It lasted from 2021/04/07 17:15 (UTC) to 2021/04/09 15:26 (UTC). We apologize for this situation and are ready to re-stream lost messages again if you need it. Open / Comment