Incidents reported on status page for trakked.io https://status.trakked.io/ https://d1lppblt9t2x15.cloudfront.net/logos/7800034f93138e47a36d8ac61287461c.png https://status.trakked.io/ en https://status.trakked.io/incident/557310 Wed, 04 Jun 2025 12:13:00 -0000 https://status.trakked.io/incident/557310#2cae9d901cbf0b218b891a229215610ed8b3a5844c936726f03712b456c1ffec Unfortunately, there is no feedback from GitHub, but currently the problem seems to be fixed. https://status.trakked.io/incident/557310 Thu, 08 May 2025 07:24:00 -0000 https://status.trakked.io/incident/557310#765fb5430b9f202653ea4b24da692df721190624c4ff4b24b382436bf0f7c698 Unfortunately, there is no response from GitHub yet. There is a current discussion on GitHub where new users are complaining about the problem every day. https://github.com/orgs/community/discussions/157887 https://status.trakked.io/incident/557310 Tue, 06 May 2025 08:42:00 -0000 https://status.trakked.io/incident/557310#ea6c4b65d965629d3f8603202204184b02472f489e5e743a51f49343615cdae4 There are currently problems with updates when an installation is connected to a Git repository. The reason for this is a recent change to the rate limits by GitHub, which are now much stricter and prevent the commit. We assume that this is a temporary problem, as the behavior has already been reported by numerous GitHub users. There are many indications that the current restriction is due to an overly restrictive setting on the part of GitHub. We assume that GitHub will adjust the configuration in the near future and ask for a little patience until then. Workaround: To be able to continue to perform updates via trakked, we recommend temporarily disconnecting from the Git repository. https://status.trakked.io/incident/529580 Mon, 17 Mar 2025 18:38:00 -0000 https://status.trakked.io/incident/529580#ffcbdf3fec2a6ed03decfbc12f9641766d0e645f510a5c7db6cfd10cc1ddaca9 The problem has been fixed by UptimeRobot and all services are fully functional again https://status.trakked.io/incident/529580 Mon, 17 Mar 2025 12:02:00 -0000 https://status.trakked.io/incident/529580#9acf0b0aafb221f0abacf7eba09fdf00f3e249dbb6a333cfb0c7801944b2b817 There are currently problems with our service provider UptimeRobot. We are therefore currently not receiving any monitoring data. The remaining functions of trakked are not affected. https://status.trakked.io/incident/515389 Thu, 20 Feb 2025 06:23:00 -0000 https://status.trakked.io/incident/515389#3c1c8846053d0bd014e60d85427d94cc1ea1f77e10b4c87eca62c85bcdeee3a9 The problem has been fixed with Contao Manager 1.9.1 and everything is running as usual again. https://status.trakked.io/incident/515389 Wed, 19 Feb 2025 08:01:00 -0000 https://status.trakked.io/incident/515389#7117c8df062c8ded91c5550945363a52d03d8001c4a628ed96a8ee82c1a7c1ba After updating the Contao Manager to version 1.9, it is currently not possible to perform an update via trakked. We are already working on a solution. We apologize for the inconvenience. https://status.trakked.io/incident/472873 Wed, 11 Dec 2024 10:24:00 -0000 https://status.trakked.io/incident/472873#bbb5dc71aacfdc1ebb64aba0d9de683d1c5f28916a692ca2cefab7395f1d9d3b Uptime Robot has fixed the error. The monitoring works again as usual. https://status.trakked.io/incident/472873 Thu, 05 Dec 2024 12:50:00 -0000 https://status.trakked.io/incident/472873#25f4fea39ad47980c11f1c43796a1ccc845c1674ca0fc7ce8706275647e6d1be The UptimeRobot API is currently down which means the app is not able to display real-time information. We have been in touch multiple times with their support and they keep telling us that it should be working "very soon". Unfortunately, their own status page at status.uptimerobot.com does not represent the actual state of the API. The good news: Monitoring works and you will receive e-mails, just the visuals in the app are currently not working. https://status.trakked.io/incident/383750 Thu, 27 Jun 2024 06:45:00 -0000 https://status.trakked.io/incident/383750#07f593ab6f068f1f7f9b68bf056835a5bf934533f6ae8bbeeea246d18c907e3a We can confirm that SSL certificate expiration reminder e-mails are being sent again. The problem is resolved.