← Back to status overview
xYnta Status Page

All systems are operational.

Fixed

4 weeks ago —

The incident has been resolved, and we are now closing this notice.

Our network provider has just posted the following update:

A fix has been implemented. Last week, we migrated to new hardware. Sadly, this new hardware seems to have issues, so we have successfully reverted to the previous working state. We have tested this new set-up extensively, but only after taking it into production did it start to show issues. The previous hardware is stable, albeit a little outdated. We'll investigate the issue with the new hardware over the coming weeks and do even more testing before we attempt another migration.

Thank you for your understanding.

Watching

4 weeks ago —

Our network provider has just posted the following update:

We have implemented a workaround for the issues we've been seeing, and traffic should now be stable again. We're still working on a stable fix, and we will let you know once we know more.

Watching

4 weeks ago —

Our network provider has just posted the following update:

We have identified the root cause of the ongoing network latency. The issue is caused by a core network router experiencing connection instability (commonly referred to as “flapping”), which is resulting in intermittent slow response times and timeouts.

Our network engineers are actively working to stabilize the affected hardware and restore normal traffic flow. We will provide another update once a fix is being deployed or within the next 30 minutes. Thank you for your patience.

Watching

4 weeks ago —

Our network provider has now also reported latency issues on their status page. The problems persist, and we are continuing to monitor the situation closely.

Identified

4 weeks ago —

There appears to be a connectivity issue on the network where this nameserver is located. We are monitoring the situation closely. The primary nameserver is fully operational, so you should not experience any disruption.

4 weeks ago —

We are currently experiencing connectivity issues with our secondary nameserver. The issue is under investigation, and we will keep you updated on the progress.

Incident UUID adc34162-aa1a-45c4-976a-b3334b544f5e