No-IP Outage History
13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded No-IP Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 17, 2026 | SSL certificate errors on mail.noip.comThe renewed certificate has been deployed to all mail service ports. | 38 min | Resolved |
| Sep 18, 2026 | No-IP Windows Client Registration and Configuration FailsThis incident has been resolved. | 44 min | Resolved |
| Sep 1, 2026 | New No-IP Public Tunnels are Not ProvisionedWe are currently investigating this issue. | 14h 56m | Resolved |
| Aug 31, 2026 | Alternate port SMTP delivery problemsThe issue affecting Alternate Port SMTP has been resolved the queue backlog as normalized. All systems are operational. | 3h 41m | Resolved |
| Aug 27, 2026 | No-IP Public Tunnels SSL Certificates Not Being Set CorrectlyThis incident has been resolved. | 1h 56m | Resolved |
| Aug 17, 2026 | Elevated errors on the Dynamic DNS update endpointThis 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… | 1h 47m | Resolved |
| Aug 16, 2026 | Resolution issues affecting hopto.me hostnamesThis incident has been resolved. | 264h 34m | Resolved |
| Aug 6, 2026 | Webmail Login UnavailableThe POP3/IMAP Email service are stable and this incident has been resolved. | 3h 24m | Resolved |
| Jun 8, 2026 | Investigating Issues Affecting Website and Multiple ServicesThis incident has been resolved. | 3h 33m | Resolved |
| Apr 24, 2026 | Managed DNS – Delayed DNS Propagation Between Primary and Secondary ServersDNS updates are now propagating to secondary servers in real time. All systems are operating normally. | 2h 31m | Resolved |
| Apr 4, 2026 | Email Login IssuesThis incident has been resolved. | 5h 1m | Resolved |
| Mar 25, 2026 | Degraded Performance – Outbound API IntegrationsThis incident is resolved - all systems are operational. | 3h 27m | Resolved |
| Feb 25, 2026 | POP3/IMAP Webmail Login, Mail Client ConnectionThis incident has been resolved. | 1h 11m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next No-IP incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This No-IP Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before No-IP acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single No-IP outage in this window ran 11d, against a mean recovery of 23h 39m. If you depend on No-IP in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.