SUBNET.IM

187.16.148.0/22

At a glance

Addresses

1,024

/22 block

Visibility

23%

18 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 29th September 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
  1. Sao Paulo28255263009266213This path
  2. Singapore282556939132337This path
  3. Oregon, US28255693920130This path
  4. London, UK282552630091374098529This path
  5. Amsterdam2825569395829941051213151This 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

23%

Seen by 18 of 80 full-feed vantage points

Seen by few vantage points

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
29th September 2008
Allocation block
187.16.144.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.

CoveringMore specific
Prefix hierarchy for 187.16.148.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.187.16.144.0/21AS28255187.16.144.0/20AS28255187.16.148.0/22AS28255This prefix187.16.144.0/22AS28255187.16.149.0/24AS28255

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 187.16.148.0/22
PrefixAddressesOriginVisibility
187.16.144.0/212kAS28255Wtl Telecomunicacoes do Brasil Ltda18/80
187.16.144.0/204.1kAS28255Wtl Telecomunicacoes do Brasil Ltda80/80

More specific announcements

Announcements contained within 187.16.148.0/22
PrefixAddressesOriginVisibility
187.16.149.0/24256AS28255Wtl Telecomunicacoes do Brasil Ltda79/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 187.16.148.0/22
PrefixAddressesOriginVisibility
187.16.144.0/221kAS28255Wtl Telecomunicacoes do Brasil Ltda18/80

History

  1. AS2825512th 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 187.16.148.0/22 in the calculator/22 reference

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