INVERS GmbH Status

Resolved: Systems remain stable, and we are closing the incident.

We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers.

We apologize for any inconvenience caused by this incident.

Monitoring: While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Most systems have been available for several minutes. The One API message queue has recovered.

We are still monitoring the situation and gathering facts about the root cause of this incident.

Monitoring: Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

Monitoring: The remaining systems are back online, and we are monitoring their stability.

Monitoring: Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

Investigating: We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: Systems remain stable, and we are closing the incident.

We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers.

We apologize for any inconvenience caused by this incident.

Monitoring: While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Most systems have been available for several minutes. The One API message queue has recovered.

We are still monitoring the situation and gathering facts about the root cause of this incident.

Monitoring: Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

Monitoring: The remaining systems are back online, and we are monitoring their stability.

Monitoring: Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

Investigating: We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: This incident has been resolved.

Monitoring: The issue (solved in between) only affected customers which are using the OneAPI. Customers connected to the Classic-API were not affected.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: Systems remain stable, and we are closing the incident.

We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers.

We apologize for any inconvenience caused by this incident.

Monitoring: While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Most systems have been available for several minutes. The One API message queue has recovered.

We are still monitoring the situation and gathering facts about the root cause of this incident.

Monitoring: Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

Monitoring: The remaining systems are back online, and we are monitoring their stability.

Monitoring: Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

Investigating: We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: This incident has been resolved.

Monitoring: The issue (solved in between) only affected customers which are using the OneAPI. Customers connected to the Classic-API were not affected.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: Systems remain stable, and we are closing the incident.

We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers.

We apologize for any inconvenience caused by this incident.

Monitoring: While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Most systems have been available for several minutes. The One API message queue has recovered.

We are still monitoring the situation and gathering facts about the root cause of this incident.

Monitoring: Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

Monitoring: The remaining systems are back online, and we are monitoring their stability.

Monitoring: Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

Investigating: We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: Systems remain stable, and we are closing the incident.

We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers.

We apologize for any inconvenience caused by this incident.

Monitoring: While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Most systems have been available for several minutes. The One API message queue has recovered.

We are still monitoring the situation and gathering facts about the root cause of this incident.

Monitoring: Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

Monitoring: The remaining systems are back online, and we are monitoring their stability.

Monitoring: Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

Investigating: We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: This incident has been resolved.

Monitoring: The issue (solved in between) only affected customers which are using the OneAPI. Customers connected to the Classic-API were not affected.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

Resolved: Systems remain stable, and we are closing the incident.

We will follow up on the issue internally with the responsible teams and our hosting partners and prepare a corresponding document with a summary. Once this is ready, we will announce it here and be available to discuss it with our customers.

We apologize for any inconvenience caused by this incident.

Monitoring: While the systems have all been back up and running for some time now, we have not yet received any reports from our partners that everything is finally running smoothly again. Until then, we will leave the status at "monitoring.”

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Most systems have been available for several minutes. The One API message queue has recovered.

We are still monitoring the situation and gathering facts about the root cause of this incident.

Monitoring: Most systems, including FleetControl, have been available again for several minutes. The One API message queue is still unavailable.

Monitoring: The remaining systems are back online, and we are monitoring their stability.

Monitoring: Due to redundancy, the Classic API functions are still available, and customer operations can continue as normal.

Investigating: We are continuing to investigate this issue. Customers connected to the Classic-API are not affected.

Investigating: We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.