Incident Summary
On 11 October 2026, between approximately 14:17 and 15:37 CEST, GreenFlux experienced a degradation of several core platform services. During this period, some charging session authorisation requests were not processed successfully, which may have prevented affected drivers from starting charging sessions.
The issue was identified through automated monitoring, and our engineering teams immediately began investigating and mitigating the impact. Service performance was restored and verified through continued monitoring.
Customer Impact
Customers may have experienced:
- Intermittent failures when authorising charging sessions.
- Charging sessions that could not be started due to unsuccessful token validation.
- Delays or failures in related platform services during the incident window.
The impact was partial and intermittent. Not all customers or charging sessions were affected.
Timeline
All times are in CEST (UTC+02:00).
Time | Event |
14:17 | Automated monitoring detected an elevated failure rate in charging session authorisation requests and triggered an alert. |
14:18 | The incident was acknowledged and the engineering team began investigating the issue. |
14:41 | Investigation identified an increase in unsuccessful token authorisation responses affecting charging session starts. |
14:47 | Engineers confirmed service degradation and timeouts within the authorisation process. |
14:48 | Mitigation activities were initiated, including restarting the affected authorisation service. Service performance began to improve, although intermittent errors were still observed. |
15:37 | Service stability was restored and charging session authorisations returned to normal operation. |
19:00 | Follow-up checks confirmed that all services continued to operate normally. |
12 October 2026 | A detailed investigation identified excessive API traffic from a single client as the triggering factor behind the service degradation. Corrective actions were defined to prevent recurrence. |
Root Cause
The incident was triggered by an unusually high volume of requests from a single API client within a very short period of time.
This unexpected traffic spike created excessive load on shared platform components and caused degradation of several backend services involved in processing charging session authorisations. As a result, some authorisation requests experienced delays or failed to complete successfully, leading to charging session start failures for a subset of users.
Our investigation identified that additional protective controls, such as request-rate limiting, were not in place to sufficiently isolate shared services from this type of traffic pattern.
Resolution
Once the issue was identified, engineering teams took immediate action to stabilise the affected services. This included restarting the impacted authorisation service and closely monitoring platform behaviour.
Following these actions, service performance returned to normal and no further abnormalities were detected. Subsequent monitoring confirmed the stability of all affected services.
Preventive Actions
To reduce the likelihood and impact of similar incidents in the future, GreenFlux is implementing the following improvements:
- Introduction of API rate-limiting controls to prevent excessive traffic from affecting shared platform services.
- Additional protection mechanisms for critical backend services to improve resilience under high-load conditions.
- Further investigation into service behaviour during overload scenarios to strengthen platform stability.
- Enhancements to monitoring and alerting capabilities to enable faster detection and response to abnormal traffic patterns.
- Continued review of platform safeguards to ensure individual client activity cannot adversely affect other platform users.