Mailgun: Logs and Events API
Timeline of updates
- resolved
Earlier today, a poorly formed search query was executed against one of our Elasticsearch clusters containing customer event logs. This query consumed all available search queues across the cluster and after numerous attempts, we were unable to terminate the queries while the cluster was online. As a result, we performed a rolling restart of the cluster, which resulted in a rebalance of the nodes. Once the rebalancing was completed, we re-enabled the events API and logs section of the control panel. To help mitigate future issues, we've deployed timeouts on queries that will help prevent long-running operations from compromising the performance of our search infrastructure.
From Mailgun’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.mailgun.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Mailgun, started 2017-07-14 17:27 UTC, resolved after 5.6 h, 1 update(s).
- Title
- Logs and Events API
- Vendor
- Mailgun
- Date
- URL
- https://rewindex.com/company/mailgun/incidents/dxfzynm1lm0v
Mailgun profileRecent Mailgun incidentsAll outages on July 14, 2017Mailgun in July 2017MarkdownJSON