subnet.im

2803:e50:520::/48

Not announced at this prefix length

We do not see 2803:e50:520::/48 announced as its own route. The most specific announcement covering it is 2803:e50::/32, originated by AS273217 (ACOLME TECH, SRL). Traffic to addresses in this block follows that route.

At a glance

Subnets

65,536 × /64

/48 block

Visibility

Unknown

RPKI

Unknown

Registry

LACNICDO

Allocated 12th April 2024

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
Dominican Republic
Allocated
12th April 2024
Allocation block
2803:e50::/32
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 2803:e50:520::/48
ROA prefixAuthorised originMax length
2803:e50::/32AS273217/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2803:e50:520::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2803:e50::/32AS2732172803:e50:520::/48This 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 2803:e50:520::/48
PrefixAddressesOriginVisibility
2803:e50::/324.3B × /64AS273217ACOLME TECH, SRL62/63

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. AS2732172nd November 2026 — 6th November 2026
  2. AS27321712th August 2026 — 1st November 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.

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