On 29 August 2026, a service disruption affected the connectivity of a subset of charging stations to the GreenFlux platform. As a result, impacted charging stations were temporarily unable to exchange operational messages with the platform using the OCPP protocol.
The issue affected GreenFlux public OCPP endpoint. Service was fully restored on the same day, and charging stations progressively reconnected to the platform after remediation was completed.
Customer Impact
During the incident, affected charging stations were unable to establish or maintain a connection with the GreenFlux platform. This may have impacted charging station monitoring, status updates, and operations that require communication with the platform.
An assessment of charging activity was performed by comparing charging session volumes on the day of the incident against historical data from comparable Saturdays.
The incident is estimated to have resulted in an approximately 8% reduction in charging sessions compared to expected charging activity levels.
While this assessment provides only an estimate, it indicates the overall impact on charging activity which also depended on the charging station configuration and operational mode..
Timeline (CEST)
Time | Event |
05:10 | GreenFlux public charging station connectivity service became unavailable. |
07:30 | Incident escalated to technical teams via 24/7 line. |
08:36 | Technical teams initiated active troubleshooting and recovery efforts. |
09:10 | Customer communication published via the Status Page. |
09:15 | Corrective actions implemented and service recovery initiated. |
09:29 | Service restoration confirmed and communicated. |
09:35 | Most charging stations successfully reconnected. |
11:34 | All queued communications processed and platform operations fully stabilized. |
Root Cause
The incident was caused by a configuration issue introduced during infrastructure maintenance activities performed the day before the outage.
As part of these activities, changes were made to shared cloud infrastructure components. One of the affected services relied on access permissions that were unintentionally removed during the change process. As a result, the OCPP socket services were unable to access required application resources and gradually became unavailable.
This dependency was not identified during the change impact assessment, which allowed the issue to remain undetected until service degradation occurred.
Resolution
After investigation, the missing service permissions were identified and restored.
The following actions were taken to resolve the incident:
- Restored the required service access permissions.
- Restarted the affected platform components.
- Monitored platform recovery and charging station reconnections.
- Verified that queued communications were successfully processed after service restoration.
Following these actions, all affected services returned to normal operation.
Preventive Actions
To reduce the risk of similar incidents in the future, we are implementing the following improvements:
- Enhanced dependency management: We will maintain clear documentation of critical infrastructure components and the services that depend on them to ensure all production dependencies are identified before changes are made.
- Stronger change validation: Resource changes will include additional checks to verify that required permissions and access configurations remain intact after infrastructure modifications.
- Improved monitoring and alerting: We are strengthening automated monitoring and escalation processes to enable faster detection of service disruptions and quicker engagement of the relevant teams.
- Review of shared infrastructure components: We will assess and simplify shared infrastructure dependencies where possible, improving visibility and reducing operational complexity.
- Improved incident response procedures: We are updating escalation paths and on-call processes to accelerate coordination during critical production incidents.
Conclusion
We sincerely apologize for the disruption caused by this incident. While service was restored promptly once the root cause was identified, we recognize the impact that connectivity interruptions can have on charging operations.
We have completed a thorough review of the incident and are implementing the improvements outlined above to strengthen our change management processes, increase visibility of infrastructure dependencies, and further improve incident detection and response times.
