New No-IP Public Tunnels are Not Provisioned
Ongoing · last updateinvestigatingSep 1 · 03:50 UTC
We are currently investigating this issue.
Reported by No-IP on their status page.
checked Sep 11, 2026 4:24 PM UTC · No-IP's official status page
No-IP is up and running.
No-IP is currently operational with all systems functioning normally.
All components operational
Email only. No password. No card.
Be the first to know
Statusfield watches No-IP alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
No-IP incident history
7 reports published by No-IP in the last 30 days · 2 still open
When No-IP breaks, it is typically resolved in 3h 11m — median across 5 resolved incidents over 90 days.
September 1, 2026
August 31, 2026
Alternate port SMTP delivery problems
Last updateresolvedAug 31 · 23:04 UTC
The issue affecting Alternate Port SMTP has been resolved the queue backlog as normalized. All systems are operational.
Reported by No-IP on their status page.
August 27, 2026
No-IP Public Tunnels SSL Certificates Not Being Set Correctly
Last updateresolvedAug 27 · 17:27 UTC
This incident has been resolved.
Reported by No-IP on their status page.
August 17, 2026
Elevated errors on the Dynamic DNS update endpoint
Last updateresolvedAug 17 · 17:01 UTC
This incident has been resolved. The fix deployed for the elevated errors on our Dynamic DNS update endpoint (dynupdate.no-ip.com) has held, and update requests have returned to processing normally. We have confirmed full recovery and the endpoint is operating as expected.
Reported by No-IP on their status page.
Elevated errors on the Dynamic DNS update endpoint
Last updateResolvedAug 17 · 17:01 UTC
This incident has been resolved. The fix deployed for the elevated errors on our Dynamic DNS update endpoint (dynupdate.no-ip.com) has held, and update requests have returned to processing normally. We have confirmed full recovery and the endpoint is operating as expected.
Reported by No-IP on their status page.
August 16, 2026
Resolution issues affecting hopto.me hostnames
Last updateresolvedAug 27 · 15:25 UTC
This incident has been resolved.
Reported by No-IP on their status page.
Resolution issues affecting hopto.me hostnames
Ongoing · last updateMonitoringAug 17 · 19:24 UTC
We have restored the affected domains and DNS resolution is now recovering for hostnames on hopto.me and a few other .me domains impacted by this issue. Our team has confirmed that these domains are resolving again.If your hostname is still not resolving, this is expected to clear on its own shortly. Due to standard DNS caching (TTL) on the .me registry, it may take up to an hour for the change to fully propagate across all networks and providers.We are continuing to monitor resolution closely to confirm everything is fully back to normal. We apologize for the disruption and appreciate your patience.
Reported by No-IP on their status page.