SUBNET.IM

185.171.85.0/24

Eurofiber France SASAS200780

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCFR

Allocated 5th October 2016

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 185.171.85.0/24, fanning out from AS200780 toward the vantage points that see it. Each path is written out in full beneath the graph.AS200780Eurofiber France …OriginAS35625Eurofiber France …AS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam20078035625213151This path
  2. London, UK200780356258529This path
  3. Singapore20078035625132337This path
  4. Sao Paulo200780356253356266213This path
  5. Oregon, US20078035625693920130This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 80 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
France
Allocated
5th October 2016
Allocation block
185.171.84.0/22
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.171.85.0/24
PrefixAddressesOriginVisibility
185.171.84.0/24256AS200780Eurofiber France SAS80/80

History

  1. AS20078012th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 185.171.85.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.