SUBNET.IM

191.97.111.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICAR

Allocated 6th February 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.

  1. London, UK266217303229271295612998529This path
  2. Sao Paulo26621730322927129563356266213This path
  3. Singapore26621730322927129566939132337This path
  4. Oregon, US2662173032292712956693920130This path
  5. Amsterdam2662173032292712956291434549213151This 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
Argentina
Allocated
6th February 2014
Allocation block
191.97.108.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.

CoveringMore specific
Prefix hierarchy for 191.97.111.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.191.97.108.0/22AS26621191.97.111.0/24AS26621This prefix191.97.110.0/24AS26621

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 191.97.111.0/24
PrefixAddressesOriginVisibility
191.97.108.0/221kAS26621FEROGLIO JULIA ELENA79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 191.97.111.0/24
PrefixAddressesOriginVisibility
191.97.110.0/24256AS26621FEROGLIO JULIA ELENA79/80

History

  1. AS2662112th 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.97.111.0/24 in the calculator/24 reference

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