I have Mailgun set up to handle incoming messages and route them to my webhook endpoint. This morning I tested by sending 7 messages total. Every single message reached my endpoint successfully and triggered my processing logic. However, when I check the Mailgun dashboard logs, here’s what I see: - Message 1: Shows Routed → Delivered → Stored status - Message 2: Shows Routed → Delivered → Stored status - Message 3: No log entries at all - Message 4: Only shows Routed status - Message 5: No log entries at all - Message 6: Shows Routed → Delivered status - Message 7: No log entries at all. I can confirm all messages were sent successfully since they appear in my email client’s sent folder and my webhook received each one. Has anyone experienced similar issues with missing or partial log entries in Mailgun? What could cause the logging system to miss certain messages while still processing them correctly?
This happens because Mailgun splits their routing and logging systems. The routing handles webhooks instantly, but logging runs separately and can break without affecting delivery. I’ve seen this hit lower-tier accounts hardest - their logging gets deprioritized when servers are busy. Those inconsistent statuses you’re seeing? Their event system is probably timing out or maxing out resources. Your webhooks work fine, but their dashboard becomes useless for compliance or debugging. I’d track events yourself by capturing webhook payloads directly instead of relying on their logs for anything important.
Yeah, this is a classic Mailgun architecture problem. Their event tracking runs separately from the actual delivery system, so things get out of sync constantly. I’ve dealt with this mess on multiple client projects. Here’s what happens: Mailgun delivers your emails fine and fires webhooks right away, but their event logging runs async and drops events all the time. That’s why you’re seeing weird status jumps - their logging microservices don’t talk to each other properly. After months of dealing with their broken audit trails, I just started capturing webhook events on our end instead. Every webhook that comes in gets logged immediately with timestamps, message IDs, and delivery status before we do anything else with it. Problem solved - we don’t rely on their dashboard anymore but still get complete delivery tracking for compliance.
Had the exact same issue six months ago. Turns out Mailgun’s event processing is delayed and their logging pipeline prioritizes differently than actual delivery. Your messages go through fine because routing and webhooks happen in real-time, but dashboard logging runs async and fails silently sometimes. Skip the dashboard - check the Events API directly. It’ll show stuff that never appears in the web interface. Messages sent during high traffic get logged even less reliably. Those partial status chains you’re seeing? Their logging microservices are dropping events between stages. No real fix from their end, but hitting their API programmatically gives way better visibility than the dashboard.
Yeah, Mailgun’s logging is pretty unreliable. I’ve dealt with this exact thing - their pipeline backs up or there’s some timing issue between routing and the dashboard API.
Sometimes the missing entries show up later, sometimes they don’t. Support just says it’s “normal behavior” which is super frustrating when you need accurate tracking.
I had this problem last year and built my own system instead. Created workflows that capture every email event and dump it into my own database rather than trusting Mailgun’s spotty logs.
My setup logs all webhook calls, tracks delivery status, and handles retries when their API is being slow. Now I can see everything without relying on their broken dashboard.
You can do this without coding too. Just set up workflows to catch webhook data and auto-log everything to a spreadsheet or database. Then you’ve got reliable tracking no matter what Mailgun shows you.
Mailgun’s logging is inconsistent because they run delivery and logging on separate pipelines. Webhooks fire instantly, but their event logging chokes under load or fails randomly.
I hit this same issue managing email flows. Missing logs killed our compliance tracking and made debugging delivery problems impossible.
I stopped fighting their broken dashboard and built automation to capture every webhook event when it hits our endpoint. It logs everything to our database, tracks delivery patterns, and handles retries when their API gets flaky.
Same setup monitors bounce rates, failed deliveries, and generates reports with complete data. No more guessing about missing messages or dealing with partial status chains.
You can do this without coding - just create workflows that catch webhook data and store everything in a database or spreadsheet. Then you’ve got reliable tracking no matter what their dashboard shows.
Same here, it’s infuriating. Mailgun’s dashboard is trash for tracking - I’ve had messages go through fine but see zero logs for weeks. Webhooks work perfectly, but their logging just dies randomly. I started capturing everything myself when webhooks fire and completely ignore their dashboard. Way more reliable than their busted logging.