SUBNET.IM

177.136.38.0/23

TASCOM TELECOMUNICAÇÕES LTDAAS52871

At a glance

Addresses

512

/23 block

Visibility

4%

3 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 31st January 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 177.136.38.0/23, fanning out from AS52871 toward the vantage points that see it. Each path is written out in full beneath the graph.AS52871TASCOM TELECOMUNI…OriginAS262355VSX NetworksAS266213PLANETCLICK TELEC…
  1. Sao Paulo52871262355266213This 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

4%

Seen by 3 of 80 full-feed vantage points

Seen by few vantage points

Observed at 2 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
31st January 2012
Allocation block
177.136.32.0/21
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 177.136.38.0/23
ROA prefixAuthorised originMax length
177.136.32.0/21AS52871/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 177.136.38.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.177.136.36.0/22AS52871177.136.32.0/21AS52871177.136.38.0/23AS52871This prefix177.136.36.0/23AS52871177.136.38.0/24AS52871177.136.39.0/24AS52871

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 177.136.38.0/23
PrefixAddressesOriginVisibility
177.136.36.0/221kAS52871TASCOM TELECOMUNICAÇÕES LTDA3/80
177.136.32.0/212kAS52871TASCOM TELECOMUNICAÇÕES LTDA80/80

More specific announcements

Announcements contained within 177.136.38.0/23
PrefixAddressesOriginVisibility
177.136.38.0/24256AS52871TASCOM TELECOMUNICAÇÕES LTDA3/80
177.136.39.0/24256AS52871TASCOM TELECOMUNICAÇÕES LTDA9/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 177.136.38.0/23
PrefixAddressesOriginVisibility
177.136.36.0/23512AS52871TASCOM TELECOMUNICAÇÕES LTDA3/80

History

  1. AS5287112th 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 177.136.38.0/23 in the calculator/23 reference

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