subnet.im

187.84.44.0/23

MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERNAS53052

At a glance

Addresses

512

/23 block

Visibility

21%

17 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 28th July 2009

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: 4 observed paths to 187.84.44.0/23, fanning out from AS53052 toward the vantage points that see it. Each path is written out in full beneath the graph.AS53052MULTIVELOX SERVIC…OriginAS262355VSX NetworksAS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS58299Openfactory GmbH …AS41051Freetransit Proje…AS213151Christian Elsen
  1. Sao Paulo53052262355266213This path
  2. Singapore530526939132337This path
  3. Oregon, US53052693920130This path
  4. Amsterdam5305269395829941051213151This 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

21%

Seen by 17 of 80 full-feed vantage points

Seen by few vantage points

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
28th July 2009
Allocation block
187.84.32.0/20
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.

CoveringMore specific
Prefix hierarchy for 187.84.44.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.187.84.44.0/22AS53052187.84.44.0/23AS53052This prefix187.84.46.0/23AS53052187.84.44.0/24AS53052187.84.45.0/24AS53052

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 187.84.44.0/23
PrefixAddressesOriginVisibility
187.84.44.0/221kAS53052MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERN80/80

More specific announcements

Announcements contained within 187.84.44.0/23
PrefixAddressesOriginVisibility
187.84.44.0/24256AS53052MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERN17/80
187.84.45.0/24256AS53052MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERN17/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 187.84.44.0/23
PrefixAddressesOriginVisibility
187.84.46.0/23512AS53052MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERN17/80

History

  1. AS5305212th 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 187.84.44.0/23 in the calculator/23 reference

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