Update - We will be performing emergency maintenance on our links to AMS-IX.
More information can be found here: https://status.tilaa.com/incidents/r1vdrvzj427s
Jul 07, 2026 - 10:51 CEST
More information can be found here: https://status.tilaa.com/incidents/r1vdrvzj427s
Jul 07, 2026 - 10:51 CEST
Update - Engineers from AMS-IX and Iron Mountain are actively checking and working on pinpointing the issue, which is caused by low levels of light received through the fiber connections. All active components have been verified to work correctly. As soon as we have further updates we will share this
Jul 06, 2026 - 15:51 CEST
Jul 06, 2026 - 15:51 CEST
Update - Engineers from Iron Mountain have succesfully verified the connections to our racks, and are currently following the physical path to AMS-IX.
Jul 05, 2026 - 15:07 CEST
Jul 05, 2026 - 15:07 CEST
Update - Our on-site engineers are currently working with both AMS-IX and the Iron Mountain data center to resolve this incident.
Jul 05, 2026 - 14:08 CEST
Jul 05, 2026 - 14:08 CEST
Update - AMX-IX has swapped our connection to their backup path, but still receive low light levels, even though we are sending sufficient light over the link. Since we determine the issue to be physical, our on-site engineers are currently working to resolve this matter.
Jul 05, 2026 - 12:47 CEST
Jul 05, 2026 - 12:47 CEST
Update - We're temporarily rerouting traffic away from AMS-IX to ensure stable operations, and we'll then further investigate the issue that we've been seeing.
Jul 05, 2026 - 09:32 CEST
Jul 05, 2026 - 09:32 CEST
Identified - We are seeing our BGP session with AMS-IX flapping. We're in touch with AMS-IX to resolve the issue, but until this is resolved you might experience intermittent packet loss. We apologise for any inconvenience, and assure you we're doing everything we can to resolve the issue as quickly as possible.
Jul 05, 2026 - 09:17 CEST
Jul 05, 2026 - 09:17 CEST
Investigating - We are currently investigating an issue with AMS-IX BGP sessions
Jul 05, 2026 - 08:59 CEST
Jul 05, 2026 - 08:59 CEST
Update - At Tuesday July 7th we will start updating the Kubernetes version of the Nexaa environment.
We don't expect any downtime during the upgrade. It might be updating or creating new containers will have a small hick-up but none is expected.
Jul 06, 2026 - 14:55 CEST
We don't expect any downtime during the upgrade. It might be updating or creating new containers will have a small hick-up but none is expected.
Jul 06, 2026 - 14:55 CEST
Update - On Thursday July 2nd in the afternoon (CEST) we will start changing to a container-optimized operating system on some database nodes on the production environment. We don't expect too much impact, except database-clusters with a single node will have a restart during these actions which causes the database-cluster being unavailable for a short amount of time. Multi-node clusters are being switched over so they will keep running.
Jul 02, 2026 - 10:30 CEST
Jul 02, 2026 - 10:30 CEST
Update - On Wednesday July 1st we will start changing to a container-optimized operating system on some nodes on the production environment. We don't expect too much impact, except containers will have a restart during these actions.
Jun 30, 2026 - 10:27 CEST
Jun 30, 2026 - 10:27 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 2026 - 06:00 CEST
Jun 24, 2026 - 06:00 CEST
Scheduled - To further enhance the performance and resilience of the nexaa.io platform, we have scheduled a significant modernization of our container infrastructure. This maintenance focuses on upgrading the core layers that power your containerized workloads.
Technical Objectives:
Host Platform Migration: Transitioning to a security-hardened, container-optimized operating system.
Network Fabric Optimization: Upgrading the internal container networking interface (CNI) for improved throughput and security.
Orchestration Engine Upgrade: Updating our cluster management layer to the latest stable version.
Edge Routing Transition: Implementing a more efficient ingress management system for improved traffic handling.
Expected Impact:
We have engineered this migration to be seamless.
We expect limited downtime, only restarts of containers, single-node databases and message queue-clusters
For the restart of containers make sure your registry credentials are valid, without this your container is unable to go back online after the restart.
Jun 24, 2026 06:00 - Jul 8, 2026 06:00 CEST
Technical Objectives:
Host Platform Migration: Transitioning to a security-hardened, container-optimized operating system.
Network Fabric Optimization: Upgrading the internal container networking interface (CNI) for improved throughput and security.
Orchestration Engine Upgrade: Updating our cluster management layer to the latest stable version.
Edge Routing Transition: Implementing a more efficient ingress management system for improved traffic handling.
Expected Impact:
We have engineered this migration to be seamless.
We expect limited downtime, only restarts of containers, single-node databases and message queue-clusters
For the restart of containers make sure your registry credentials are valid, without this your container is unable to go back online after the restart.
Jun 24, 2026 06:00 - Jul 8, 2026 06:00 CEST
Data Center
Operational
Amsterdam
Operational
Haarlem
Operational
Services
Degraded Performance
API
Operational
MyTilaa
Operational
Networking
Degraded Performance
NFS
Operational
Nexaa
Under Maintenance
Support Center
Operational
WWW
Operational
Big Disk
Operational
Backup service
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Emergency Network Maintenance Jul 7, 2026 21:00-22:00 CEST
In relation to https://status.tilaa.com/incidents/8y1qjc2dk4fg, our uplink to the AMS-IX (Amsterdam Internet Exchange) is currently down. Our network has automatically rerouted traffic through our other peering and transit partners. As a result, the direct impact on service availability is minimal, but our network’s redundancy has been temporarily reduced.
We are actively investigating the issue in collaboration with the technicians at AMS-IX and the data center. Although the cause of the outage may lie outside our own infrastructure, we have decided to proactively replace physical hardware on our end. This helps us completely rule out local factors and accelerate the further debugging process together with AMS-IX and the data center.
If you encounter persistent issues after the maintenance window, please contact support at support@tilaa.com.
Posted on Jul 07, 2026 - 10:47 CEST
We are actively investigating the issue in collaboration with the technicians at AMS-IX and the data center. Although the cause of the outage may lie outside our own infrastructure, we have decided to proactively replace physical hardware on our end. This helps us completely rule out local factors and accelerate the further debugging process together with AMS-IX and the data center.
If you encounter persistent issues after the maintenance window, please contact support at support@tilaa.com.
Posted on Jul 07, 2026 - 10:47 CEST