subnet.im

2a03:220:f002::/48

Start2 LLCAS61400

At a glance

Subnets

65,536 × /64

/48 block

Visibility

46%

29 of 63 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 30th June 2014

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: 4 observed paths to 2a03:220:f002::/48, fanning out from AS61400 toward the vantage points that see it. Each path is written out in full beneath the graph.AS61400Start2 LLCOriginAS25091IP-Max SAAS8298IPng Networks GmbHAS6939Hurricane Electri…AS132337AxclusiveAS4637Telstra Internati…AS35280F5 Networks SARL
  1. Amsterdam61400250918298This path
  2. Singapore614006939132337This path
  3. London, UK614006939463735280This path
  4. Sao Paulo614006939463735280This 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

46%

Seen by 29 of 63 full-feed vantage points

Partially 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
Russia
Allocated
30th June 2014
Allocation block
2a03:220::/32
Status
allocated
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.

CoveringMore specific
Prefix hierarchy for 2a03:220:f002::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a03:220::/32AS614002a03:220:f002::/…AS61400This prefix

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 2a03:220:f002::/48
PrefixAddressesOriginVisibility
2a03:220::/324.3B × /64AS61400Start2 LLC63/63

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. AS6140012th October 2026 — present
  2. AS6140012th August 2026 — 21st September 2026
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.