down
Is name.com down?
Check name.com availability, incident history, downtime reports, and website performance.
https://www.name.com ↗The official provider feed identifies an active incident or affected component.
Estimated down reports for name.com
Last 24 hoursNot enough activity data is available for this service yet.
Last collection attempt: 2026-10-21 11:27:52 UTC · Update temporarily delayed.
No user-submitted outage reports in the last 24 hours.
name.com outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
name.com website uptime and response time
Current website availability is unknown. No website checks available yet.
Unknown
Successful website checks (24h)
0 successful / 0 measurable checks
Unknown
Median response time
Unknown
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports service problems. The official provider feed identifies an active incident or affected component.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
name.com official status · fetched 2026-10-22 00:01:02 UTC
3 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| name.com Website | operational |
| name.com API | operational |
| name.com Registry Connections | operational |
Official incident timeline
Degraded Performance - .si Registry Connection · investigating · 2026-10-01T15:20:19.554Z
Product match: components.
Read the provider’s incident report
- · investigating
We are currently experiencing degraded performance for .si domain operations due to significant latency at the .si registry. Registration, renewal, transfer, and update requests for .si domains may take considerably longer than usual to complete, and some requests may time out. Other TLDs are not affected. We have contacted the .si registry and are actively monitoring the situation. We will post an update as soon as we have more information. We apologize for any inconvenience.
Service degradation (api.name.com, www.name.com) · resolved · 2026-07-24T13:09:03.544Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
Due to service provider issues, name.com started experiencing performance degradation at 4:57am MDT, affecting customers of api.name.com and www.name.com. Recovery started at 5:09 am MDT, with services fully restored at 5:12 am MDT. We are continuing to monitor activity until our service provider confirms the incident is fully resolved.
Identity Digital - Domain Create and Renewal Errors · resolved · 2026-07-11T20:21:14.497Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Between 1:01 PM and 1:19 PM MT (19:01–19:19 UTC), we were experiencing errors on registrations and renewals for TLDs operated by Identity Digital. The issue has been resolved, and registrations and renewals are now processing normally. We apologize for any inconvenience this may have caused.
DENIC DNS Disruption - DNSSEC outage .DE · resolved · 2026-05-06T00:07:23.943Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved. DENIC confirmed systems are operating normally again for .de domains, but are still investigating the cause of the temporary disruption. For a posted summary directly from DENIC, follow their status page here https://status.denic.de/.
- · investigating
DENIC is currently experiencing a disruption in its DNS service for .de domains. As a result, all DNSSEC-signed .de domains are currently affected in their reachability. The root cause of the disruption has not yet been fully identified by DENIC. DENIC’s technical teams are working intensively on analysis and on restoring stable operations as quickly as possible. Based on current information, users and operators of .de domains may experience impairments in domain resolution. Further updates wil
API outage · postmortem · 2026-05-08T15:29:44.944Z
Product match: components.
Read the provider’s incident report
- · postmortem
* **Duration:** 14:33 UTC – 16:09 UTC \(~96 minutes\) * **Impact:** The [api.name.com](http://api.name.com) endpoint was unreachable to external clients, resulting in socket timeouts and 502 errors. * **Root Cause Summary:** The outage was triggered by an unanticipated 50x surge in traffic to a specific, heavyweight API endpoint. This volume resulted in severe database resource saturation and row-lock contention on the shared writer database, preventing the API from processing requests. **Resol
- · resolved
This incident has been resolved.
- · monitoring
After further remediation, we are seeing recovery. We are still monitoring closely to ensure its sustained.
- · investigating
We're currently investigating the issue.
Website and API Outage · resolved · 2025-11-18T15:48:53.774Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
After an interruption to www.name.com and api.name.com, service was restored at approximately 2:22pm UTC. We are continuing to monitor to ensure continued stability.
.Space DNS resolution degraded · resolved · 2025-09-25T16:06:38.718Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
The registry operator for .space has encountered degraded DNS resolution on .space domains. We will update as soon as we receive another update from the .space registry with updates
Recovery tracker
The provider still reports an active problem.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: unknown. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of name.com.
No active incidents recorded.
- Elevated Error Rate for Durable Objects in Lisbon · investigating
- Incorrect geo location for some Cloudflare WARP users · identified
About name.com status on Iszdown
Check name.com availability, incident history, downtime reports, and website performance.
This page combines the available name.com report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
3 product-matched official components are listed above. No public website measurement is available in the current window.
Visit the official name.com website · Official provider status · How it works
What to check when name.com is not working
These are troubleshooting suggestions, not a list of currently reported problems.
name.com will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
name.com is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent name.com outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Degraded Performance - .si Registry Connection | No resolution recorded | investigating | |
| Identity Digital - Domain Create and Renewal Errors | 1 min | resolved | |
| DENIC DNS Disruption - DNSSEC outage .DE | 126 min | resolved | |
| API outage | 89 min | postmortem | |
| Website and API Outage | 1 min | resolved |
Frequently asked questions about name.com
Is name.com down right now?
Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-10-22T00:13:55.000Z.
How many name.com outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does name.com show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every name.com feature.
When was name.com status last updated?
The latest status observation was 2026-10-22T00:01:02.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has name.com had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow name.com or report a problem?
Use “Watch this service” to save name.com in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to name.com
Check a related product separately; its status can differ from name.com.