User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 2 hr ago. Last stored result reached it in 407 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 320 ms | 0 |
| Nov 7 | 0 | 0.0 | 284 ms | 0 |
| Nov 7 | 0 | 0.0 | 118 ms | 0 |
| Nov 7 | 0 | 0.0 | 244 ms | 0 |
| Nov 8 | 0 | 0.0 | 281 ms | 0 |
| Nov 8 | 0 | 0.0 | 318 ms | 0 |
| Nov 8 | 0 | 0.0 | 316 ms | 0 |
| Nov 8 | 0 | 0.0 | 213 ms | 0 |
| Nov 9 | 0 | 0.0 | 442 ms | 0 |
| Nov 9 | 0 | 0.0 | 322 ms | 0 |
| Nov 9 | 0 | 0.0 | 323 ms | 0 |
| Nov 9 | 0 | 0.0 | 356 ms | 0 |
| Nov 10 | 0 | 0.0 | 394 ms | 0 |
| Nov 10 | 0 | 0.0 | 485 ms | 0 |
| Nov 10 | 0 | 0.0 | 289 ms | 0 |
| Nov 10 | 0 | 0.0 | 281 ms | 0 |
| Nov 11 | 0 | 0.0 | 206 ms | 0 |
| Nov 11 | 0 | 0.0 | 283 ms | 0 |
| Nov 11 | 0 | 0.0 | 344 ms | 0 |
| Nov 11 | 0 | 0.0 | 244 ms | 0 |
| Nov 12 | 0 | 0.0 | 353 ms | 0 |
| Nov 12 | 0 | 0.0 | 315 ms | 0 |
| Nov 12 | 0 | 0.0 | 197 ms | 0 |
| Nov 12 | 0 | 0.0 | 416 ms | 0 |
| Nov 13 | 0 | 0.0 | 266 ms | 0 |
| Nov 13 | 0 | 0.0 | 182 ms | 0 |
| Nov 13 | 0 | 0.0 | 351 ms | 0 |
| Nov 13 | 0 | 0.0 | 331 ms | 0 |
| Nov 14 | 0 | 0.0 | 249 ms | 0 |
| Nov 14 | 0 | 0.0 | 199 ms | 0 |
| Nov 14 | 0 | 0.0 | 318 ms | 0 |
| Nov 14 | 0 | 0.0 | 362 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for gno.land 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 gno.land goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
gno.land is listed in our Cloud & developer category and checked at gno.land. We're building Gno.land, set to become the leading open-source smart contract platform, using Gno, an interpreted and fully deterministic variation of the Go…
gno.land publishes an official status page at status.gno.land; 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: 305 ms average, 110–452 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public gno.land incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
305 ms on average over the last 24 hours (110–452 ms).
Yes, at https://status.gno.land.
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 gno.land here at once, the problem is on gno.land'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 gno.land. 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.