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 421 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 605 ms | 0 |
| Mon 23 | 0 | 0.0 | 525 ms | 0 |
| Tue 01 | 0 | 0.0 | 252 ms | 0 |
| Tue 03 | 0 | 0.0 | 290 ms | 0 |
| Tue 05 | 0 | 0.0 | 250 ms | 0 |
| Tue 08 | 0 | 0.0 | 390 ms | 0 |
| Tue 10 | 0 | 0.0 | 192 ms | 0 |
| Tue 12 | 0 | 0.0 | 224 ms | 0 |
| Tue 14 | 0 | 0.0 | 368 ms | 0 |
| Tue 16 | 0 | 0.0 | 430 ms | 0 |
| Tue 19 | 0 | 0.0 | 444 ms | 0 |
| Tue 21 | 0 | 0.0 | 232 ms | 0 |
| Tue 23 | 0 | 0.0 | 228 ms | 0 |
| Wed 01 | 0 | 0.0 | 401 ms | 0 |
| Wed 03 | 0 | 0.0 | 233 ms | 0 |
| Wed 06 | 0 | 0.0 | 376 ms | 0 |
| Wed 08 | 0 | 0.0 | 322 ms | 0 |
| Wed 10 | 0 | 0.0 | 208 ms | 0 |
| Wed 12 | 0 | 0.0 | 202 ms | 0 |
| Wed 15 | 0 | 0.0 | 440 ms | 0 |
| Wed 17 | 0 | 0.0 | 300 ms | 0 |
| Wed 19 | 0 | 0.0 | 417 ms | 0 |
| Wed 22 | 0 | 0.0 | 345 ms | 0 |
| Thu 00 | 0 | 0.0 | 278 ms | 0 |
| Thu 02 | 0 | 0.0 | 478 ms | 0 |
| Thu 04 | 0 | 0.0 | 463 ms | 0 |
| Thu 06 | 0 | 0.0 | 437 ms | 0 |
| Thu 08 | 0 | 0.0 | 213 ms | 0 |
| Thu 10 | 0 | 0.0 | 273 ms | 0 |
| Thu 12 | 0 | 0.0 | 286 ms | 0 |
| Thu 14 | 0 | 0.0 | 419 ms | 0 |
| Thu 16 | 0 | 0.0 | 420 ms | 0 |
| Thu 18 | 0 | 0.0 | 391 ms | 0 |
| Thu 20 | 0 | 0.0 | 322 ms | 0 |
| Thu 21 | 0 | 0.0 | 339 ms | 0 |
| Thu 23 | 0 | 0.0 | 771 ms | 0 |
| Fri 01 | 0 | 0.0 | 349 ms | 0 |
| Fri 03 | 0 | 0.0 | 221 ms | 0 |
| Fri 05 | 0 | 0.0 | 292 ms | 0 |
| Fri 07 | 0 | 0.0 | 365 ms | 0 |
| Fri 09 | 0 | 0.0 | 263 ms | 0 |
| Fri 11 | 0 | 0.0 | 393 ms | 0 |
| Fri 13 | 0 | 0.0 | 293 ms | 0 |
| Fri 15 | 0 | 0.0 | 236 ms | 0 |
| Fri 17 | 0 | 0.0 | 602 ms | 0 |
| Fri 19 | 0 | 0.0 | 638 ms | 0 |
| Fri 21 | 0 | 0.0 | 269 ms | 0 |
| Fri 23 | 0 | 0.0 | 393 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.
One report per service every 10 minutes from this network. No account.
Get an email when Name.am goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Name.am alerts to Slack, Discord or a webhook — free.
Name.am, at name.am, is one of the Cloud & developer services we monitor. The .AM Top-Level Domain Registry Gateway. AM domains for $16.74/year with free hosting, free SSL, free ID protection. PayPal and cards accepted.
Name.am publishes an official status page at status.name.am; 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 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 358 ms average, 169–638 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-07 and lasted 24 h 5 min. 1 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
358 ms on average over the last 24 hours (169–638 ms).
Yes, at https://status.name.am.
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 Name.am here at once, the problem is on Name.am'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 Name.am. 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.