subnet.im

2607:f0c8::/32

Beanfield Technologies Inc.AS21949

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

ARINCA

Allocated 30th July 2007

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 2607:f0c8::/32 as seen from London, UK, read outward from the origin: AS21949 → AS9002 → AS51907. Each hop is listed with its network name beneath the graph.AS21949Beanfield Technol…OriginAS9002RETN LimitedAS51907Kanton Zug

Seen from London, UK

  1. 1AS21949Beanfield Technologies Inc.CAOrigin
    Peer of AS21949seen on 1,680 paths from 12 vantage points
  2. 2AS9002RETN LimitedGB
    Peer of AS9002seen on 325,294 paths from 2 vantage points
  3. 3AS51907Kanton 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. Amsterdam2194934549213151This path
  2. London, UK21949900251907Shown above
  3. Sao Paulo21949719532590This path
  4. Singapore219496939132337This 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
ARIN — North America
Country
Canada
Allocated
30th July 2007
Allocation block
2607:f0c8::/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 2607:f0c8::/32
ROA prefixAuthorised originMax length
2607:f0c8::/32AS21949/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. AS2194912th 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.