SUBNET.IM

168.205.236.0/23

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 9th March 2016

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: 5 observed paths to 168.205.236.0/23, fanning out from AS265367 toward the vantage points that see it. Each path is written out in full beneath the graph.AS265367Paulo Cesar Cardo…OriginAS268689ELEVEL TECNOLOGIA…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS7195EdgeUnoAS213151Christian ElsenAS137409GSL Networks Pty …AS8529Zain Omantel Inte…AS6939Hurricane Electri…AS20130Depaul University
  1. Sao Paulo265367268689266213This path
  2. Singapore265367268689132337This path
  3. Amsterdam2653672686897195213151This path
  4. London, UK2653672686891374098529This path
  5. Oregon, US265367268689693920130This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally propagated

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
9th March 2016
Allocation block
168.205.236.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 168.205.236.0/23
PrefixAddressesOriginVisibility
168.205.238.0/23512AS265367Paulo Cesar Cardozo da Mata ME80/80

History

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

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