# Reth Glamsterdam Hive failures — source access blocked

The requested inventory could not be established. Both Hive listings and GitHub were inaccessible from this runtime. No listing or per-run result JSON was read, so the newest runs, client versions, individual failing tests, EIP assignments, failure messages, and changes between runs are unknown. This report does **not** establish that any suite passed or that any matching issue is absent.

## Source access evidence

Requests made during this attempt:

| Public URL attempted | Result |
|---|---|
| https://hive.ethpandaops.io/glamsterdam/listing.jsonl | HTTP 403; curl exit 22 |
| https://hive.ethpandaops.io/glamsterdam-quick/listing.jsonl | HTTP 403; curl exit 22; an earlier attempt also returned a sandbox network-address rejection |
| https://hive.ethpandaops.io | CONNECT tunnel HTTP 403; `x-proxy-error: blocked-by-allowlist`; curl exit 56 |
| https://github.com/paradigmxyz/reth/issues/27206 | CONNECT tunnel HTTP 403; `x-proxy-error: blocked-by-allowlist`; curl exit 56 |
| https://api.github.com/search/issues?q=repo%3Aparadigmxyz%2Freth+27206 | HTTP 403; curl exit 22 |

These are attempted sources, not successfully read pages. The API query submitted was `repo:paradigmxyz/reth 27206`; it returned no readable search results. No test-name or EIP queries could be derived because the test data could not be retrieved. No per-run JSON URLs could be discovered from the blocked listings.

## Suite tables

The counts below are **historical context supplied in the assignment**, not independently verified observations, and must not be interpreted as the newest available results. The assignment dates are reproduced without an inferred time or timezone. Each table records the missing data explicitly rather than inventing individual failures.

### eels/consume-engine

| Feed | Supplied historical date | Supplied failure count | Client version; failing test names; EIPs; failure excerpts | Two newest runs: appeared/disappeared |
|---|---|---:|---|---|
| glamsterdam | 2026-10-26 | 1,626 | Unknown: source inaccessible | Unknown |
| glamsterdam-quick | 2026-10-27 | 23 | Unknown: source inaccessible | Unknown |

### consume-enginex

| Feed | Supplied historical date | Supplied failure count | Client version; failing test names; EIPs; failure excerpts | Two newest runs: appeared/disappeared |
|---|---|---:|---|---|
| glamsterdam | 2026-10-26 | 3,094 | Unknown: source inaccessible | Unknown |
| glamsterdam-quick | 2026-10-27 | 23 | Unknown: source inaccessible | Unknown |

### consume-rlp

| Feed | Supplied historical date | Supplied failure count | Client version; failing test names; EIPs; failure excerpts | Two newest runs: appeared/disappeared |
|---|---|---:|---|---|
| glamsterdam | 2026-10-26 | 6 | Unknown: source inaccessible | Unknown |
| glamsterdam-quick | 2026-10-27 | 6 | Unknown: source inaccessible | Unknown |

### consume-wirex

| Feed | Supplied historical date | Supplied failure count | Client version; failing test names; EIPs; failure excerpts | Two newest runs: appeared/disappeared |
|---|---|---:|---|---|
| glamsterdam | Not supplied | Unknown | Unknown: source inaccessible | Unknown |
| glamsterdam-quick | 2026-10-27 | 4 | Unknown: source inaccessible | Unknown |

### eels/execute

| Feed | Run date | Failure count | Client version; failing test names; EIPs; failure excerpts | Two newest runs: appeared/disappeared |
|---|---|---|---|---|
| glamsterdam | Unknown | Unknown | Unknown: source inaccessible | Unknown |
| glamsterdam-quick | Unknown | Unknown | Unknown: source inaccessible | Unknown |

## EIP summary and issue matching

| EIP | Verified failure count | Matching issue/PR and state |
|---|---|---|
| Cannot determine without failing test names/paths | Unknown | Unchecked: source access failed; **not** a “not found” result |

The assignment identifies [Reth issue #27206](https://github.com/paradigmxyz/reth/issues/27206) as a performance report about hashing code three times in the BAL path. Its page and state could not be verified. That supplied description does not establish a match to any Hive failure, so it is not counted as one.

No appeared/disappeared comparison is possible: neither feed's two newest runs could be identified. The two feeds' supplied historical counts are not consecutive runs of one suite and cannot substitute for that comparison. Completing this research requires access to the public listings, their referenced result JSON, and public Reth issue/PR search. No requester-specific value is missing; the blocker is this runtime's network access.