subnet.im

2804:70d4:8000::/34

RNET TELECOM LTDA ­ MEAS270751

At a glance

Subnets

1,073,741,824 × /64

/34 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 26th May 2020

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 2804:70d4:8000::/34 as seen from Singapore, read outward from the origin: AS270751 → AS269075 → AS53427 → AS132337. Each hop is listed with its network name beneath the graph.AS270751RNET TELECOM LTDA…OriginAS269075GO-NET FIBRAAS53427TGLOBAL NETWORKSAS132337Axclusive

Seen from Singapore

  1. 1AS270751RNET TELECOM LTDA ­ MEBROrigin
    Peer of AS270751seen on 464 paths from 141 vantage points
  2. 2AS269075GO-NET FIBRABR
    Peer of AS269075seen on 194 paths from 76 vantage points
  3. 3AS53427TGLOBAL NETWORKSUS
    Peer of AS53427seen on 154 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Sao Paulo27075126907532590This path
  2. Singapore27075126907553427132337Shown above
  3. Amsterdam27075126907526707927351752320213151This path
  4. London, UK2707512690752670792735175232051907This 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

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
26th May 2020
Allocation block
2804:70d4::/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:70d4:8000::/34
ROA prefixAuthorised originMax length
2804:70d4::/32AS270751/48

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:70d4:8000::/34
PrefixAddressesOriginVisibility
2804:70d4:c000::/341.1B × /64AS270751RNET TELECOM LTDA ­ ME61/62

History

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