subnet.im

2804:2380::/32

TURBO NET TELECOM LTDAAS264166

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 20th March 2015

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2804:2380::/32 as seen from London, UK, read outward from the origin: AS264166 → AS61745 → AS8167 → AS52320 → AS51907. Each hop is listed with its network name beneath the graph.AS264166TURBO NET TELECOM…OriginAS61745NBS TelecomAS8167V.talAS52320V.tal (GlobeNet)AS51907Kanton Zug

Seen from London, UK

  1. 1AS264166TURBO NET TELECOM LTDABROrigin
    Peer of AS264166seen on 437 paths from 133 vantage points
  2. 2AS61745NBS TelecomBR
    Peer of AS61745seen on 5,564 paths from 114 vantage points
  3. 3AS8167V.talBR
    Peer of AS8167seen on 174,578 paths from 142 vantage points
  4. 4AS52320V.tal (GlobeNet)CO
    Peer of AS52320seen on 6,595 paths from 2 vantage points
  5. 5AS51907Kanton ZugCHVantage 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 Paulo2641666174532590This path
  2. Singapore264166617456939132337This path
  3. Amsterdam26416661745816752320213151This path
  4. London, UK2641666174581675232051907Shown 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

97%

Seen by 60 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
20th March 2015
Allocation block
2804:2380::/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:2380::/32
ROA prefixAuthorised originMax length
2804:2380::/32AS264166/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

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

History

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