subnet.im

2a13:3687::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCIQ

Allocated 22nd August 2022

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 2a13:3687::/32 as seen from Sao Paulo, read outward from the origin: AS205049 → AS42705 → AS208293 → AS210021 → AS3356 → AS32590. Each hop is listed with its network name beneath the graph.AS205049Techno Fast Compa…OriginAS42705Talia LimitedAS208293AlSalam State Com…AS210021DIL Technology Li…AS3356Lumen (Level 3)AS32590Valve Corporation

Seen from Sao Paulo

  1. Peer of AS205049seen on 266 paths from 142 vantage points
  2. Peer of AS42705seen on 1,770 paths from 142 vantage points
  3. Peer of AS208293seen on 6,009 paths from 142 vantage points
  4. Peer of AS210021seen on 3,259 paths from 125 vantage points
  5. Peer of AS3356seen on 232,620 paths from 2 vantage points
  6. 6AS32590Valve CorporationUSVantage 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. Singapore20504942705208293210021132337This path
  2. Amsterdam205049427052082932100216939213151This path
  3. Sao Paulo20504942705208293210021335632590Shown above
  4. London, UK2050494270520829321002133561557651907This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Iraq
Allocated
22nd August 2022
Allocation block
2a13:3680::/29
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 2a13:3687::/32
ROA prefixAuthorised originMax length
2a13:3687::/32AS19905/32
2a13:3687::/32AS205049/32
2a13:3680::/29AS19905/29
2a13:3680::/29AS205049/29

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 2a13:3687::/32
PrefixAddressesOriginVisibility
2a13:3686::/324.3B × /64AS205049Techno Fast Company Ltd.62/62

History

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