All Systems Operational

About This Site

How-to contact INVERS Support Team (customer with valid support contract):
- All support requests: support@invers.com
- Emergency support, INVERS hosted systems only (if a majority of the fleet is down):
8:00 - 18:00 CET (business hours): +49 271 23888 20, follow the instructions
18:00 - 8:00 CET (outside business hours): +49 271 23888 0, follow the instructions

On these days we only offer emergency support in 2022: January 01, April 15, April 18, May 01, May 26, June 06, June 16, October 03, December 24, December 26.

Cellular connectivity (GSM / UMTS / LTE / 2G / 3G / 4G) ? Operational
CloudBoxx Operational
CloudBoxx API Operational
CloudBoxx Push - Message Queue Operational
Hardware Installation Apps ? Operational
CocoSoft Hosting Operational
CocoSoft Hosting - Europe Operational
CocoSoft Hosting - Asia & Middle East Operational
FleetControl Operational
ICS Hosting Operational
OneAPI Operational
OneAPI REST API Operational
OneAPI Events API (RabbitMQ) Operational
Customer service communication channels ? Operational
Phone ? Operational
E-Mail ? Operational
Ticket system ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Datacenter Maintenance Aug 25, 14:00-18:00 UTC
Our datacenter provider is performing scheduled maintenance. They don't expect any disruptions of our services but still an impact can't be ruled out entirely.
Posted on Aug 4, 09:48 UTC
Past Incidents
Aug 16, 2022
Cellular connectivity under monitoring
Resolved - This incident has been resolved.
Aug 16, 04:21 UTC
Update - WE are back to normal.
Aug 15, 23:55 UTC
Update - The improvement continues reliably.
Aug 15, 22:43 UTC
Update - Improvement continues.
Aug 15, 22:22 UTC
Update - We got the confirmation from the core network operator that the situation improves, but it takes a while until the connections are back (and so an improvement is visible in our monitoring).
Aug 15, 21:53 UTC
Update - We see some improvements, units are returning, we keep monitoring. About <1% of all units are affected.
Aug 15, 21:15 UTC
Update - The root cause is identified, as the number is stable for about 1,5h now, we keep working with the partners to reduce the number of offline units.
Aug 15, 20:37 UTC
Update - The number is not yet decreasing, we keep monitoring and stay in touch with our partners.
Aug 15, 19:10 UTC
Monitoring - The number is not growing anymore and on a small level. We keep monitoring.
Aug 15, 18:13 UTC
Identified - We see a small increase of offline connections, we check with our partners to identify and fix the root cause.
Aug 15, 17:37 UTC
Monitoring - We currently monitor as we got reports from our partners that they see data throughput issues. No issues on INVERS customers detected so for, so it's just FYI
Aug 15, 17:19 UTC
Aug 15, 2022
Aug 14, 2022

No incidents reported.

Aug 13, 2022

No incidents reported.

Aug 12, 2022

No incidents reported.

Aug 11, 2022

No incidents reported.

Aug 10, 2022

No incidents reported.

Aug 9, 2022
Maintenance activity
Completed - The scheduled maintenance has been completed.
Aug 9, 12:10 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 9, 10:10 UTC
Scheduled - We will perform a maintenance, no significant impact expected, very few connections might need a re-connect.

The info is short notice as this maintenance will prevent a potential outage.
Aug 9, 10:09 UTC
Aug 8, 2022
Cellular connectivity issues
Resolved - All devices are back and stable since a while.
Aug 8, 21:15 UTC
Update - We are continuing to monitor for any further issues.
Aug 8, 20:33 UTC
Update - We are still observing slow but steady recovery. About 3/4 of the affected devices are back online.
Aug 8, 20:27 UTC
Update - 1/2 of the defected devices are back. Recovery is proceeding constantly. The core reason seems to be found, currently to be confirmed.
Aug 8, 18:34 UTC
Monitoring - The situation improves significantly. About 1/4 of the affected are back, overall it affected <5% of all units. We keep monitoring the progress, and keep you posted here. Sorry for the inconvenience caused.
Aug 8, 18:07 UTC
Update - We see slight improvements, some of the missing connections are coming back, but we are not out of the woods yet.
Aug 8, 17:33 UTC
Update - Currently it seems an operation at the connectivity provider caused a side-affect on the signalling. The GNOC in the US is working on it, situation still stable but not yet improving.
Aug 8, 17:15 UTC
Update - The GNOC (Global Network Operations Center) and the SME (Subject Matter Expert) established a communication bridge to ensure all experts are working on this matter. While the number increased in between, it's not right now, it's again stable (not growing)
Aug 8, 17:09 UTC
Identified - The degraded performance started at about 15:00 UTC, the affected devices is not growing anymore since ~15:45. The connectivity provider confirmed the issue and is working with the partners to solve it asap. We will post updates here.
Aug 8, 16:38 UTC
Investigating - We currently experience cellular connectivity issues. We are investigating.
Aug 8, 16:17 UTC
Very few more missing heartbeats than usual at this time of the day
Resolved - This incident has been resolved.
Aug 8, 11:23 UTC
Monitoring - For about 15 min, close to normal again
Aug 8, 10:56 UTC
Aug 7, 2022

No incidents reported.

Aug 6, 2022

No incidents reported.

Aug 5, 2022

No incidents reported.

Aug 4, 2022

No incidents reported.

Aug 3, 2022
Degraded Message Queue performance
Resolved - The message delay is on pre-incident level and all services are stable.
Aug 3, 17:40 UTC
Monitoring - An approach to restore stability has been implemented and we are seeing a decrease in delays on the message queue.
Aug 3, 17:07 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 3, 15:51 UTC
Investigating - We are currently investigating a delay in CloudBoxx data that is consumed via our RabbitMQ services. (Events, Trackings, heartbeats)
The issue persists since 14:30 UTC.
Aug 3, 15:41 UTC
Aug 2, 2022

No incidents reported.

← Incident History Powered by Atlassian Statuspage