subnet.im

2804:24ac::/33

GLOBALMT TELECOMAS264237

At a glance

Subnets

2,147,483,648 × /64

/33 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 6th May 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:24ac::/33 as seen from London, UK, read outward from the origin: AS264237 → AS264255 → AS4230 → AS9002 → AS51907. Each hop is listed with its network name beneath the graph.AS264237GLOBALMT TELECOMOriginAS264255INTERFIBRAS TELEC…AS4230Claro (Embratel)AS9002RETN LimitedAS51907Kanton Zug

Seen from London, UK

  1. 1AS264237GLOBALMT TELECOMBROrigin
    Peer of AS264237seen on 140 paths from 140 vantage points
  2. 2AS264255INTERFIBRAS TELECOMUNICACOES LTDABR
    Peer of AS264255seen on 157 paths from 109 vantage points
  3. 3AS4230Claro (Embratel)BR
    Peer of AS4230seen on 16,086 paths from 13 vantage points
  4. 4AS9002RETN LimitedGB
    Peer of AS9002seen on 325,294 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 Paulo26423726425532590This path
  2. Amsterdam264237264255423034549213151This path
  3. London, UK2642372642554230900251907Shown above
  4. Singapore26423726425542306939132337This 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
6th May 2015
Allocation block
2804:24ac::/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:24ac::/33
ROA prefixAuthorised originMax length
2804:24ac::/33AS264237/33
2804:24ac::/32AS264237/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2804:24ac::/33: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2804:24ac::/32AS2642372804:24ac::/33AS264237This prefix2804:24ac:8000::…AS264237

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 2804:24ac::/33
PrefixAddressesOriginVisibility
2804:24ac::/324.3B × /64AS264237GLOBALMT TELECOM62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2804:24ac::/33
PrefixAddressesOriginVisibility
2804:24ac:8000::/332.1B × /64AS264237GLOBALMT TELECOM61/62

History

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