SUBNET.IM

200.202.98.0/23

Leste TelecomAS7063

At a glance

Addresses

512

/23 block

Visibility

8%

6 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 17th November 1999

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: 2 observed paths to 200.202.98.0/23, fanning out from AS7063 toward the vantage points that see it. Each path is written out in full beneath the graph.AS7063Leste TelecomOriginAS262664GIGALINE INTERNET…AS266213PLANETCLICK TELEC…AS137409GSL Networks Pty …AS8529Zain Omantel Inte…
  1. Sao Paulo7063262664266213This path
  2. London, UK70632626641374098529This 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

8%

Seen by 6 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
17th November 1999
Allocation block
200.202.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.

CoveringMore specific
Prefix hierarchy for 200.202.98.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.200.202.96.0/22AS7063200.202.96.0/21AS7063200.202.96.0/20AS7063200.202.98.0/23AS7063This prefix200.202.96.0/23AS7063200.202.98.0/24AS7063200.202.99.0/24AS7063

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 200.202.98.0/23
PrefixAddressesOriginVisibility
200.202.96.0/221kAS7063Leste Telecom79/80
200.202.96.0/212kAS7063Leste Telecom79/80
200.202.96.0/204.1kAS7063Leste Telecom79/80

More specific announcements

Announcements contained within 200.202.98.0/23
PrefixAddressesOriginVisibility
200.202.98.0/24256AS7063Leste Telecom6/80
200.202.99.0/24256AS7063Leste Telecom6/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 200.202.98.0/23
PrefixAddressesOriginVisibility
200.202.96.0/23512AS7063Leste Telecom6/80

History

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

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