User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
netomi.com · 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 50 min ago. Last stored result reached it in 179 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 93 ms | 0 |
| Mon 23 | 0 | 0.0 | 170 ms | 0 |
| Tue 01 | 0 | 0.0 | 74 ms | 0 |
| Tue 03 | 0 | 0.0 | 98 ms | 0 |
| Tue 05 | 0 | 0.0 | 307 ms | 0 |
| Tue 08 | 0 | 0.0 | 78 ms | 0 |
| Tue 10 | 0 | 0.0 | 146 ms | 0 |
| Tue 12 | 0 | 0.0 | 227 ms | 0 |
| Tue 14 | 0 | 0.0 | 145 ms | 0 |
| Tue 16 | 0 | 0.0 | 241 ms | 0 |
| Tue 19 | 0 | 0.0 | 83 ms | 0 |
| Tue 21 | 0 | 0.0 | 109 ms | 0 |
| Tue 23 | 0 | 0.0 | 135 ms | 0 |
| Wed 01 | 0 | 0.0 | 106 ms | 0 |
| Wed 04 | 0 | 0.0 | 251 ms | 0 |
| Wed 06 | 0 | 0.0 | 183 ms | 0 |
| Wed 08 | 0 | 0.0 | 232 ms | 0 |
| Wed 10 | 0 | 0.0 | 128 ms | 0 |
| Wed 12 | 0 | 0.0 | 130 ms | 0 |
| Wed 15 | 0 | 0.0 | 292 ms | 0 |
| Wed 17 | 0 | 0.0 | 68 ms | 0 |
| Wed 19 | 0 | 0.0 | 213 ms | 0 |
| Wed 21 | 0 | 0.0 | 236 ms | 0 |
| Wed 23 | 0 | 0.0 | 158 ms | 0 |
| Thu 01 | 0 | 0.0 | 240 ms | 0 |
| Thu 03 | 0 | 0.0 | 183 ms | 0 |
| Thu 05 | 0 | 0.0 | 84 ms | 0 |
| Thu 08 | 0 | 0.0 | 102 ms | 0 |
| Thu 10 | 0 | 0.0 | 180 ms | 0 |
| Thu 12 | 0 | 0.0 | 160 ms | 0 |
| Thu 14 | 0 | 0.0 | 180 ms | 0 |
| Thu 16 | 0 | 0.0 | 127 ms | 0 |
| Thu 18 | 0 | 0.0 | 138 ms | 0 |
| Thu 20 | 0 | 0.0 | 194 ms | 0 |
| Thu 22 | 0 | 0.0 | 270 ms | 0 |
| Fri 00 | 0 | 0.0 | 179 ms | 0 |
| Fri 02 | 0 | 0.0 | 211 ms | 0 |
| Fri 04 | 0 | 0.0 | 69 ms | 0 |
| Fri 06 | 0 | 0.0 | 385 ms | 0 |
| Fri 08 | 0 | 0.0 | 219 ms | 0 |
| Fri 10 | 0 | 0.0 | 180 ms | 0 |
| Fri 11 | 0 | 0.0 | 93 ms | 0 |
| Fri 12 | 0 | 0.0 | 261 ms | 0 |
| Fri 14 | 0 | 0.0 | 91 ms | 0 |
| Fri 16 | 0 | 0.0 | 258 ms | 0 |
| Fri 18 | 0 | 0.0 | 106 ms | 0 |
| Fri 19 | 0 | 0.0 | 216 ms | 0 |
| Fri 21 | 0 | 0.0 | 179 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 Netomi 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 Netomi goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Netomi alerts to Slack, Discord or a webhook — free.
Netomi is listed in our Cloud & developer category and checked at netomi.com. Netomi powers intelligent experiences for the world's most ambitious companies. New engagements are by referral.
Netomi publishes an official status page at status.netomi.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 188 ms average, 69–385 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Netomi incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
188 ms on average over the last 24 hours (69–385 ms).
Yes, at https://status.netomi.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 Netomi here at once, the problem is on Netomi'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 Netomi. 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.