Hi, I already discussed this with your AI support agent, who confirmed this needs a human investigation and recommended I open a proper ticket. Summary below:

Symptom: I run a Flask app receiving webhook POST requests from an external service (TradingView). The external service reports "Webhook delivery failed — couldn't find this domain" for 8-25% of delivery attempts (occasionally spiking to 70%+), starting ~Aug 24 10:30 UTC. Affects all my endpoints, specifically whenever many requests hit my app in the same second (I have ~10 external sources that can fire simultaneously).

What I've ruled out, with evidence:

App code bug — my app's own logs show 100% success (HTTP 200) on every request that arrives. Zero errors, crashes, or exceptions.

Domain-specific issue — generated a brand new Railway domain; identical failure rate appeared immediately on the new domain.

Server concurrency limits — updated my app to handle concurrent requests properly (confirmed via logs), failures continue identically.

Timing rules out a code regression — the failures started mid-way through a period with zero deployments. The same unchanged code ran with 0% failures for days, then suddenly started failing with no deploy happening.

Key evidence: Cross-referencing my app logs against the external service's delivery log, 82% of failed deliveries have zero trace anywhere in my app logs — the request appears to never reach my app at all.

Your AI agent suggested this could be either (a) a targeted edge/DNS issue affecting my domain's region under burst load, or (b) TradingView-side rate limiting misreported as "domain not found." I'm currently running a test with a minimal /health endpoint alongside my main webhooks to help narrow this down, and will share results once collected.

Project: smc-trading-bot

Domain: smc-trading-bot-production-8123.up.railway.app

Region: [провери во Settings, копирај го точно]

Could someone take a look at DNS/edge routing logs for my project around Aug 24 10:30 UTC onward?