EBRD Ineligible Entities
Everything below is read from Verifex's live runtime state — read at 2026-09-02 22:59 UTC, cached briefly. It describes how this source is kept current and what Verifex has observed about it over time. It is not a copy of the source's contents, and it does not establish who is or is not on the list — that is determined per screening request.
Screening impact — None (operator-maintained)
Yes. Screening runs against the operator-maintained dataset (last verified 2026-05-17). This source is refreshed by operator rather than on an automated schedule; endpoint reachability does not change what is screened.
Current state
Three separate layers: how current the data is, whether the publisher's own endpoint is reachable by our probe, and the resulting impact on a screening decision. A publisher-endpoint issue does not by itself change screening.
- Data freshness
- Operator-maintained
- Operating mode
- Operator-refreshed
- Active records
- 1,081
- Last verified dataset
- 2026-05-17
- Dataset age
- 108 days
- Expected refresh
- monthly
- Publisher access
- Not measured
- Endpoint reachability (90d)
- Not probed yet
- Last automated probe
- Never
- Last observed source change
- Never
- Last run outcome
- Last run succeeded
- Median probe latency
- —
No reachability history has been recorded for this endpoint yet.
Data is active and searchable; automatic refresh requires operator configuration.
Publisher endpoint reachability
How often the publisher's own endpoint answered Verifex's automated probe over the last 90 days. This is not Verifex API or service uptime, and it does not by itself change a screening decision. Probes where the publisher blocks automated access (HTTP 403) are excluded from the percentage, not counted as downtime.
No reachability probe has been recorded for this source yet. History accrues going forward; it cannot be reconstructed for time before it was captured.
Ingestion history
Each row is one ingestion run: its outcome, the record count it produced, how many entries it added or removed versus the previous run, and how long it took.
| Started (UTC) | Outcome | Records | Added | Removed | Duration |
|---|---|---|---|---|---|
| 2026-05-17 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-16 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-15 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-14 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-13 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-12 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-11 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-10 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-09 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-08 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-07 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-06 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-05 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-04 18:40 UTC | Success | 0 | — | — | 0.0 s |
| 2026-05-03 18:40 UTC | Failed | 0 | — | — | 0.0 s |
| 2026-05-02 18:40 UTC | Failed | 0 | — | — | 0.0 s |
| 2026-05-02 10:02 UTC | Failed | 0 | — | — | 0.0 s |
| 2026-05-01 18:40 UTC | Failed | 0 | — | — | 0.0 s |
| 2026-05-01 17:09 UTC | Success | 1,081 | +18 | −23 | 2.7 s |
| 2026-05-01 16:31 UTC | Failed | 0 | — | — | 7.3 s |
| 2026-04-10 20:20 UTC | Failed | 0 | — | — | 7.5 s |
| 2026-04-08 18:40 UTC | Failed | 0 | — | — | 7.2 s |
| 2026-04-07 18:40 UTC | Failed | 0 | — | — | 7.7 s |
| 2026-04-06 17:11 UTC | Success | 1,086 | +1,086 | — | 2.2 s |
Detected content changes
Verifex stores a content hash of every distinct version it fetches. Each row below is a version whose bytes differed from the one before it — a change Verifex actually detected, with the record count and parser that read it.
No content version has been recorded for this source yet. History accrues going forward; it cannot be reconstructed for time before it was captured.
What this page does and does not establish
- It records what Verifex observed: whether the source answered, how current it is, how many records it held, and when its contents changed.
- It does not reproduce the source's list, assert the legal force of any listing, or state whether a particular person or entity appears on it. Those are answered per screening request and preserved in that request's evidence.
- A cadence is the publisher's rhythm, not a guarantee a refresh ran. Freshness that cannot be established is shown as unknown, and a count that could not be read is shown as unavailable — never as zero.
Source published by European Bank for Reconstruction and Development (EBRD) (official site). Verifex publishes reliability telemetry about this source, not its contents.