Maintenance
500 Error on api.taggrs.io
Resolved Apr 04, 2025 at 08:26am UTC
We’ve identified a malfunction in our TAGGRS Tracking Tags. On some sites, this may result in a 500 error. While this issue may affect the display of graphs in your TAGGRS dashboard, it does not impact tracking functionality.
Performance hardware upgrades
Resolved Apr 11, 2025 at 08:00pm UTC
We will be performing scheduled infrastructure upgrades to enhance the performance and reliability of our services. As part of this upgrade, we will be upgrading our CPUs for improved speed and efficiency.
During this time, some users may experience brief periods of downtime or reduced performance. We will work to keep any disruptions as short as possible and will monitor the system closely throughout the upgrade process.
Unexpected Network Maintenance
Resolved Apr 11, 2025 at 01:45pm UTC
Our dashboard is currently undergoing unexpected network maintenance. We're actively working on a fix and will update this page as soon as everything is back online. Please note that your tracking data is not affected by this issue.
Potential downtime for app.taggrs.io dashboard
Resolved Apr 15, 2025 at 10:30am UTC
We are in the process of scaling our server architecture. The dashboard may be unreachable for a few minutes because of this. This does not impact your tracking.
Belgium: Network issues
Resolved Apr 24, 2025 at 09:57am UTC
We've now resolved the incident. Thanks for your patience.
3 previous updates
Scheduled Maintenance
Resolved May 16, 2025 at 04:00pm UTC
On Friday, May 16, 2025, between 18:00 and 00:00 CEST (Amsterdam time), we will perform critical security patches and performance optimizations across our entire infrastructure. During this window, your tracking server may experience a brief interruption of up to 20 minutes.
No action is required on your part, services will resume automatically once maintenance is complete. We appreciate your patience and apologize for any inconvenience.
502 error on container
Resolved May 23, 2025 at 11:18am UTC
The issue has been resolved. The containers are now running again. The problem occurred following a server upgrade aimed at enhancing performance. Our load balancers were still directing traffic to the old servers instead of the new, upgraded ones. If there are any questions about this, feel free to reach out to support@taggrs.io
2 previous updates