Critical September 18, 2026 - Detected by Pingoru
- Sep 18, 2026, 02:50 PM UTC
- Resolved
- Sep 18, 2026, 03:34 PM UTC
- Duration
- 44m
Affected: No-IP Public Tunnels
Timeline · 2 updates
-
identified Sep 18, 2026, 02:50 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Sep 18, 2026, 03:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 03:50 AM UTC
- Resolved
- Sep 01, 2026, 06:52 PM UTC
- Duration
- 15h 2m
Affected: No-IP Public Tunnels
Timeline · 1 update
-
investigating Sep 01, 2026, 03:50 AM UTC
We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 07:23 PM UTC
- Resolved
- Aug 31, 2026, 11:04 PM UTC
- Duration
- 3h 41m
Affected: Alternate-port SMTP
Timeline · 3 updates
-
identified Aug 31, 2026, 07:23 PM UTC
We are seeing delivery problems on our alternate port SMTP service. The cause is a routing problem affecting part of the network our mail servers send from. Our team is working on a fix. We have a temporary reroute in place to keep traffic moving while we sort out the underlying problem. One known limitation: mail sent to a group address or through a forward may still bounce, depending on how the receiving side is configured. We will post an update here as soon as we know more.
-
monitoring Aug 31, 2026, 08:09 PM UTC
Connectivity has been restored. Alternate port SMTP mail that was delayed is now moving through the queue and being delivered. Expect queue delays for the next hour or so while the backlog processes. We will continue monitoring.
-
resolved Aug 31, 2026, 11:04 PM UTC
The issue affecting Alternate Port SMTP has been resolved the queue backlog as normalized. All systems are operational.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2026, 03:31 PM UTC
- Resolved
- Aug 27, 2026, 05:27 PM UTC
- Duration
- 1h 56m
Affected: No-IP Public Tunnels
Timeline · 3 updates
-
investigating Aug 27, 2026, 03:31 PM UTC
We are currently investigating this issue.
-
monitoring Aug 27, 2026, 04:35 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 27, 2026, 05:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 03:14 PM UTC
- Resolved
- Aug 17, 2026, 05:01 PM UTC
- Duration
- 1h 47m
Affected: Dynamic Update API
Timeline · 3 updates
-
investigating Aug 17, 2026, 03:14 PM UTC
We are investigating an issue affecting our Dynamic DNS update endpoint (dynupdate.no-ip.com). Some update requests are currently returning a 911 response, which may prevent affected hostnames from updating their IP address as expected. Our team is actively looking into the cause and working to restore normal update processing as quickly as possible. We apologize for the inconvenience and appreciate your patience. We will post further updates here as we learn more.
-
monitoring Aug 17, 2026, 04:17 PM UTC
We have deployed a fix for the elevated errors on our Dynamic DNS update endpoint (dynupdate.no-ip.com) and are beginning to see recovery, with update requests processing normally again. We are continuing to monitor the endpoint closely to confirm full recovery.
-
resolved Aug 17, 2026, 05:01 PM 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.
Read the full incident report →
- Detected by Pingoru
- Aug 16, 2026, 02:51 PM UTC
- Resolved
- Aug 27, 2026, 03:25 PM UTC
- Duration
- 11d
Affected: Free Dynamic DNSEnhanced Dynamic DNS
Timeline · 3 updates
-
investigating Aug 16, 2026, 02:51 PM UTC
We are currently investigating an issue affecting DNS resolution for hostnames on the hopto.me domain. Customers using hostnames on this domain may find that they are not resolving as expected. Our team is actively looking into the cause and working to restore normal resolution as quickly as possible. We understand how disruptive this is and apologize for the inconvenience. We will post further updates here as we learn more. Thank you for your patience.
-
monitoring Aug 17, 2026, 07:24 PM 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.
-
resolved Aug 27, 2026, 03:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2026, 01:48 PM UTC
- Resolved
- Aug 06, 2026, 05:12 PM UTC
- Duration
- 3h 24m
Affected: POP3 / IMAP Email
Timeline · 3 updates
-
investigating Aug 06, 2026, 01:48 PM UTC
Our third party provider is currently investigating a login issue with POP3/IMAP Email service. OpenSRS Status Page: https://www.opensrsstatus.com/
-
monitoring Aug 06, 2026, 02:30 PM UTC
A fix has been implemented, and service performance has improved. Our third party email provider will continue to closely monitor the environment to ensure stability.
-
resolved Aug 06, 2026, 05:12 PM UTC
The POP3/IMAP Email service are stable and this incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 12:29 PM UTC
- Resolved
- Jun 08, 2026, 04:03 PM UTC
- Duration
- 3h 33m
Affected: Account Management (my.noip.com)No-IP account signup and login
Timeline · 3 updates
-
investigating Jun 08, 2026, 12:29 PM UTC
We are currently investigating reports of issues affecting our database infrastructure. This may be impacting access to our website and multiple services. Our team is actively working to identify the root cause and assess the scope of the impact. We will provide additional updates as more information becomes available. We apologize for any inconvenience and appreciate your patience.
-
monitoring Jun 08, 2026, 02:07 PM UTC
The issue affecting the database has been mitigated, and services are currently recovering. We are seeing systems return to normal operation and continue to closely monitor performance and stability across affected services. Our team will remain engaged and monitor the environment to ensure recovery is sustained. We will provide additional updates as necessary. Thank you for your patience.
-
resolved Jun 08, 2026, 04:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 12:38 AM UTC
- Resolved
- Apr 24, 2026, 03:09 AM UTC
- Duration
- 2h 31m
Affected: Plus Managed DNS
Timeline · 3 updates
-
investigating Apr 24, 2026, 12:38 AM UTC
We are currently investigating an issue impacting Managed DNS zones where DNS updates are experiencing delays propagating from our primary DNS servers to our secondary DNS servers. During this time, recent DNS changes may not be reflected immediately across all authoritative servers, which could result in inconsistent DNS resolution depending on the querying resolver. Our engineering team is actively working to identify the root cause and restore normal propagation times. We will provide updates as more information becomes available.
-
monitoring Apr 24, 2026, 02:57 AM UTC
We have identified the root cause of the issue and implemented a fix. DNS update delays are now beginning to decrease as changes propagate through the system. We will continue to monitor performance closely and provide further updates as needed.
-
resolved Apr 24, 2026, 03:09 AM UTC
DNS updates are now propagating to secondary servers in real time. All systems are operating normally.
Read the full incident report →
- Detected by Pingoru
- Apr 04, 2026, 08:13 PM UTC
- Resolved
- Apr 05, 2026, 01:15 AM UTC
- Duration
- 5h 1m
Affected: POP3 / IMAP Email
Timeline · 2 updates
-
investigating Apr 04, 2026, 08:13 PM UTC
Our third party provider is currently investigating issues with logging in to email accounts via Webmail, IMAP and POP. OpenSRS Status Page: https://www.opensrsstatus.com/incidents/yh5tksft4d9w
-
resolved Apr 05, 2026, 01:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 02:45 PM UTC
- Resolved
- Mar 25, 2026, 06:12 PM UTC
- Duration
- 3h 27m
Affected: Domain RegistrationPOP3 / IMAP EmailMail ForwardingAlternate-port SMTPBackup MX / Mail ReflectorSSL CertificatesPayment Processing
Timeline · 3 updates
-
investigating Mar 25, 2026, 02:45 PM UTC
We are currently investigating an issue impacting outbound API integrations. Customers may experience delays or failures when interacting with external API-dependent services. Our team is actively working to identify the root cause and will provide updates as more information becomes available.
-
monitoring Mar 25, 2026, 02:57 PM UTC
The issue impacting outbound API integrations has been resolved. All systems are now operating normally. We will continue to monitor performance to ensure stability. Thank you for your patience while we worked to resolve this issue.
-
resolved Mar 25, 2026, 06:12 PM UTC
This incident is resolved - all systems are operational.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 04:25 PM UTC
- Resolved
- Feb 25, 2026, 05:37 PM UTC
- Duration
- 1h 11m
Affected: POP3 / IMAP Email
Timeline · 2 updates
-
investigating Feb 25, 2026, 04:25 PM UTC
Our third party provider is currently investigating an issues with POP3/IMAP email service. Users may experience errors when attempting to use Webmail as well as mail clients. OpenSRS Status Page: https://www.opensrsstatus.com/incidents/43q88wrjm19f
-
resolved Feb 25, 2026, 05:37 PM UTC
This incident has been resolved.
Read the full incident report →
Critical November 2, 2025 - Detected by Pingoru
- Nov 02, 2025, 03:46 PM UTC
- Resolved
- Nov 02, 2025, 04:51 PM UTC
- Duration
- 1h 5m
Affected: WebsiteAccount Management (my.noip.com)
Timeline · 3 updates
-
investigating Nov 02, 2025, 03:46 PM UTC
We are currently investigating the issue. Mail, DNS Resolution and Dynamic Updates appear to be working correctly during this time.
-
monitoring Nov 02, 2025, 04:08 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 02, 2025, 04:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 08:09 PM UTC
- Resolved
- Aug 19, 2025, 08:27 PM UTC
- Duration
- 17m
Affected: POP3 / IMAP Email
Timeline · 2 updates
-
investigating Aug 19, 2025, 08:09 PM UTC
Our third party provider is currently investigating an issues with POP3/IMAP Email service webmail unable to login. IMAP and POP services are unaffected. OpenSRS Status Page: https://www.opensrsstatus.com/incidents/bjdb832g1786
-
resolved Aug 19, 2025, 08:27 PM UTC
Webmail is now working correctly.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 11:35 PM UTC
- Resolved
- Jun 19, 2025, 12:25 AM UTC
- Duration
- 49m
Affected: Account Management (my.noip.com)No-IP account signup and login
Timeline · 2 updates
-
identified Jun 18, 2025, 11:35 PM UTC
We are currently experiencing an issue with our logging infrastructure that is causing degraded performance and intermittent errors across our website and the my.noip.com web application. Our engineering team is actively investigating the root cause and working to restore full functionality.
-
resolved Jun 19, 2025, 12:25 AM UTC
We have the issue resolved and do not expect further problems.
Read the full incident report →
- Detected by Pingoru
- Apr 18, 2025, 05:30 AM UTC
- Resolved
- Apr 18, 2025, 05:31 AM UTC
- Duration
- 1m
Timeline · 2 updates
-
monitoring Apr 18, 2025, 05:30 AM UTC
Earlier today, we experienced a brief interruption in DNS resolution due to an unexpected issue following a configuration update. The update caused our name servers to temporarily become unresponsive, leading to a roughly 10-minute window where DNS queries may have failed to resolve. DNS cashing may have caused longer resolution failures in some cases. Our engineering team quickly identified the issue and restored full functionality.
-
resolved Apr 18, 2025, 05:31 AM UTC
We have resolved the DNS resolution disruption and are working on additional safeguards to prevent similar occurrences in the future. We sincerely apologize for any disruption this may have caused and appreciate your patience as we worked to resolve it.
Read the full incident report →
- Detected by Pingoru
- Dec 20, 2024, 03:26 PM UTC
- Resolved
- Dec 20, 2024, 06:34 PM UTC
- Duration
- 3h 7m
Affected: Free Dynamic DNSEnhanced Dynamic DNSPlus Managed DNSDynamic Update API
Timeline · 3 updates
-
identified Dec 20, 2024, 03:26 PM UTC
We are currently investigating reports of delays processing updates to DNS records or creating new records in a subset of applications. We have identified the caused and working on processing the backlog of updates in queue. DNS is continuing to resolve.
-
monitoring Dec 20, 2024, 03:41 PM UTC
We have mitigated the issue and our update queue has processed all backlogged updates and we will continue to monitor the recovery.
-
resolved Dec 20, 2024, 06:34 PM UTC
This incident is resolved and all systems are operational.
Read the full incident report →
Critical September 26, 2024 - Detected by Pingoru
- Sep 26, 2024, 02:31 PM UTC
- Resolved
- Sep 26, 2024, 06:05 PM UTC
- Duration
- 3h 34m
Affected: WebsiteAccount Management (my.noip.com)Alternate-port SMTPBackup MX / Mail ReflectorMonitoringPayment ProcessingSupport (noip.com/support)
Timeline · 4 updates
-
investigating Sep 26, 2024, 02:31 PM UTC
We are currently investing reports of 500 errors being thrown when attempting to purchase services in the No-IP checkout flow.
-
investigating Sep 26, 2024, 03:12 PM UTC
We are continuing to investigate the issues that are affecting No-IP services. At this time Dynamic DNS and DNS resolution is not affected.
-
monitoring Sep 26, 2024, 03:21 PM UTC
We have identified the cause to be related to an outage with one of our ISPs in our data center. We have re routed traffic and have observed recovery throughout the affected properties and services. We will continue to monitor over the next couple hours.
-
resolved Sep 26, 2024, 06:05 PM UTC
This incident is resolved. All systems are operational.
Read the full incident report →