All Systems Operational

Frontend Operational
90 days ago
99.96 % uptime
Today
Public API Operational
90 days ago
99.96 % uptime
Today
Private gridBox API Operational
Platform Components (beta) Operational
90 days ago
99.95 % uptime
Today
Measurement ingestion Operational
90 days ago
100.0 % uptime
Today
Asset inventory management Operational
90 days ago
100.0 % uptime
Today
Measurement processing Operational
90 days ago
100.0 % uptime
Today
Measurement aggregation Operational
90 days ago
99.95 % uptime
Today
Measurement API Operational
90 days ago
99.97 % uptime
Today
Backend HTTP API Operational
90 days ago
100.0 % uptime
Today
Backend gRPC API Operational
90 days ago
100.0 % uptime
Today
Cloud-to-Cloud integration Operational
90 days ago
99.6 % uptime
Today
Live View Operational
90 days ago
100.0 % uptime
Today
Webhook Delivery Operational
90 days ago
100.0 % uptime
Today
Flex Layer Operational
90 days ago
100.0 % uptime
Today
Third Party Operational
Frontend Email Delivery Operational
Frontend Authentication API Operational
AWS ec2-eu-central-1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Mar 20, 2026

No incidents reported today.

Mar 19, 2026
Resolved - The issue was resolved on Enode side and our endpoint is back operational
Mar 19, 13:04 CET
Identified - The endpoint /systems/{systemID}/assets/{assetID}/chargesessions is failing since  11:36 due to a failure on Enode side.
We already contacted Enode.

Mar 19, 12:20 CET
Mar 18, 2026
Resolved - Due to a data migration on our permission system, users did not have permissions to start gridBox scan or reset jobs. This included admin users, installers, and customers. The problem persisted between 2026/03/18 05:00PM and 2026/03/19 01:00PM.
Mar 18, 17:00 CET
Resolved - Between 10:35 and 11:45 the linking process was broken.
The issue is already fixed. Next link tentatives are succeeding already.
We are working on getting the failed asset creations that happened in the period done.

Mar 18, 12:13 CET
Mar 17, 2026

No incidents reported.

Mar 16, 2026
Resolved - From 12:04 to 13:34 the data arrived late from Enode, leading to the charge session of some EVs plugged in the period to not be optimized
Mar 16, 16:40 CET
Mar 15, 2026

No incidents reported.

Mar 14, 2026

No incidents reported.

Mar 13, 2026

No incidents reported.

Mar 12, 2026
Resolved - This incident has been resolved.
Mar 12, 11:37 CET
Identified - We have identified the issue and we should be processing historical measurements again. We will backfill missing data.
Mar 12, 10:15 CET
Investigating - Since 2:30 am this morning, historical measurement aggregation is very slow. It's caught up to 5:30, but we are falling further behind. We are investigating the issue.
Mar 12, 09:42 CET
Resolved - From 16:30 to 19:40 CET the EV events were sent with some minutes of delay. The problem was identified and fixed, restoring normal operation.
Mar 12, 04:30 CET
Mar 11, 2026

No incidents reported.

Mar 10, 2026

No incidents reported.

Mar 9, 2026
Resolved - The fix has proven effective, all affected systems have recovered.
Mar 9, 10:28 CET
Update - We are continuing to monitor for any further issues.
Mar 9, 09:54 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 9, 09:45 CET
Resolved - The incident caused some deviations in the historical data calculations, and temporarily reduced forecast accuracy.
The forecast accuracy is back to normal, but artifacts of measurement errors may show in historical measurements for the time between March 3rd and March 4th (for a small subset of affected systems March 5th) for a small number of systems.

Mar 9, 09:53 CET
Update - Configurations have been restored for all affected assets, all systems are now operating normally.
Historical measurements and derived indicators for affected systems may be wrong between March 03, 2026, 10:17 and March 05, 2026, 13:03.

Mar 5, 13:09 CET
Monitoring - A fix for the root cause has been rolled out. We have restored the configuration for affected assets. We are still investigating a small number of potentially impacted systems.
Historical measurements are impacted. We are evaluating options for applying a data fix.

Mar 4, 18:09 CET
Identified - The issue has been identified, we are working on a fix.
Mar 4, 15:57 CET
Investigating - Assets where reverse flow is enabled are being treated as forward flow. This impacts the local EMS optimization and measurements.
Mar 4, 15:57 CET
Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.