Help! Directory Cache Not Clearing!

I am completely desperate and utterly frustrated. Our 'Country Codes Directory' web tool is stuck showing old data, and I just can't get the cache to clear, no matter what I try. I've been at this for hours and feel like I'm missing something incredibly obvious, or perhaps something incredibly obscure.

We're running a Laravel application with Redis for caching, Nginx as our web server, and Cloudflare for CDN. The problem is, while database updates are immediate and I can verify them directly, the frontend for our directory web tool continues to serve stale data for hours, sometimes even days, after updates. It's making our data look outdated and unreliable, which is a huge issue for a directory service.

Here’s what I’ve tried so far, all to no avail:

• Ran all the usual Laravel cache commands: php artisan cache:clear, view:clear, config:clear, and route:clear.
• Flushed Redis completely using redis-cli FLUSHALL directly on the server.
• Purged Cloudflare cache – everything, multiple times, using the 'Purge Everything' option.
• Restarted PHP-FPM and Nginx services after each attempt, just in case.
• Verified the database directly – the data is absolutely updated correctly there.
• Checked Nginx configurations meticulously for any unexpected caching directives that might be holding onto old responses.
• Tried incognito mode and different browsers on various devices – still the same stale data for our web tool.

The symptoms are always the same: our web tool serves old data. For example, if I update a country's ISO code or dialing code, the old one shows up. It's like a ghost in the machine! Here’s a dummy console output that illustrates what I'm seeing, where a cache hit returns outdated information:

// Simulated Redis/Laravel cache check for a country's ISO code after update
GET country:USA:iso_code
"US" (Expected: "USA")

// Simulated Nginx cache status for a request
X-Cache-Status: HIT

// Simulated Cloudflare cache status
CF-Cache-Status: HIT

What obscure caching layer am I possibly missing? Is there a common pitfall in multi-layered caching setups (Laravel, Redis, Nginx, Cloudflare) that causes this kind of persistent, stubborn stale data? How can I ensure immediate cache invalidation across all layers for this crucial directory web tool? This is severely impacting our user experience and data integrity.

Any insights, troubleshooting steps, or even wild guesses would be a lifesaver right now. Thanks in advance!