subnet.im

168.197.139.0/24

Not announced at this prefix length

We do not see 168.197.139.0/24 announced as its own route. The most specific announcement covering it is 168.197.138.0/23, originated by AS52872 (VOANET Telecomunicações Ltda.). Traffic to addresses in this block follows that route.

At a glance

Addresses

256

/24 block

Visibility

Unknown

RPKI

Unknown

Registry

LACNICBR

Allocated 13th September 2016

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Registry and RPKI

RIR
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
13th September 2016
Allocation block
168.197.136.0/22
Status
allocated
Origin validation
Unknown

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 168.197.139.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.168.197.138.0/23AS52872168.197.136.0/22AS52872168.197.139.0/24This prefix168.197.138.0/24AS52872

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 168.197.139.0/24
PrefixAddressesOriginVisibility
168.197.138.0/23512AS52872VOANET Telecomunicações Ltda.77/77
168.197.136.0/221kAS52872VOANET Telecomunicações Ltda.77/77

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 168.197.139.0/24
PrefixAddressesOriginVisibility
168.197.138.0/24256AS52872VOANET Telecomunicações Ltda.77/77

History

  1. AS5287223rd October 2026 — 23rd October 2026
  2. AS5287222nd October 2026 — 22nd October 2026
  3. AS5287226th September 2026 — 6th October 2026
  4. AS5287225th September 2026 — 25th 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 168.197.139.0/24 in the calculator/24 reference

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