User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
gridserve.com · Cloud & developer
Is GRIDSERVE down?
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.
What to try while GRIDSERVE is having problems
Estimated fix: Not enough GRIDSERVE history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → gridserve.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 20 min ago. Last stored result reached it in 112 ms.
Official status
Minor incident
GreenFlux Services is down Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 83 ms | 0 |
| Mon 21 | 0 | 0.0 | 82 ms | 0 |
| Mon 23 | 0 | 0.0 | 72 ms | 0 |
| Tue 01 | 0 | 0.0 | 98 ms | 0 |
| Tue 03 | 0 | 0.0 | 139 ms | 0 |
| Tue 05 | 0 | 0.0 | 60 ms | 0 |
| Tue 07 | 0 | 0.0 | 62 ms | 0 |
| Tue 09 | 0 | 0.0 | 71 ms | 0 |
| Tue 11 | 0 | 0.0 | 169 ms | 0 |
| Tue 14 | 0 | 0.0 | 72 ms | 0 |
| Tue 16 | 0 | 0.0 | 602 ms | 0 |
| Tue 18 | 0 | 0.0 | 99 ms | 0 |
| Tue 20 | 0 | 0.0 | 127 ms | 0 |
| Tue 23 | 0 | 0.0 | 725 ms | 0 |
| Wed 01 | 0 | 0.0 | 404 ms | 0 |
| Wed 03 | 0 | 0.0 | 253 ms | 0 |
| Wed 05 | 0 | 0.0 | 166 ms | 0 |
| Wed 08 | 0 | 0.0 | 78 ms | 0 |
| Wed 10 | 0 | 0.0 | 174 ms | 0 |
| Wed 12 | 0 | 0.0 | 2037 ms | 0 |
| Wed 13 | 0 | 0.0 | 399 ms | 0 |
| Wed 15 | 0 | 0.0 | 330 ms | 0 |
| Wed 17 | 0 | 0.0 | 395 ms | 0 |
| Wed 19 | 0 | 0.0 | 368 ms | 0 |
| Wed 22 | 0 | 0.0 | 139 ms | 0 |
| Thu 00 | 0 | 0.0 | 95 ms | 0 |
| Thu 02 | 0 | 0.0 | 234 ms | 0 |
| Thu 04 | 0 | 0.0 | 194 ms | 0 |
| Thu 06 | 0 | 0.0 | 191 ms | 0 |
| Thu 08 | 0 | 0.0 | 211 ms | 0 |
| Thu 10 | 0 | 0.0 | 113 ms | 0 |
| Thu 12 | 0 | 0.0 | 98 ms | 0 |
| Thu 14 | 0 | 0.0 | 78 ms | 0 |
| Thu 16 | 0 | 0.0 | 335 ms | 0 |
| Thu 18 | 0 | 0.0 | 102 ms | 0 |
| Thu 21 | 0 | 0.0 | 216 ms | 0 |
| Thu 23 | 0 | 0.0 | 220 ms | 0 |
| Fri 00 | 0 | 0.0 | 212 ms | 0 |
| Fri 02 | 0 | 0.0 | 92 ms | 0 |
| Fri 04 | 0 | 0.0 | 104 ms | 0 |
| Fri 06 | 0 | 0.0 | 196 ms | 0 |
| Fri 07 | 0 | 0.0 | 230 ms | 0 |
| Fri 09 | 0 | 0.0 | 94 ms | 0 |
| Fri 11 | 0 | 0.0 | 349 ms | 0 |
| Fri 13 | 0 | 0.0 | 57 ms | 0 |
| Fri 15 | 0 | 0.0 | 41 ms | 0 |
| Fri 17 | 0 | 0.0 | 196 ms | 0 |
| Fri 19 | 0 | 0.0 | 112 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live GRIDSERVE badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for GRIDSERVE yet. Outages of 10 minutes or more get their own page here.
Having trouble with GRIDSERVE?
One report per service every 10 minutes from this network. No account.
Follow GRIDSERVE
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.
About GRIDSERVE
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: 158 ms average, 41–349 ms range across 14 successful checks.
Questions
Is GRIDSERVE down right now?
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
When was GRIDSERVE last down?
We have not recorded a public GRIDSERVE incident since monitoring began 6 days ago.
What is GRIDSERVE's uptime?
From our own checks: 100% over 6 days of checks.
How fast does GRIDSERVE respond?
158 ms on average over the last 24 hours (41–349 ms).
Does GRIDSERVE have an official status page?
Yes, at https://status.gridserve.com.
GRIDSERVE not working for me but the status is fine. What now?
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.