SUBNET.IM

189.89.4.0/23

JUPITER PROVEDOR DE INTERNET LTDAAS28182

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 11th February 2008

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.89.4.0/23, fanning out from AS28182 toward the vantage points that see it. Each path is written out in full beneath the graph.AS28182JUPITER PROVEDOR …OriginAS28191Jupiter Telecomun…AS266213PLANETCLICK TELEC…AS137409GSL Networks Pty …AS8529Zain Omantel Inte…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS267613ELETRONET S.A.AS13786Seaborn (Seabras …AS174Cogent Communicat…AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. Sao Paulo2818228191266213This path
  2. London, UK28182281911374098529This path
  3. Singapore28182281916939132337This path
  4. Oregon, US2818228191693920130This path
  5. Amsterdam28182281912676131378617434549213151This 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

99%

Seen by 79 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
11th February 2008
Allocation block
189.89.0.0/20
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 189.89.4.0/23
ROA prefixAuthorised originMax length
189.89.4.0/23AS28182/23
189.89.0.0/20AS28182/20

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 189.89.4.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.189.89.0.0/20AS28182189.89.4.0/23AS28182This prefix189.89.6.0/23AS28182189.89.4.0/24AS28182189.89.5.0/24AS28182

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 189.89.4.0/23
PrefixAddressesOriginVisibility
189.89.0.0/204.1kAS28182JUPITER PROVEDOR DE INTERNET LTDA79/80

More specific announcements

Announcements contained within 189.89.4.0/23
PrefixAddressesOriginVisibility
189.89.4.0/24256AS28182JUPITER PROVEDOR DE INTERNET LTDA18/80
189.89.5.0/24256AS28182JUPITER PROVEDOR DE INTERNET LTDA18/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 189.89.4.0/23
PrefixAddressesOriginVisibility
189.89.6.0/23512AS28182JUPITER PROVEDOR DE INTERNET LTDA79/80

History

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

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