subnet.im

2602:f75a::/36

OsieAS401541

At a glance

Subnets

268,435,456 × /64

/36 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

ARIN

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 2602:f75a::/36 as seen from London, UK, read outward from the origin: AS401541 → AS38733 → AS45903 → AS9304 → AS15412 → AS6939 → AS51907. Each hop is listed with its network name beneath the graph.AS401541OsieOriginAS38733CMC Telecom Infra…AS45903CMC Telecom Infra…AS9304HGC Global Commun…AS15412Flag Telecom UK L…AS6939Hurricane Electri…AS51907Kanton Zug

Seen from London, UK

  1. 1AS401541OsieUSOrigin
    Peer of AS401541seen on 1,023 paths from 141 vantage points
  2. 2AS38733CMC Telecom Infrastructure CompanyVN
    Peer of AS38733seen on 6,600 paths from 142 vantage points
  3. 3AS45903CMC Telecom Infrastructure CompanyVN
    Peer of AS45903seen on 21,578 paths from 141 vantage points
  4. 4AS9304HGC Global Communications LimitedHK
    Peer of AS9304seen on 54,835 paths from 139 vantage points
  5. 5AS15412Flag Telecom UK LimitedGB
    Peer of AS15412seen on 224,570 paths from 97 vantage points
  6. 6AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 132,979 paths from 2 vantage points
  7. 7AS51907Kanton 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. Amsterdam40154138733459039304154126939213151This path
  2. London, UK4015413873345903930415412693951907Shown above
  3. Sao Paulo4015413873345903930415412693932590This path
  4. Singapore40154138733459039304154126939132337This 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
Unknown
Allocated
Unknown
Allocation block
2602:f75a::/36
Status
reserved
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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