User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Name.am 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 → name.am—
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 2 hr ago. Last stored result reached it in 365 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 |
|---|---|---|---|---|
| 10:30 | 0 | 0.0 | 273 ms | 0 |
| 12:30 | 0 | 0.0 | 286 ms | 0 |
| 14:30 | 0 | 0.0 | 419 ms | 0 |
| 16:45 | 0 | 0.0 | 420 ms | 0 |
| 18:45 | 0 | 0.0 | 391 ms | 0 |
| 20:45 | 0 | 0.0 | 322 ms | 0 |
| 21:30 | 0 | 0.0 | 339 ms | 0 |
| 23:15 | 0 | 0.0 | 771 ms | 0 |
| 01:30 | 0 | 0.0 | 349 ms | 0 |
| 03:30 | 0 | 0.0 | 221 ms | 0 |
| 05:30 | 0 | 0.0 | 292 ms | 0 |
| 07:45 | 0 | 0.0 | 365 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
1 / 1Outages · 30 / 90 days
24 h 5 minAverage 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 Name.am 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
Having trouble with Name.am?
One report per service every 10 minutes from this network. No account.
Follow Name.am
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.
About Name.am
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: 365 ms average, 169–771 ms range across 13 successful checks.
Questions
Is Name.am down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Name.am last down?
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.
What is Name.am's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Name.am respond?
365 ms on average over the last 24 hours (169–771 ms).
Does Name.am have an official status page?
Yes, at https://status.name.am.
Name.am 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 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.