subnet.im

191.7.224.0/19

At a glance

Addresses

8,192

/19 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 11th March 2014

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 191.7.224.0/19, fanning out from AS263330 toward the vantage points that see it. Each path is written out in full beneath the graph.AS263330Fundação Educacio…OriginAS268276MEGA WIFI - EIRELIAS262595OnNet Telecomunic…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS28198SEMPRE TELECOMUNI…AS213151Christian ElsenAS8529Zain Omantel Inte…AS6939Hurricane Electri…AS20130Depaul University
  1. Sao Paulo263330268276262595266213This path
  2. Singapore263330268276262595132337This path
  3. Amsterdam26333026827626259528198213151This path
  4. London, UK263330268276262595281988529This path
  5. Oregon, US26333026827626259528198693920130This 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 March 2014
Allocation block
191.7.224.0/19
Status
assigned
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 191.7.224.0/19
PrefixAddressesOriginVisibility
191.7.192.0/198.2kAS263327ONLINE TELECOMUNICACOES LTDA80/80

History

  1. AS26333012th 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 191.7.224.0/19 in the calculator/19 reference

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