subnet.im

2407:b00::/32

HostcenterAS45382

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICKR

Allocated 29th May 2013

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 2407:b00::/32 as seen from London, UK, read outward from the origin: AS45382 → AS9286 → AS9957 → AS3491 → AS9002 → AS51907. Each hop is listed with its network name beneath the graph.AS45382HostcenterOriginAS9286KINXAS9957KINXAS3491PCCW Global (HK) …AS9002RETN LimitedAS51907Kanton Zug

Seen from London, UK

  1. 1AS45382HostcenterKROrigin
    Peer of AS45382seen on 622 paths from 142 vantage points
  2. 2AS9286KINXKR
    Peer of AS9286seen on 26,574 paths from 142 vantage points
  3. 3AS9957KINXKR
    Peer of AS9957seen on 10,873 paths from 100 vantage points
  4. 4AS3491PCCW Global (HK) Ltd.HK
    Peer of AS3491seen on 47,624 paths from 16 vantage points
  5. 5AS9002RETN LimitedGB
    Peer of AS9002seen on 325,294 paths from 2 vantage points
  6. 6AS51907Kanton 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. Amsterdam45382928699576939213151This path
  2. Singapore45382928699576939132337This path
  3. London, UK45382928699573491900251907Shown above
  4. Sao Paulo45382928699571741295632590This 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

100%

Seen by 62 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
APNIC — Asia-Pacific
Country
South Korea
Allocated
29th May 2013
Allocation block
2407:b00::/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 2407:b00::/32
ROA prefixAuthorised originMax length
2407:b00::/32AS45382/32

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. AS4538212th 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.