SUBNET.IM

2804:73ec:8000::/34

ULTRANET PROVEDOR CUSTODIA LTDAAS270946

At a glance

Subnets

1,073,741,824 × /64

/34 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 15th July 2020

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Amsterdam.

OriginVantage point · Amsterdam
One AS path to 2804:73ec:8000::/34 as seen from Amsterdam, read outward from the origin: AS270946 → AS266623 → AS263276 → AS14840 → AS213151. Each hop is listed with its network name beneath the graph.AS270946ULTRANET PROVEDOR…OriginAS266623New FibraAS263276BBG TELECOM LTDAAS14840BR.DIGITALAS213151Christian Elsen

Seen from Amsterdam

  1. 1AS270946ULTRANET PROVEDOR CUSTODIA LTDABROrigin
    Peer of AS270946seen on 140 paths from 140 vantage points
  2. 2AS266623New FibraBR
    Peer of AS266623seen on 684 paths from 132 vantage points
  3. 3AS263276BBG TELECOM LTDABR
    Peer of AS263276seen on 3,917 paths from 141 vantage points
  4. 4AS14840BR.DIGITAL BR
    Peer of AS14840seen on 5,199 paths from 2 vantage points
  5. 5AS213151Christian ElsenDEVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. London, UK270946266623103151907This path
  2. Sao Paulo27094626662327125332590This path
  3. Singapore2709462666231031132337This path
  4. Amsterdam27094626662326327614840213151Shown above

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

98%

Seen by 61 of 62 full-feed vantage points

Globally propagated

Observed at 4 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
15th July 2020
Allocation block
2804:73ec::/32
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 2804:73ec:8000::/34
ROA prefixAuthorised originMax length
2804:73ec::/32AS270946/128

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 2804:73ec:8000::/34
PrefixAddressesOriginVisibility
2804:73ec:c000::/341.1B × /64AS270946ULTRANET PROVEDOR CUSTODIA LTDA61/62

History

  1. AS27094612th 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.

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