Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Route host comparison ignores dns name case · case 01
Route host comparison ignores dns name case.
Route host comparison ignores dns name case · case 02
Route host comparison ignores dns name case.
Route host comparison ignores dns name case · case 03
Route host comparison ignores dns name case.
Route host comparison ignores dns name case · case 04
Route host comparison ignores dns name case.
Route host comparison ignores dns name case · case 05
Route host comparison ignores dns name case.
Wildcard host route covers subdomains but not apex · case 01
Wildcard host route covers subdomains but not apex.
Wildcard host route covers subdomains but not apex · case 02
Wildcard host route covers subdomains but not apex.
Wildcard host route covers subdomains but not apex · case 03
Wildcard host route covers subdomains but not apex.
Wildcard host route covers subdomains but not apex · case 04
Wildcard host route covers subdomains but not apex.
Wildcard host route covers subdomains but not apex · case 05
Wildcard host route covers subdomains but not apex.
Route method filter is applied before priority · case 01
Route method filter is applied before priority.
Route method filter is applied before priority · case 02
Route method filter is applied before priority.
Route method filter is applied before priority · case 03
Route method filter is applied before priority.
Route method filter is applied before priority · case 04
Route method filter is applied before priority.
Route method filter is applied before priority · case 05
Route method filter is applied before priority.
Route header constraint distinguishes existence from truthiness · case 01
Route header constraint distinguishes existence from truthiness.
Route header constraint distinguishes existence from truthiness · case 02
Route header constraint distinguishes existence from truthiness.
Route header constraint distinguishes existence from truthiness · case 03
Route header constraint distinguishes existence from truthiness.
Route header constraint distinguishes existence from truthiness · case 04
Route header constraint distinguishes existence from truthiness.
Route header constraint distinguishes existence from truthiness · case 05
Route header constraint distinguishes existence from truthiness.
Query route matches any repeated value · case 01
Query route matches any repeated value.
Query route matches any repeated value · case 02
Query route matches any repeated value.
Query route matches any repeated value · case 03
Query route matches any repeated value.
Query route matches any repeated value · case 04
Query route matches any repeated value.
Query route matches any repeated value · case 05
Query route matches any repeated value.
Weighted route selection uses cumulative half open buckets · case 01
Weighted route selection uses cumulative half open buckets.
Weighted route selection uses cumulative half open buckets · case 02
Weighted route selection uses cumulative half open buckets.
Weighted route selection uses cumulative half open buckets · case 03
Weighted route selection uses cumulative half open buckets.
Weighted route selection uses cumulative half open buckets · case 04
Weighted route selection uses cumulative half open buckets.
Weighted route selection uses cumulative half open buckets · case 05
Weighted route selection uses cumulative half open buckets.
Zero weight upstreams never receive traffic · case 01
Zero weight upstreams never receive traffic.
Zero weight upstreams never receive traffic · case 02
Zero weight upstreams never receive traffic.
Zero weight upstreams never receive traffic · case 03
Zero weight upstreams never receive traffic.
Zero weight upstreams never receive traffic · case 04
Zero weight upstreams never receive traffic.
Zero weight upstreams never receive traffic · case 05
Zero weight upstreams never receive traffic.
Least loaded route normalizes by capacity · case 01
Least loaded route normalizes by capacity.
Least loaded route normalizes by capacity · case 02
Least loaded route normalizes by capacity.
Least loaded route normalizes by capacity · case 03
Least loaded route normalizes by capacity.
Least loaded route normalizes by capacity · case 04
Least loaded route normalizes by capacity.
Least loaded route normalizes by capacity · case 05
Least loaded route normalizes by capacity.
Route failover excludes already attempted upstreams · case 01
Route failover excludes already attempted upstreams.
Route failover excludes already attempted upstreams · case 02
Route failover excludes already attempted upstreams.
Route failover excludes already attempted upstreams · case 03
Route failover excludes already attempted upstreams.
Route failover excludes already attempted upstreams · case 04
Route failover excludes already attempted upstreams.
Route failover excludes already attempted upstreams · case 05
Route failover excludes already attempted upstreams.
Failover stays within request replay budget · case 01
Failover stays within request replay budget.
Failover stays within request replay budget · case 02
Failover stays within request replay budget.
Failover stays within request replay budget · case 03
Failover stays within request replay budget.
Failover stays within request replay budget · case 04
Failover stays within request replay budget.
Failover stays within request replay budget · case 05
Failover stays within request replay budget.
Healthy endpoint filter retains draining endpoints only for existing flows · case 01
Healthy endpoint filter retains draining endpoints only for existing flows.
Healthy endpoint filter retains draining endpoints only for existing flows · case 02
Healthy endpoint filter retains draining endpoints only for existing flows.
Healthy endpoint filter retains draining endpoints only for existing flows · case 03
Healthy endpoint filter retains draining endpoints only for existing flows.
Healthy endpoint filter retains draining endpoints only for existing flows · case 04
Healthy endpoint filter retains draining endpoints only for existing flows.
Healthy endpoint filter retains draining endpoints only for existing flows · case 05
Healthy endpoint filter retains draining endpoints only for existing flows.
Route rewrite removes only the matched leading prefix · case 01
Route rewrite removes only the matched leading prefix.
Route rewrite removes only the matched leading prefix · case 02
Route rewrite removes only the matched leading prefix.
Route rewrite removes only the matched leading prefix · case 03
Route rewrite removes only the matched leading prefix.
Route rewrite removes only the matched leading prefix · case 04
Route rewrite removes only the matched leading prefix.
Route rewrite removes only the matched leading prefix · case 05
Route rewrite removes only the matched leading prefix.
Route rewrite adds exactly one path separator · case 01
Route rewrite adds exactly one path separator.
Route rewrite adds exactly one path separator · case 02
Route rewrite adds exactly one path separator.
Route rewrite adds exactly one path separator · case 03
Route rewrite adds exactly one path separator.
Route rewrite adds exactly one path separator · case 04
Route rewrite adds exactly one path separator.
Route rewrite adds exactly one path separator · case 05
Route rewrite adds exactly one path separator.
Route priority is secondary to match specificity · case 01
Route priority is secondary to match specificity.
Route priority is secondary to match specificity · case 02
Route priority is secondary to match specificity.
Route priority is secondary to match specificity · case 03
Route priority is secondary to match specificity.
Route priority is secondary to match specificity · case 04
Route priority is secondary to match specificity.
Route priority is secondary to match specificity · case 05
Route priority is secondary to match specificity.
Ipv4 network broadcast address is not allocated to host · case 01
Ipv4 network broadcast address is not allocated to host.
Ipv4 network broadcast address is not allocated to host · case 02
Ipv4 network broadcast address is not allocated to host.
Ipv4 network broadcast address is not allocated to host · case 03
Ipv4 network broadcast address is not allocated to host.
Ipv4 network broadcast address is not allocated to host · case 04
Ipv4 network broadcast address is not allocated to host.
Ipv4 network broadcast address is not allocated to host · case 05
Ipv4 network broadcast address is not allocated to host.
Link local destination requires interface scope · case 01
Link local destination requires interface scope.
Link local destination requires interface scope · case 02
Link local destination requires interface scope.
Link local destination requires interface scope · case 03
Link local destination requires interface scope.
Link local destination requires interface scope · case 04
Link local destination requires interface scope.
Link local destination requires interface scope · case 05
Link local destination requires interface scope.
Ipv4 and ipv6 endpoint identities remain distinct · case 01
Ipv4 and ipv6 endpoint identities remain distinct.
Ipv4 and ipv6 endpoint identities remain distinct · case 02
Ipv4 and ipv6 endpoint identities remain distinct.
Ipv4 and ipv6 endpoint identities remain distinct · case 03
Ipv4 and ipv6 endpoint identities remain distinct.
Ipv4 and ipv6 endpoint identities remain distinct · case 04
Ipv4 and ipv6 endpoint identities remain distinct.
Ipv4 and ipv6 endpoint identities remain distinct · case 05
Ipv4 and ipv6 endpoint identities remain distinct.
Ecmp selection uses flow identity not packet ordinal · case 01
Ecmp selection uses flow identity not packet ordinal.
Ecmp selection uses flow identity not packet ordinal · case 02
Ecmp selection uses flow identity not packet ordinal.
Ecmp selection uses flow identity not packet ordinal · case 03
Ecmp selection uses flow identity not packet ordinal.
Ecmp selection uses flow identity not packet ordinal · case 04
Ecmp selection uses flow identity not packet ordinal.
Ecmp selection uses flow identity not packet ordinal · case 05
Ecmp selection uses flow identity not packet ordinal.
Policy route fallback occurs only after no policy match · case 01
Policy route fallback occurs only after no policy match.
Policy route fallback occurs only after no policy match · case 02
Policy route fallback occurs only after no policy match.
Policy route fallback occurs only after no policy match · case 03
Policy route fallback occurs only after no policy match.
Policy route fallback occurs only after no policy match · case 04
Policy route fallback occurs only after no policy match.
Policy route fallback occurs only after no policy match · case 05
Policy route fallback occurs only after no policy match.
Route table refresh replaces removed routes · case 01
Route table refresh replaces removed routes.
Route table refresh replaces removed routes · case 02
Route table refresh replaces removed routes.
Route table refresh replaces removed routes · case 03
Route table refresh replaces removed routes.
Route table refresh replaces removed routes · case 04
Route table refresh replaces removed routes.
Route table refresh replaces removed routes · case 05
Route table refresh replaces removed routes.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗