Start with what you can observe

A charger disappears from the dashboard, returns later, and drops again. Drivers may also report that they cannot start a session. For a site owner, the immediate challenge is deciding who should investigate: the charging network, the IT team, or a field technician.

An offline alert is a symptom, not a diagnosis. ChargePoint’s CT4000 owner guide defines its Unreachable alarm as a lost connection to the ChargePoint network. That model-specific label does not identify which part of the communications path failed. The steps below are SureCharge recommendations for organizing the investigation; always follow your equipment’s own documentation.

Capture evidence before changing anything

Record the station and connector IDs, when the problem began, the last dashboard update, and any displayed message. Ask an on-site contact to photograph the normal display from a safe position and report whether other chargers are affected. A lit screen is useful information, but it does not prove that charging works.

Note recent changes: an internet outage, router replacement, password update, firewall change, equipment service, or power interruption. Keep these as possible leads. Do not assume that the most recent change caused the fault, and do not include network passwords or customer payment details in the ticket.

Separate the local network from the cloud connection

ChargePoint’s CP6000 North America troubleshooting guide distinguishes the connection to the local router, the secure network connection, and access to its cloud service. It identifies issues such as missing network addresses, name-resolution failures, and firewall restrictions. Those distinctions are a useful example of why “the internet is working” is not a complete diagnosis.

Ask the authorized IT administrator to check the charger’s specific connection against the manufacturer’s network requirements. A phone browsing successfully nearby does not test the charger’s connection. Have IT document what was checked and any changes made; avoid making ad hoc firewall exceptions or changing charger settings without an approved plan.

Use the pattern to choose the next owner

SureCharge recommends comparing affected assets and outage times. If several chargers drop together, investigate shared dependencies such as the site network or a gateway. If one charger repeatedly fails while nearby units remain connected, focus the support request on that asset. Neither pattern, by itself, proves a cause.

For an unresolved cloud connection or recurring network alarm, involve the charging network or manufacturer with the evidence collected. Bring in a qualified field technician when support identifies a hardware, wiring, or electrical investigation. For a fleet, notify dispatch early and use a confirmed working alternative within the site’s operating plan.

Treat a reset as a controlled action

A restart may be part of a manufacturer’s troubleshooting procedure, but repeated resets can interrupt service and make the original symptoms harder to reconstruct. SureCharge recommends capturing the evidence first, checking for active sessions, and agreeing on an authorized action with support.

Do not open cabinets, handle internal network components, operate electrical equipment, or repeatedly reset a tripping breaker as a general troubleshooting shortcut. Charger servicing and electrical work belong with appropriately qualified personnel following manufacturer procedures. If there is visible damage, smoke, a burning smell, or another safety concern, stop routine troubleshooting and follow the site’s emergency procedures.

Verify recovery and watch for recurrence

After the approved correction, confirm that dashboard information is updating and arrange a documented charging test where safe and appropriate. Record the result and who verified it. Monitor through the next normal operating period rather than closing the ticket solely because the charger briefly reappeared online.

The Department of Energy’s Alternative Fuels Data Center recommends establishing maintenance responsibility and defining response and repair expectations. Use that principle here: keep one incident owner responsible for updates and escalation until the agreed recovery checks are complete.

Keep this checklist with your service desk

  • Capture asset IDs, timestamps, display messages, and recent changes.
  • Compare the affected chargers without assuming a cause.
  • Have authorized IT check the charger’s actual network path.
  • Coordinate any restart through manufacturer guidance and support.
  • Document a charging test, monitor recurrence, and assign the next action.

Sources & further reading