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 1 hr ago. Last stored result reached it in 51 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 95 ms | 0 |
| Tue 04 | 0 | 0.0 | 230 ms | 0 |
| Tue 06 | 0 | 0.0 | 83 ms | 0 |
| Tue 08 | 0 | 0.0 | 93 ms | 0 |
| Tue 10 | 0 | 0.0 | 137 ms | 0 |
| Tue 12 | 0 | 0.0 | 78 ms | 0 |
| Tue 15 | 0 | 0.0 | 117 ms | 0 |
| Tue 17 | 0 | 0.0 | 86 ms | 0 |
| Tue 19 | 0 | 0.0 | 293 ms | 0 |
| Tue 22 | 0 | 0.0 | 159 ms | 0 |
| Wed 00 | 0 | 0.0 | 276 ms | 0 |
| Wed 02 | 0 | 0.0 | 103 ms | 0 |
| Wed 04 | 0 | 0.0 | 267 ms | 0 |
| Wed 06 | 0 | 0.0 | 171 ms | 0 |
| Wed 09 | 0 | 0.0 | 1185 ms | 0 |
| Wed 11 | 0 | 0.0 | 113 ms | 0 |
| Wed 13 | 0 | 0.0 | 116 ms | 0 |
| Wed 15 | 0 | 0.0 | 286 ms | 0 |
| Wed 17 | 0 | 0.0 | 92 ms | 0 |
| Wed 20 | 0 | 0.0 | 147 ms | 0 |
| Wed 22 | 0 | 0.0 | 125 ms | 0 |
| Thu 00 | 0 | 0.0 | 227 ms | 0 |
| Thu 02 | 0 | 0.0 | 104 ms | 0 |
| Thu 04 | 0 | 0.0 | 112 ms | 0 |
| Thu 06 | 0 | 0.0 | 223 ms | 0 |
| Thu 08 | 0 | 0.0 | 246 ms | 0 |
| Thu 10 | 0 | 0.0 | 238 ms | 0 |
| Thu 12 | 0 | 0.0 | 54 ms | 0 |
| Thu 14 | 0 | 0.0 | 265 ms | 0 |
| Thu 16 | 0 | 0.0 | 127 ms | 0 |
| Thu 19 | 0 | 0.0 | 148 ms | 0 |
| Thu 21 | 0 | 0.0 | 190 ms | 0 |
| Thu 23 | 0 | 0.0 | 51 ms | 0 |
| Fri 01 | 0 | 0.0 | 179 ms | 0 |
| Fri 03 | 0 | 0.0 | 136 ms | 0 |
| Fri 05 | 0 | 0.0 | 156 ms | 0 |
| Fri 07 | 0 | 0.0 | 47 ms | 0 |
| Fri 09 | 0 | 0.0 | 113 ms | 0 |
| Fri 11 | 0 | 0.0 | 95 ms | 0 |
| Fri 13 | 0 | 0.0 | 72 ms | 0 |
| Fri 15 | 0 | 0.0 | 88 ms | 0 |
| Fri 17 | 0 | 0.0 | 267 ms | 0 |
| Fri 18 | 0 | 0.0 | 69 ms | 0 |
| Fri 19 | 0 | 0.0 | 111 ms | 0 |
| Fri 21 | 0 | 0.0 | 242 ms | 0 |
| Fri 23 | 0 | 0.0 | 84 ms | 0 |
| Sat 00 | 0 | 0.0 | 64 ms | 0 |
| Sat 02 | 0 | 0.0 | 51 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for nyris 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 nyris goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send nyris alerts to Slack, Discord or a webhook — free.
We track nyris (nyris.io) as part of the Cloud & developer group. Spare parts identification from photos, CAD data, text or barcodes. nyris visual search links results to your product catalog for teams and customers.
nyris publishes an official status page at status.nyris.io; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 114 ms average, 47–267 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public nyris incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
114 ms on average over the last 24 hours (47–267 ms).
Yes, at https://status.nyris.io.
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 nyris here at once, the problem is on nyris'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 nyris. 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.