Visual Inconsistency on Container Job Displayed Status
Monitoring - We identified the issue and created a fix for this.
We will continue to monitor the results.
Jul 15, 2026 - 12:57 CEST
Identified - We have identified visual inconsistencies on Container Job run statuses on Nexaa.
While the inconsistency is only visual, it can create confusion onto whether your container jobs got executed on their configured cron schedule. We advice you to follow your Monitoring Dashboard to confirm the run status of your container job and we are working on aligning the correct status to our API.
Jul 10, 2026 - 11:18 CEST
Uptime over the past 90 days. View historical uptime.
Data Center Operational
90 days ago
100.0 % uptime
Today
Amsterdam Operational
90 days ago
100.0 % uptime
Today
Haarlem Operational
90 days ago
100.0 % uptime
Today
Services Operational
90 days ago
100.0 % uptime
Today
API Operational
MyTilaa Operational
Networking Operational
NFS Operational
90 days ago
100.0 % uptime
Today
Nexaa Operational
90 days ago
100.0 % uptime
Today
Support Center Operational
WWW Operational
Big Disk Operational
90 days ago
100.0 % uptime
Today
Backup service Operational
90 days ago
100.0 % uptime
Today
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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Network Maintenance Jul 16, 2026 21:00 - Jul 17, 2026 00:00 CEST

We will be performing network-related maintenance on our infrastructure. This maintenance is a necessary step in the preparation and deployment of our new network infrastructure.

While we do not expect a full service outage, please be aware that periods of packet loss are expected during the maintenance window. Our team will be closely monitoring the network to minimize impact and ensure stability.

If you encounter persistent issues after the maintenance window, please contact support at support@tilaa.com.
Posted on Jul 09, 2026 - 15:38 CEST
Jul 15, 2026

Unresolved incident: Visual Inconsistency on Container Job Displayed Status.

Jul 14, 2026
Network issues
Resolved - The AMS-IX links have been closely monitored for an extensive period of time now, and are stable. A post-mortem of this incident will be shared as soon as possible.
Jul 14, 14:31 CEST
Monitoring - Together with AMS-IX and Iron Mountain engineers, we have identified and resolved the issue. Traffic levels are now back to nominal. We will continue to monitor the links closely, and will keep you updated.
Jul 7, 22:24 CEST
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 7, 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 6, 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 5, 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 5, 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 5, 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 5, 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 5, 09:17 CEST
Investigating - We are currently investigating an issue with AMS-IX BGP sessions
Jul 5, 08:59 CEST
Jul 13, 2026

No incidents reported.

Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026
Jul 9, 2026

No incidents reported.

Jul 8, 2026
Nexaa.io Maintenance
Completed - The scheduled maintenance has been completed.
Jul 8, 06:00 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 6, 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 2, 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, 10:27 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 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.
May 12, 11:45 CEST
Jul 7, 2026
Emergency Network Maintenance
Completed - The maintenance has concluded successfully. We will continue to monitor our network components.
Jul 7, 21:45 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 7, 21:00 CEST
Scheduled - 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.
Jul 7, 10:47 CEST
Jul 6, 2026
Jul 5, 2026
Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026
Jul 1, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage