subnet.im

200.25.92.0/23

Not announced at this prefix length

We do not see 200.25.92.0/23 announced as its own route. The most specific announcement covering it is 200.25.92.0/22, originated by AS7195 (EdgeUno). Traffic to addresses in this block follows that route.

At a glance

Addresses

512

/23 block

Visibility

Unknown

RPKI

Unknown

Registry

LACNICCO

Allocated 31st March 1995

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
Colombia
Allocated
31st March 1995
Allocation block
200.25.0.0/17
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 200.25.92.0/23
ROA prefixAuthorised originMax length
200.25.0.0/17AS7195/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 200.25.92.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.25.92.0/22AS7195200.25.92.0/23This prefix200.25.92.0/24AS7195200.25.93.0/24AS7195

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.25.92.0/23
PrefixAddressesOriginVisibility
200.25.92.0/221kAS7195EdgeUno76/76

More specific announcements

Announcements contained within 200.25.92.0/23
PrefixAddressesOriginVisibility
200.25.92.0/24256AS7195EdgeUno1/76
200.25.93.0/24256AS7195EdgeUno1/76

Sibling prefixes

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

History

  1. AS719523rd October 2026 — 24th October 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 200.25.92.0/23 in the calculator/23 reference

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