#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.
#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 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 started, error: Failed to connect to flespi MQTT Broker. Usually this indicates either the problem with MQTT Broker itself or when the Broker is shutdowned for the maintenance.
Dear flespi users!
We're observing an uplink fluctuations at our datacenter right now and investigating the case.
We're observing an uplink fluctuations at our datacenter right now and investigating the case.
We now have a report and explanation what has happened this night.
To make long story short it was a misconfiguration inside the routing platform of our up-link provider which failed to correctly detect the flapping link between two routers that impacted automatic management of CARP / VRRP. We experienced periodic packet loss within for approximately 40 minutes until engineer on site detect the problem, disabled automatics and switched the routing to the correct link.
The misconfiguration is being fixed now and similar situations in the future should be avoided.
We apologize for the problems occurred and wish you a very good weekend!
To make long story short it was a misconfiguration inside the routing platform of our up-link provider which failed to correctly detect the flapping link between two routers that impacted automatic management of CARP / VRRP. We experienced periodic packet loss within for approximately 40 minutes until engineer on site detect the problem, disabled automatics and switched the routing to the correct link.
The misconfiguration is being fixed now and similar situations in the future should be avoided.
We apologize for the problems occurred and wish you a very good weekend!
Dear flespi users,
Please be informed that we will perform planned database maintenance today in the next 10 minutes.
We do not expect significant impact on the platform operation, except for a short slowdown of the analytics engine and longer items creation or modification.
Sorry for any inconvenience.
Please be informed that we will perform planned database maintenance today in the next 10 minutes.
We do not expect significant impact on the platform operation, except for a short slowdown of the analytics engine and longer items creation or modification.
Sorry for any inconvenience.
flespi noc (eu)
Dear flespi users, Please be informed that we will perform planned database maintenance today in the next 10 minutes. We do not expect significant impact on the platform operation, except for a short slowdown of the analytics engine and longer items creation…
Dear flespi users,
Planned database maintenance is done.
Have a nice weekend!
Planned database maintenance is done.
Have a nice weekend!
Dear flespi users!
Channel commands REST API is marked as deprecated from now and we will completely discontinue the support of commands on the channel level on December 1, 2022.
Channels will be available only for incoming data flow. For any bidirectional communication with device you are welcome to use device commands: https://flespi.com/blog/remote-device-management-options
Please read full information about upcoming changes and migration instructions here: https://flespi.com/blog/channel-commands-discontinued
Channel commands REST API is marked as deprecated from now and we will completely discontinue the support of commands on the channel level on December 1, 2022.
Channels will be available only for incoming data flow. For any bidirectional communication with device you are welcome to use device commands: https://flespi.com/blog/remote-device-management-options
Please read full information about upcoming changes and migration instructions here: https://flespi.com/blog/channel-commands-discontinued
flespi.io
API Box
Api documentation swagger based
#eu: downtime started, error: Failed to connect to flespi MQTT Broker. Usually this indicates either the problem with MQTT Broker itself or when the Broker is shutdowned for the maintenance.
Dear flespi users!
The last downtime was caused by the automatic re-routing of the uplink connection at the edge of our datacenter.
Normally it should be very fast, and we'll investigate why it was so long for the last time, and take action if needed.
Sorry for any inconvenience.
The last downtime was caused by the automatic re-routing of the uplink connection at the edge of our datacenter.
Normally it should be very fast, and we'll investigate why it was so long for the last time, and take action if needed.
Sorry for any inconvenience.
#eu: downtime started, error: Failed to add command to channel commands queue. Usually this indicates either flespi telematics hub REST API overload or when the hub is in the maintenance mode.
Recent downtime is due to a DDoS attack towards our uplink provider and 30 seconds latency the network guard system need before the attack is detected and mitigated. We are unable to prevent such cases currently, but may implement some optimizations later. 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.