No impact incident
namecom: Incident Root Cause Analysis: Oct 31, 2026 DNS Changes
Nov 3, 2026, 20:28 UTC
started
ongoing
not resolved yet
—
duration
Current status of namecom: Operational — live namecom status
Timeline
- Nov 3, 2026, 20:28 UTCmonitoringOn Oct 31, 2026 (UTC), unauthorized DNS changes were made to 15 customer domains. All changes were restored by Oct 31, 16:11 UTC, and system access for the account where the changes originated has been fully revoked. Read the full incident report here: https://drive.google.com/file/d/1hUsmik81BR5MlX-gDRvwA4OUUPsbvA58/view
- Nov 3, 2026, 20:30 UTCmonitoringWe are continuing to monitor for any further issues.
Updates as published by namecom (original).
Other services with incidents at the same time
- Zapier 21:03 UTC · Delayed or failed template recommendations and template setup
- GitHub 20:57 UTC · Incident with Git Operations
- SerpApi 20:45 UTC · [Google Search API] The "Site:" Operator is Ignored
- Sinch 20:40 UTC · Delivery Issue Colombia - Claro
- Kraken 20:39 UTC · Brazilian Real (BRL) PIX Funding Delays
- AdGuard 20:29 UTC · AdGuard DNS - no fresh query logs
- WiscNet 20:25 UTC · WiscNet - Multiple Site Outage - 11/03/2026
- ITS Network & Systems 20:21 UTC · Biomedical Sciences Building Network Connectivity Issues
- 3DSOutscale 20:15 UTC · Incident API / API Incident
- IPRoyal 20:12 UTC · Residential proxies and Residential API: partial outage
- Ohio University 20:09 UTC · Panopto Lecture Capture
- W. W. Norton & Company 20:02 UTC · Student time spent visualization error
- WatchGuard Technologies 20:00 UTC · 2026-11-03 - AMER - FireCloud connectivity disruption
- Qualys 19:51 UTC · US Platform 1: VM Scan Processing Delays (IM-12959)
- Buildkite 19:42 UTC · Elevated API error rates