subnet.im

2804:269c:feee::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

44%

27 of 62 vantage points

RPKI

Invalid

Registry

LACNICBR

Allocated 7th July 2015

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:269c:feee::/48 as seen from Singapore, read outward from the origin: AS61574 → AS47065 → AS20473 → AS2914 → AS4229 → AS132337. Each hop is listed with its network name beneath the graph.AS61574UNIVERSIDADE FEDE…OriginAS47065USC / UFMG PEERIN…AS20473The Constant Comp…AS2914NTT America, Inc.AS4229Zenlayer IncAS132337Axclusive

Seen from Singapore

  1. Peer of AS61574seen on 5,773 paths from 62 vantage points
  2. Peer of AS47065seen on 13,612 paths from 142 vantage points
  3. Peer of AS20473seen on 66,971 paths from 140 vantage points
  4. Peer of AS2914seen on 3,459 paths from 2 vantage points
  5. Peer of AS4229seen on 13,937 paths from 2 vantage points
  6. 6AS132337AxclusiveSGVantage 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. Amsterdam615744706520473291434549213151This path
  2. Singapore61574470652047329144229132337Shown above
  3. London, UK61574470652047329146830419133428851907This 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

44%

Seen by 27 of 62 full-feed vantage points

Partially propagated

Observed at 3 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
7th July 2015
Allocation block
2804:269c::/32
Status
assigned
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2804:269c:feee::/48
ROA prefixAuthorised originMax length
2804:269c:feee::/48AS61575/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:269c:feee::/48
PrefixAddressesOriginVisibility
2804:269c:feef::/4865.5k × /64AS61574UNIVERSIDADE FEDERAL DE MINAS GERAIS29/62

History

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