Any chance these issues broke the Tapatalk connectivity?
Quote from: meekGee on 03/18/2025 04:33 pmAny chance these issues broke the Tapatalk connectivity?Please use the following thread for discussing Tapatalk issues:https://forum.nasaspaceflight.com/index.php?topic=32811.0
Yeah, I think the disk is getting full. Mark will sort it. Happens about once a year, easy to solve once Mark picks up the message
It appears to be affecting image display, too: thumbnails are all fine, but full-size recently uploaded images will throw a "404 - Attachment Not Found" error until force-reloaded (CTRL+SHIFT+R) a few times, at which point the full sized image will load.
All reporting host error.The latest two, but its been occurring for about 10 minutes.Cloudflare Ray ID: 97dc0d842e7dc0b2Cloudflare Ray ID: 97dc0f512f52c0b2
Cloudflare Global Network experiencing issuesMonitoring - A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal.Nov 18, 2025 - 14:42 UTCUpdate - We've deployed a change which has restored dashboard services. We are still working to remediate broad application services impactNov 18, 2025 - 14:34 UTC[...]Update - We have made changes that have allowed Cloudflare Access and WARP to recover. Error levels for Access and WARP users have returned to pre-incident rates. We have re-enabled WARP access in London.We are continuing to work towards restoring other services.Nov 18, 2025 - 13:13 UTC[...]Identified - The issue has been identified and a fix is being implemented.Nov 18, 2025 - 13:09 UTC[...]Investigating - Cloudflare is experiencing an internal service degradation. Some services may be intermittently impacted. We are focused on restoring service. We will update as we are able to remediate. More updates to follow shortly.Nov 18, 2025 - 11:48 UTC
The issue was not caused, directly or indirectly, by a cyber attack or malicious activity of any kind. Instead, it was triggered by a change to one of our database systems' permissions which caused the database to output multiple entries into a “feature file” used by our Bot Management system. That feature file, in turn, doubled in size. The larger-than-expected feature file was then propagated to all the machines that make up our network.
Today has been grim so far. Hopefully now they've fixed it for good, but we'll see.