Enter a guild name. Warcraft Insights reads its public logs and charts avoidable
mistakes pull by pull. No login required.
Private or unlisted logs? Connect Warcraft Logs
Mistakes
Run details
Display
Mistake analysis — Coming soon
We’re checking this boss’s mistake rules before publishing personal scores. Progression, phases and boss insights are still available.
Players on chart
Players
Compare mistakes per attended pull, alongside each player’s participation. Lower is fewer recorded mistakes; assignments and mechanic opportunities can differ.
Wrapped
Your guild. Every boss.
See where your Mythic guild stands, find the next wall, and understand your pulls. No login required.
complete kill logs
final-boss pulls — logged median
latest full week's median pulls per kill
Find your guild
Multiple raid teams?
Guilds with multiple teams: search the team name exactly as Warcraft Logs records it, for example "Little Hard Feelings", to view that team on its own.
This chart plots only guilds with public logs. Chinese (CN) realms are excluded because boosting makes their figures unreliable, so this set is smaller than the kill totals on the Tier Report. Guilds whose Warcraft Logs and Raider.io pull counts disagree are also excluded as likely inaccurate. To report an incorrect exclusion, flag it in the Discord.
View the chart as a table
Compare with another guild
Metric
Your guild
Compare guild
Phase progression
Progression Recap
Progression replay
Guild insights
Boss summary
Data help & Warcraft Logs connection
Season stats
Scout
Scout a character
A recruitment report built from public logs: parse percentiles, mechanical discipline, and reliability.
Directory
Recruitment prospects from analysed public logs, ranked by our recruitment rating.
Built from public logs and our own guild analyses. The rating favours clean play in lower-ranked guilds, so this is a list of raiders rated above their guild's rank rather than a ranking of absolute skill.
Rows marked ~ are provisional: bulk data covers only a raider's best final-boss kills, which produces a higher rating than the full report. Open the report for the median-based rating.
To be removed from this directory, contact blink01 on Discord.
About Warcraft Insights
What is Warcraft Insights?
Warcraft Insights reads public Warcraft Logs and reports raid hours, pull counts, progression pace, and a pull-by-pull breakdown of avoidable deaths by player. Any guild with public data can be analysed.
The data, and Warcraft Logs' limits
Hours, pulls, and mistake breakdowns come from public Warcraft Logs; rankings and the wider progression field come from Raider.io. Guilds that keep their logs private cannot be shown in log-based detail. Many of the strongest guilds do so, so these figures cover guilds with public logs and exclude much of the top of the rankings. Guild lookups are computationally expensive and rate-limited, so a first fetch can take several minutes and may take longer during busy periods. Results are cached, so repeat views are usually fast; a refresh or a changed analysis may require a new fetch.
Privacy and storage
No account or login is required. Requests necessarily expose your IP address to the hosting platform; the API uses it transiently for rate limits and does not add it to guild analysis records. First-party counters store only day-level totals for external referrer hostnames and Patreon click locations. Vercel Web Analytics supplies cookie-free page-view counts.
Guild, realm, player and report information comes from public Warcraft Logs and Raider.io. Shared fetch and insight caches may retain that public data for up to a year after their last update. This browser also keeps recent analyses, lookup preferences and optional goals in local browser storage for convenience; you can remove them by clearing site data in your browser.
Connecting Warcraft Logs stores that sign-in's tokens encrypted on the server, along with the connector's Warcraft Logs user name, until the guild disconnects or the grant is revoked at Warcraft Logs. The connecting browser holds a cookie that authorises managing the connection. Once a member includes unlisted or private reports, their raid data enters the same analysis records as public data; links to non-public reports are never shown. Guild rank is checked to gate private-log consent and is not displayed.
What's new
What's new
Aug 1 Guilds with private or unlisted logs are now supported: connect Warcraft Logs from a guild's Insights view, or paste unlisted report links. Private logs need officer consent.
Aug 1 Pull counts no longer double-count a pull recorded by two loggers whose clocks disagree. Completion records show each record holder's realm.
Jul 31 Longest Active Progressions on the tier report: the guilds with the most logged hours on the final boss and no kill yet, updated daily. Completion records: fastest and slowest progressions, fewest and most final-boss pulls.
Jul 30 A per-player mistakes table with sortable mechanic columns, cleanest raiders first, and shareable cards.
Jul 28 "Think this data is incorrect?" on every analysed guild queues a re-check when the site is idle.
Jul 13 Multi-boss analysis, team-aware guild lookup, clearer mobile navigation, and faster shared tier calculations.
Jul 6 Terminate, Light's End and enrage deaths no longer count as mistakes. Added a per-player "What killed you" breakdown.
Jul 6 Kill forecast, fatigue curve, player trajectories, and head-to-head comparison on the insights screen.
Jul 6 Tier report: "Cutting Edge Projection" against the last three tiers, "Kill Cost by Nerf Window", and "Category Leaders".
Jul 6 Fuzzy search on guild and realm lookup — "lhf" finds Little Hard Feelings.
Jul 5 Share links unfurl in Discord with live stat cards: guild pages, tier sections, Wrapped, and recap awards.
Jul 4 Data-accuracy warnings when a guild's public logs look incomplete. Draught of Rampant Abandon counts as a combat potion.
Jul 4 Multi-team guilds: statistics use the first team to kill, and team names are accepted in lookup.
Jul 4 Recap awards for healthstones, attendance, and battle resurrections. Estimated pull count shown while an analysis runs.
Jul 2 "CE by raid hours" distribution and the Omnium Folio power-gain marker on the tier report.
Jun The Tier Report, Wrapped, the recap awards, and the progress-hours chart the site began with.
A work in progress
Warcraft Insights is run for the raiding community, not as a business. The data has known inaccuracies. Report anything that looks incorrect in the Discord, where bugs, ideas, and feedback are collected. The Patreon link below helps cover the Warcraft Logs and hosting costs.
Thanks
Made by Blink, with help from Dario and Sam.
With thanks to the RLE Discord for the feedback and ideas that shaped the site, and to Lanfear, whose work heavily inspired the progress parse page.
Before you contribute
Warcraft Insights is a side project run for the raiding community, not a business. Contributions cover the Warcraft Logs subscription and hosting costs. The site remains free regardless. A fuller explanation is available on the Patreon page.
Each boss has a hand-built list of mechanics that players could have avoided. Only hits and deaths from that list count as mistakes.
What does not count
Logs do not record when a raid leader calls a wipe, so the end of a pull is estimated. On bosses with a known raid-ending mechanic, the first hit from it marks the pull as lost, and nothing after that counts. On other bosses, counting stops once several deaths accumulate. In both cases, deaths during a wipe are not counted as mistakes. Potions, healthstones, and combat potions are reported as usage statistics, not mistakes.
Role and repeat-hit rules
Tanks are exempt from mechanics they are expected to absorb. Repeated hits within a short window are counted once rather than individually.
Damage
The damage view uses unmitigated damage taken from those avoidable mechanics.
The lists are hand-built per boss and will not be perfect. Flag it in the Discord if a mechanic appears to be counted incorrectly.