User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
gridly.com · Cloud & developer
Is Gridly down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → gridly.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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 53 min ago. Last stored result reached it in 441 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 1489 ms | 0 |
| Mon 19 | 0 | 0.0 | 468 ms | 0 |
| Mon 21 | 0 | 0.0 | 396 ms | 0 |
| Mon 23 | 0 | 0.0 | 371 ms | 0 |
| Tue 01 | 0 | 0.0 | 448 ms | 0 |
| Tue 03 | 0 | 0.0 | 645 ms | 0 |
| Tue 05 | 0 | 0.0 | 315 ms | 0 |
| Tue 07 | 0 | 0.0 | 273 ms | 0 |
| Tue 09 | 0 | 0.0 | 365 ms | 0 |
| Tue 11 | 0 | 0.0 | 304 ms | 0 |
| Tue 14 | 0 | 0.0 | 340 ms | 0 |
| Tue 16 | 0 | 0.0 | 437 ms | 0 |
| Tue 18 | 0 | 0.0 | 167 ms | 0 |
| Tue 20 | 0 | 0.0 | 502 ms | 0 |
| Tue 23 | 0 | 0.0 | 1619 ms | 0 |
| Wed 01 | 0 | 0.0 | 337 ms | 0 |
| Wed 03 | 0 | 0.0 | 687 ms | 0 |
| Wed 05 | 0 | 0.0 | 453 ms | 0 |
| Wed 08 | 0 | 0.0 | 1747 ms | 0 |
| Wed 10 | 0 | 0.0 | 816 ms | 0 |
| Wed 12 | 0 | 0.0 | 288 ms | 0 |
| Wed 14 | 0 | 0.0 | 891 ms | 0 |
| Wed 16 | 0 | 0.0 | 389 ms | 0 |
| Wed 18 | 0 | 0.0 | 146 ms | 0 |
| Wed 21 | 0 | 0.0 | 326 ms | 0 |
| Wed 23 | 0 | 0.0 | 178 ms | 0 |
| Thu 01 | 0 | 0.0 | 190 ms | 0 |
| Thu 03 | 0 | 0.0 | 267 ms | 0 |
| Thu 05 | 0 | 0.0 | 179 ms | 0 |
| Thu 07 | 0 | 0.0 | 1081 ms | 0 |
| Thu 09 | 0 | 0.0 | 263 ms | 0 |
| Thu 11 | 0 | 0.0 | 1334 ms | 0 |
| Thu 13 | 0 | 0.0 | 443 ms | 0 |
| Thu 15 | 0 | 0.0 | 377 ms | 0 |
| Thu 17 | 0 | 0.0 | 220 ms | 0 |
| Thu 20 | 0 | 0.0 | 225 ms | 0 |
| Thu 22 | 0 | 0.0 | 996 ms | 0 |
| Fri 00 | 0 | 0.0 | 232 ms | 0 |
| Fri 02 | 0 | 0.0 | 363 ms | 0 |
| Fri 04 | 0 | 0.0 | 1124 ms | 0 |
| Fri 06 | 0 | 0.0 | 988 ms | 0 |
| Fri 08 | 0 | 0.0 | 229 ms | 0 |
| Fri 10 | 0 | 0.0 | 358 ms | 0 |
| Fri 11 | 0 | 0.0 | 431 ms | 0 |
| Fri 12 | 0 | 0.0 | 1359 ms | 0 |
| Fri 14 | 0 | 0.0 | 198 ms | 0 |
| Fri 16 | 0 | 0.0 | 1121 ms | 0 |
| Fri 17 | 0 | 0.0 | 441 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Gridly 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 Gridly yet. Outages of 10 minutes or more get their own page here.
Having trouble with Gridly?
One report per service every 10 minutes from this network. No account.
Follow Gridly
Get an email when Gridly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Gridly alerts to Slack, Discord or a webhook — free.
About Gridly
Gridly is listed in our Cloud & developer category and checked at gridly.com. Manage content, translations, and tasks in one place. Eliminate manual work, cut down translation costs and translate faster with guaranteed quality.
Gridly publishes an official status page at status.gridly.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 620 ms average, 198–1359 ms range across 13 successful checks.
Questions
Is Gridly down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Gridly last down?
We have not recorded a public Gridly incident since monitoring began 8 days ago.
What is Gridly's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Gridly respond?
620 ms on average over the last 24 hours (198–1359 ms).
Does Gridly have an official status page?
Yes, at https://status.gridly.com.
Gridly 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 Gridly here at once, the problem is on Gridly'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 Gridly. 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.