Resolved -
This incident has been resolved.
Jul 9, 23:02 GMT+04:00
Identified -
Current Status: In Progress Start Time: Today, July 9, 2025, 04:00 GST (Asia/Dubai) Estimated Completion: Today, July 9, 2025, 23:00 GST (Asia/Dubai)
What’s Happening We are migrating our DNS backend to a new, more robust provider. This upgrade will improve performance, security, and reliability for all AEserver customers.
What’s Unaffected
New domain name registrations will continue without interruption.
Impacted Services for Existing Customers:
Domain Transfers
Domain Renewals
Nameserver Updates
DNS Management when using dns1.aeserver.com, dns2.aeserver.com, dns3.aeserver.com
Reseller API DNS-related endpoints
During the migration window, you may experience delays or temporary errors when trying to perform any of the above operations.
Our Apologies We apologize for any hassle this may cause. Our team is working diligently to complete the migration as quickly as possible while ensuring a smooth transition.
Thank you for your patience and understanding. If you have any urgent concerns, please contact our support team at support@aeserver.com or via live chat.
Jul 9, 09:17 GMT+04:00
Resolved -
This incident has been resolved.
Jul 5, 03:55 GMT+04:00
Update -
We are continuing to monitor for any further issues.
Jul 5, 03:54 GMT+04:00
Monitoring -
A fix has been implemented and we are watching the effect on the DNS system.
Jul 4, 22:03 GMT+04:00
Identified -
DNS Management Partial Outage
Scope: DNS record updates and saves for domains using our internal name servers (dns1.aeserver.com, dns2.aeserver.com, dns3.aeserver.com) are currently failing.
Cause: Our backend DNS provider is experiencing service issues that prevent commit-through of new or modified records.
Impact:
Affected: Attempts to add, modify, or delete DNS records will not persist.
Unaffected: Existing DNS resolution continues to function normally.
Current Status: Provider is aware of the problem and actively working on a remediation.
Next Update: We’ll post another status update as soon as we have more information or the issue is resolved.
Jul 4, 11:51 GMT+04:00