During maintenance operations with one of our racks engineer on-site accidentally blackouted both routers and cut whole connectivity from flespi network to the Internet. Once power was restored our primary router started to pass traffic as usual.
To prevent such situations in the future we are just moved the secondary router to another rack.
The indication of our NOC was wrong, it was one downtime with 160 seconds of unavailability.
Sorry for any inconvenience and have a great weekend!
To prevent such situations in the future we are just moved the secondary router to another rack.
The indication of our NOC was wrong, it was one downtime with 160 seconds of unavailability.
Sorry for any inconvenience and have a great weekend!
#eu: downtime started, error: MQTT client failed to subscribe for flespi/message/gw/channels topic. Usually this indicates the problem with flespi MQTT Broker.
Dear flespi users,
We're investigating the cause of the last downtime.
Sorry for any inconvenience.
We're investigating the cause of the last downtime.
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.
Dear flespi users!
The last downtime was caused by network connectivity issue on our datacenter uplink provider.
Sorry for any inconveniences.
The last downtime was caused by network connectivity issue on our datacenter uplink provider.
Sorry for any inconveniences.
#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.
Dear flespi users!
We're still experiencing short uplink network issues. We've escalated it to our uplink provider.
Sorry for any inconvenience.
We're still experiencing short uplink network issues. We've escalated it to our uplink provider.
Sorry for any inconvenience.
Dear flespi users!
Today, at 14:03 (UTC) we installed the upgrade which triggered malfunction in the streaming services. At 14:33 (UTC) we noticed the problem and immediately rolled back the upgrade. After that streams restored their operations and flushed all buffered messages. There were no drop in the telematics data, just the 30-minute pause in its transmission.
Our unit tests were unable to detect that problem because they operate with freshly created streams however this particular problem was only limited to existent streams. We will enhance our tests to cover similar cases in the future.
We apologize for any inconveniences occurred.
Today, at 14:03 (UTC) we installed the upgrade which triggered malfunction in the streaming services. At 14:33 (UTC) we noticed the problem and immediately rolled back the upgrade. After that streams restored their operations and flushed all buffered messages. There were no drop in the telematics data, just the 30-minute pause in its transmission.
Our unit tests were unable to detect that problem because they operate with freshly created streams however this particular problem was only limited to existent streams. We will enhance our tests to cover similar cases in the future.
We apologize for any inconveniences occurred.
Small correction of timezone conversion: streams transmission pause was between: 15:03 and 15:33 [UTC|GMT].
#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.
Dear flespi users!
The last downtime was caused by the connectivity issues of our uplink provider.
Sorry for any inconvenience and Merry Christmas!
The last downtime was caused by the connectivity issues of our uplink provider.
Sorry for any inconvenience and Merry Christmas!
#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 started, error: Failed to perform REST API call that performs meta-data modifications. This usually indicates that all meta-data database operations are unavailable.
#eu: downtime started, error: Failed to perform REST API call that performs meta-data modifications. This usually indicates that all meta-data database operations are unavailable.