SUBNET.IM

189.39.185.0/24

Link NetAS270792

University of DelawareAS2

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

69%

55 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 8th June 2020

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 189.39.185.0/24, fanning out from AS2, AS270792 toward the vantage points that see it. Each path is written out in full beneath the graph.AS270792Link NetOriginAS267347PEGASUS TELECOMAS11432Telium Telecomuni…AS266213PLANETCLICK TELEC…AS268824CONNECTMAX TELECOMAS266166GLOBALNET SERVICO…AS132337AxclusiveAS6057Administracion Na…AS213151Christian ElsenAS8529Zain Omantel Inte…AS2University of Del…OriginAS270792Link NetAS271023TERA SOLUCOESAS13786Seaborn (Seabras …AS6939Hurricane Electri…AS20130Depaul University
  1. Sao Paulo27079226734711432266213This path
  2. Singapore270792268824266166132337This path
  3. Amsterdam2707922688242661666057213151This path
  4. London, UK27079226882426616660578529This path
  5. Oregon, US227079227102313786693920130This 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

69%

Seen by 55 of 80 full-feed vantage points

Partially 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
8th June 2020
Allocation block
189.39.184.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 189.39.185.0/24
PrefixAddressesOriginVisibility
189.39.184.0/24256AS270792Link Net78/80

History

  1. AS212th August 2026 — present
  2. AS27079212th 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 189.39.185.0/24 in the calculator/24 reference

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