SUBNET.IM

2607:f208:df0b::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

18%

11 of 62 vantage points

RPKI

Invalid

Registry

ARINUS

Allocated 1st November 2007

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 1 observed path to 2607:f208:df0b::/48, fanning out from AS21499 toward the vantage points that see it. Each path is written out in full beneath the graph.AS21499Host Europe GmbHOriginAS20773Host Europe GmbHAS132337Axclusive
  1. Singapore2149920773132337This 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.

Route visibility

18%

Seen by 11 of 62 full-feed vantage points

Seen by few vantage points

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
United States
Allocated
1st November 2007
Allocation block
2607:f208::/32
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2607:f208:df0b::/48
ROA prefixAuthorised originMax length
2607:f208:df0b::/48AS20773/48
2607:f208::/32AS26496/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

Prefixes of the same length sharing a parent block with 2607:f208:df0b::/48
PrefixAddressesOriginVisibility
2607:f208:df0a::/4865.5k × /64AS398101GoDaddy.com, LLC5/62

History

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