Fix EV charger reliability and uptime issues before drivers notice
You get paid per session, so every port that reports itself available and then turns a driver away costs you the session, the driver, and a line in your uptime report. GridLink reads every signal your network produces, from the chargers' own messages to the connection underneath, works out why the session failed, and clears the fault through your existing charge point management system.
The number in your report and the number the driver lives through
Public charging is where reliability stopped being an operations problem and became a funding one. NEVI-funded ports have to hold 97% uptime. California requires networks to report first-attempt charging success. Michigan is expected to follow, and Massachusetts has proposed holding back funding against performance.
91% to 97%
First-attempt charging success across deployed networks.
60%
Of tickets resolved with no one dispatched to the site.
45%
Of fixes landing outside business hours, when the network still has drivers.
Measured across GridLink deployments.
The four failures that move these numbers are the ordinary ones: chargers that go quiet, connectors that stay locked after a session, authorizations that never come back in time, and units delivering a fraction of their rated power while reporting healthy. Otto handles them by naming the cause, running the fix through your management system, and confirming the port came back.
The driver at the plug is part of that loop rather than a bystander. Someone standing at a port that will not start can reach GridLink by text and get an answer in seconds, including whether the bay next to them is working, which is often the whole fix. Where a port has already dropped, drivers heading to it can be told before they arrive. A prevented trip costs less than a recovered session.
Networks that also run depot charging for their own vehicles get the overnight side of this on the fleets page.
Hardware mix is not a blocker, and neither is the management system you settled on.
Questions network operators ask
Uptime measures the share of time a port reports itself available. First-attempt success measures the share of drivers who plug in and actually start charging. A port can report available for a full month and still fail drivers on stuck connectors, authorization timeouts, or power that never reaches the rated level. NEVI sets a 97% uptime floor, and California already requires first-attempt success reporting, so public networks are now measured on both.
No. GridLink runs alongside the system you already use and acts through its API. Deployments run today on Monta, Ampeco, Ampcontrol, Driivz, and EV Connect, and any management system with API access can be connected.
The first month is an observation window. Otto reads every signal your network produces, learns how your hardware fails, and builds the workflows for those faults before it starts resolving anything on its own. Nothing is sent to a charger until the behavior behind it has been seen in your own data.
Bring us your worst-performing sites.
Thirty minutes on your uptime numbers, your hardware mix, and the faults your team keeps clearing by hand. Or start with the reliability calculator and see what failed sessions are costing the network.