E05-IP: Yes
Rationale
RIPE NCC documents RIPE Atlas as an operational distributed measurement service begun in 2010, with users, deployed probes and published IP/ICMP results in its September 2015 account. The measurement-1001 public record begins in 2010 and remains marked Ongoing; retained 2026 anchor results show current IPv4 ICMP replies. This independently operated real-user IP service exceeds six months of operation; evidence is not inferred from software downloads.
Assessment method
Primary documentary evidence review; no new protocol execution
Source context
Evidence checked 2026-10-15; versions and hashes in round234-sources.json
Outstanding qualification
Credit operational IP/ICMP use, not the entirety of Atlas control/reporting protocols as part of the compared stack. No uninterrupted availability percentage, operator-by-operator certification, every optional profile feature or PRP-comparable performance is inferred. RIPE NCC is an external network measurement operator, not an internal PRP project. E05 uses the owner-approved adoption rule from revision 6.40. Deployment differences are disclosed rather than imported into the technical column. Independence is assessed from public operator attribution and role, not a private affiliation audit. No runtime, security, uptime or full-profile certification is implied.
Public sources
- https://www-static.ripe.net/static/rnd-ui/atlas/static/page/InternetProtocolJournal-18-3.pdf
- https://atlas.ripe.net/api/v2/measurements/1001/
- https://atlas.ripe.net/docs/faq/technical-details/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round234-atlas-results.json