Live / Stem / Incident
Stem: SolarEdge Monitoring Update
Stem · alsoenergy.comMinor incidentResolved2026-11-05 12:00 UTC
Public — what happened
Summary
Stem said it was investigating a problem that stopped data from devices reporting to PowerTrack through the SolarEdge API, with nothing received since about 5:00 PM ET on November 2. The company said the disruption was linked to the SolarEdge V2 API upgrade, and on November 5 it asked customers to take steps in the SolarEdge Monitoring Portal, pointing them to instructions in a help article. Stem then moved to monitoring for further issues, and the incident was marked resolved at 12:00 on November 5.
Affected
SolarEdge
Timeline
- Started — 2026-11-04 20:26 UTC
- Investigating — 2026-11-04 20:26 UTC (3 updates)
- Monitoring — 2026-11-05 00:10 UTC (3 updates)
- Resolved — 2026-11-05 12:00 UTC · 15h 34m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Stem against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Stem: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Stem report →
More from Stem
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.