subnet.im

187.61.105.0/24

CINTE TELECOM COMERCIO E SERVICOS LTDAAS53153

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 78 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 21st November 2012

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: 1 observed path to 187.61.105.0/24, fanning out from AS53153 toward the vantage points that see it. Each path is written out in full beneath the graph.AS53153CINTE TELECOM COM…OriginAS262494Virtex TelecomAS264409Huge NetworksAS13786Seaborn (Seabras …AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Oregon, US53153262494264409137866762168042013This 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.

Route visibility

1%

Seen by 1 of 78 full-feed vantage points

Seen by few vantage points

Observed at 1 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
21st November 2012
Allocation block
187.61.96.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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS5315329th October 2026 — present
  2. AS5315312th August 2026 — 21st September 2026
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.61.105.0/24 in the calculator/24 reference

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