SUBNET.IM

200.0.44.0/23

BR.Digital TelecomAS61889

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 26th May 2014

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 200.0.44.0/23, fanning out from AS61889 toward the vantage points that see it. Each path is written out in full beneath the graph.AS61889BR.Digital TelecomOriginAS14840BR.DIGITALAS132337AxclusiveAS8167V.talAS52320V.tal (GlobeNet)AS213151Christian ElsenAS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. Singapore6188914840132337This path
  2. Amsterdam6188914840816752320213151This path
  3. London, UK61889148408167523208529This path
  4. Sao Paulo6188914840816752320266213This path
  5. Oregon, US6188914840816752320693920130This 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

99%

Seen by 79 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
26th May 2014
Allocation block
200.0.32.0/20
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 200.0.44.0/23
ROA prefixAuthorised originMax length
200.0.32.0/20AS61889/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 200.0.44.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.0.32.0/20AS61889200.0.44.0/23AS61889This prefix

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.0.44.0/23
PrefixAddressesOriginVisibility
200.0.32.0/204.1kAS61889BR.Digital Telecom79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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

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