subnet.im

45.174.91.0/24

At a glance

Addresses

256

/24 block

Visibility

61%

49 of 80 vantage points

RPKI

No ROA

Registry

LACNICMX

Allocated 10th April 2019

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: 3 observed paths to 45.174.91.0/24, fanning out from AS28434 toward the vantage points that see it. Each path is written out in full beneath the graph.AS28434CEDSAMOVIL SA DE …OriginAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS6939Hurricane Electri…AS20130Depaul UniversityAS6453TATA Communicatio…AS7473Singapore Telecom…AS8966Etisalat (E&)AS132337Axclusive
  1. London, UK2843433568529This path
  2. Oregon, US284343356693920130This path
  3. Singapore284343356645374738966132337This 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

61%

Seen by 49 of 80 full-feed vantage points

Partially propagated

Observed at 3 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
Mexico
Allocated
10th April 2019
Allocation block
45.174.88.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 45.174.91.0/24
PrefixAddressesOriginVisibility
45.174.90.0/24256AS28434CEDSAMOVIL SA DE CV48/80

History

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

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