User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Name.com 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.com—
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 30 min ago. Last stored result reached it in 19 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 |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 32 ms | 0 |
| Nov 7 | 0 | 0.0 | 20 ms | 0 |
| Nov 7 | 0 | 0.0 | 13 ms | 0 |
| Nov 7 | 0 | 0.0 | 22 ms | 0 |
| Nov 7 | 0 | 0.0 | 27 ms | 0 |
| Nov 8 | 0 | 0.0 | 33 ms | 0 |
| Nov 8 | 0 | 0.0 | 24 ms | 0 |
| Nov 8 | 0 | 0.0 | 47 ms | 0 |
| Nov 8 | 0 | 0.0 | 28 ms | 0 |
| Nov 9 | 0 | 0.0 | 39 ms | 0 |
| Nov 9 | 0 | 0.0 | 29 ms | 0 |
| Nov 9 | 0 | 0.0 | 34 ms | 0 |
| Nov 9 | 0 | 0.0 | 19 ms | 0 |
| Nov 10 | 0 | 0.0 | 34 ms | 0 |
| Nov 10 | 0 | 0.0 | 33 ms | 0 |
| Nov 10 | 0 | 0.0 | 31 ms | 0 |
| Nov 10 | 0 | 0.0 | 17 ms | 0 |
| Nov 11 | 0 | 0.0 | 24 ms | 0 |
| Nov 11 | 0 | 0.0 | 16 ms | 0 |
| Nov 11 | 0 | 0.0 | 18 ms | 0 |
| Nov 11 | 0 | 0.0 | 27 ms | 0 |
| Nov 12 | 0 | 0.0 | 49 ms | 0 |
| Nov 12 | 0 | 0.0 | 41 ms | 0 |
| Nov 12 | 0 | 0.0 | 65 ms | 0 |
| Nov 12 | 0 | 0.0 | 23 ms | 0 |
| Nov 13 | 0 | 0.0 | 26 ms | 0 |
| Nov 13 | 0 | 0.0 | 28 ms | 0 |
| Nov 13 | 0 | 0.0 | 21 ms | 0 |
| Nov 13 | 0 | 0.0 | 19 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average 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.com badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Verisign .com/.net Registry Maintenance
Environment: Production Impact: Domain availability checks, Registrations, Renewals, and Management: Unavailable WHOIS/RDAP: unavailable DNS: not impacted Affected TLDs: .COM/.NET
Announced by Name.com · sourceIdentity Digital Registry Maintenance
Environment: Production Impact: EPP (epp.identitydigital.services): Unavailable Registrar Portal (https://registrar.identitydigital.services/): Unavailable WHOIS (whois.identitydigital.services): Unavailable RDAP: Unavailable DNS: Not Impacted, domains will continue to resolve normally. Affected TLDs…
Announced by Name.com · sourceGoDaddy .CN & .TW Registry Maintenance
Environment: Production Impact: Domain availability checks, Registrations, Renewals, and Management: Unavailable WHOIS/RDAP: unavailable DNS: not impacted Affected TLDs: All .CN & .TW zones
Announced by Name.com · sourceDENIC Registry Maintenance
Environment: Production Impact: Domain availability checks, Registrations, Renewals, and Management: Unavailable WHOIS/RDAP: unavailable DNS: not impacted Affected TLDs: .DE
Announced by Name.com · sourcePublic Interest Registry Maintenance
Environment: Production Impact: Domain availability checks, Registrations, Renewals, and Management: Unavailable WHOIS/RDAP: unavailable DNS: not impacted Affected TLDs: ORG, NGO, ONG, Charity, Foundation, Giving
Announced by Name.com · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for Name.com yet. Outages of 10 minutes or more get their own page here.
Having trouble with Name.com?
One report per service every 10 minutes from this network. No account.
Follow Name.com
Get an email when Name.com goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Name.com alerts to Slack, Discord or a webhook — free.
About Name.com
We track Name.com (name.com) as part of the Cloud & developer group. name.com is your complete source for domain names, hosting and other online presence solutions.
Name.com publishes an official status page at status.name.com; 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. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 26 ms average, 13–60 ms range across 13 successful checks.
Questions
Is Name.com down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Name.com last down?
We have not recorded a public Name.com incident since monitoring began 8 days ago.
What is Name.com's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Name.com respond?
26 ms on average over the last 24 hours (13–60 ms).
Does Name.com have an official status page?
Yes, at https://status.name.com.
Name.com 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.com here at once, the problem is on Name.com'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.com. 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.