subnet.im

2803:f5e0::/32

RED DOT TECHNOLOGIES, C.A.AS270042

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

95%

62 of 65 vantage points

RPKI

Valid

Registry

LACNICVE

Allocated 29th June 2020

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 2803:f5e0::/32 as seen from London, UK, read outward from the origin: AS270042 → AS23379 → AS174 → AS1299 → AS35280. Each hop is listed with its network name beneath the graph.AS270042RED DOT TECHNOLOG…OriginAS23379Blackburn Technol…AS174Cogent Communicat…AS1299Arelion (fka. Tel…AS35280F5 Networks SARL

Seen from London, UK

  1. 1AS270042RED DOT TECHNOLOGIES, C.A.VEOrigin
    Peer of AS270042seen on 110 paths from 80 vantage points
  2. 2AS23379Blackburn Technologies II, LLCPR
    Peer of AS23379seen on 376 paths from 60 vantage points
  3. 3AS174Cogent Communications, LLCUS
    Peer of AS174seen on 712,661 paths from 87 vantage points
  4. 4AS1299Arelion (fka. Telia Carrier)SE
    Peer of AS1299seen on 513,698 paths from 6 vantage points
  5. 5AS35280F5 Networks SARLFRVantage 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. Amsterdam2700422337917432590This path
  2. Sao Paulo27004223379423035280This path
  3. Singapore270042233796939132337This path
  4. London, UK27004223379174129935280Shown 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

95%

Seen by 62 of 65 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
Venezuela
Allocated
29th June 2020
Allocation block
2803:f5e0::/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 2803:f5e0::/32
ROA prefixAuthorised originMax length
2803:f5e0::/32AS270042/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. AS27004212th 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.