User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
gridserve.com · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: GreenFlux Services is down
Source: the vendor's status page · We are not affiliated with GRIDSERVE.
Estimated fix: Not enough GRIDSERVE history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 min ago. Last stored result reached it in 43 ms.
Minor incident
GreenFlux Services is down Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 8 | 0 | 0.0 | 85 ms | 0 |
| Nov 8 | 0 | 0.0 | 100 ms | 0 |
| Nov 8 | 0 | 0.0 | 123 ms | 0 |
| Nov 8 | 0 | 0.0 | 82 ms | 0 |
| Nov 9 | 0 | 0.0 | 89 ms | 0 |
| Nov 9 | 0 | 0.0 | 60 ms | 0 |
| Nov 9 | 0 | 0.0 | 82 ms | 0 |
| Nov 9 | 0 | 0.0 | 82 ms | 0 |
| Nov 10 | 0 | 0.0 | 106 ms | 0 |
| Nov 10 | 0 | 0.0 | 71 ms | 0 |
| Nov 10 | 0 | 0.0 | 86 ms | 0 |
| Nov 10 | 0 | 0.0 | 141 ms | 0 |
| Nov 11 | 0 | 0.0 | 223 ms | 0 |
| Nov 11 | 0 | 0.0 | 126 ms | 0 |
| Nov 11 | 0 | 0.0 | 397 ms | 0 |
| Nov 11 | 0 | 0.0 | 214 ms | 0 |
| Nov 12 | 0 | 0.0 | 194 ms | 0 |
| Nov 12 | 0 | 0.0 | 191 ms | 0 |
| Nov 12 | 0 | 0.0 | 98 ms | 0 |
| Nov 12 | 0 | 0.0 | 216 ms | 0 |
| Nov 13 | 0 | 0.0 | 103 ms | 0 |
| Nov 13 | 0 | 0.0 | 213 ms | 0 |
| Nov 13 | 0 | 0.0 | 57 ms | 0 |
| Nov 13 | 0 | 0.0 | 78 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for GRIDSERVE yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when GRIDSERVE goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GRIDSERVE alerts to Slack, Discord or a webhook — free.
We track GRIDSERVE (gridserve.com) as part of the Cloud & developer group. EV charging made easy. We deliver reliable, fast, and contactless electric vehicle charging at fantastic locations all over the country.
GRIDSERVE publishes an official status page at status.gridserve.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 146 ms average, 41–349 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: GreenFlux Services is down
We have not recorded a public GRIDSERVE incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
146 ms on average over the last 24 hours (41–349 ms).
Yes, at https://status.gridserve.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report GRIDSERVE here at once, the problem is on GRIDSERVE's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with GRIDSERVE. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.