Summary
On 15 July 2026, GreenFlux experienced an incident affecting the authorization of external charging tokens. As a result, charging sessions that relied on external token authorization could not be authorized successfully for approximately two hours.
The issue was detected through automated monitoring, and service was restored after the affected component was redeployed. During the incident, approximately 8,145 token authorization requests failed.
We sincerely apologize for the disruption and any inconvenience this may have caused.
Customer Impact
Between approximately 11:17 CEST and 12:59 CEST, requests requiring external token authorization were impacted.
Customers may have experienced:
- Failed authorization attempts when using external charging tokens.
- Inability to start charging sessions that depended on external token validation.
- Delays or interruptions in charging services relying on roaming token authorization.
No data loss occurred as a result of this incident.
Timeline
Time (CEST) | Event |
11:17 | The external token authorization service became unavailable. |
11:39 | Automated monitoring detected a significant increase in authorization failures and triggered a critical alert. |
12:04 | Investigation identified that the token authorization service was no longer operational. |
12:56 | The investigation confirmed that a required deployment package was missing, preventing the service from starting correctly. |
12:59 | The service was redeployed and functionality was restored. |
13:40 | An additional redeployment was successfully completed to ensure service stability. |
17:09 | The underlying cause of the missing deployment package was identified. |
Root Cause
The incident was caused by an issue in an automated deployment maintenance process.
A maintenance script responsible for removing outdated deployment packages encountered temporary platform availability errors while verifying which deployment package was actively being used. Due to insufficient validation in the script, it incorrectly removed all deployment packages instead of preserving the active one.
The affected service continued to operate normally until a subsequent restart occurred. When the service attempted to restart on 15 July, the required deployment package was no longer available, preventing the service from starting successfully and resulting in the authorization outage.
Resolution
To restore service, GreenFlux redeployed the affected application, which recreated the required deployment package and allowed the service to start successfully.
Service functionality returned to normal immediately after the redeployment was completed.
Corrective and Preventive Actions
To prevent similar incidents from occurring in the future, GreenFlux has implemented and is implementing the following improvements:
- Deployment script safeguard
- The maintenance script will be updated to verify that the active deployment package has been positively identified before any cleanup actions are performed.
- Enhanced service health monitoring
- Additional health checks will be introduced to detect service unavailability faster and provide earlier warning of startup issues.
- Faster incident response
- Monitoring and alerting processes will be improved to reduce response times for critical service failures.
- Improved escalation process
- Relevant support and engineering teams will be notified immediately when critical incidents occur, ensuring faster investigation and communication.
- Deployment process improvements
- Deployment maintenance logic will be reviewed and managed through stricter change-control and approval processes to reduce operational risk.
Conclusion
This incident resulted from a failure in an automated deployment maintenance process that removed a required deployment package. When the affected service restarted, it was unable to start successfully, causing external token authorization requests to fail.
The issue was resolved through redeployment of the service, and several technical and operational improvements have been identified to reduce the likelihood of recurrence and improve response times should a similar situation arise in the future.
GreenFlux regrets the impact of this incident and is committed to continuously improving the reliability and resilience of our platform.