SUBNET.IM

2a00:1728:20::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCBG

Allocated 26th November 2009

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 2a00:1728:20::/48, fanning out from AS31490 toward the vantage points that see it. Each path is written out in full beneath the graph.AS31490NetIX Communicati…OriginAS34224Neterra Ltd.AS6939Hurricane Electri…AS213151Christian ElsenAS3356Lumen (Level 3)AS32590Valve CorporationAS132337AxclusiveAS8220COLTAS15576NTS workspace AGAS51907Kanton Zug
  1. Amsterdam31490342246939213151This path
  2. Sao Paulo3149034224335632590This path
  3. Singapore31490342246939132337This path
  4. London, UK314903422482201557651907This 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

97%

Seen by 60 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
Bulgaria
Allocated
26th November 2009
Allocation block
2a00:1728::/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 2a00:1728:20::/48
ROA prefixAuthorised originMax length
2a00:1728:20::/48AS31490/48
2a00:1728::/32AS34224/48

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2a00:1728:20::/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.2a00:1728::/32AS342242a00:1728:20::/48AS31490This prefix2a00:1728:20:100…AS31490

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 2a00:1728:20::/48
PrefixAddressesOriginVisibility
2a00:1728::/324.3B × /64AS34224Neterra Ltd.61/62

More specific announcements

Announcements contained within 2a00:1728:20::/48
PrefixAddressesOriginVisibility
2a00:1728:20:100::/56256 × /64AS31490NetIX Communications JSC3/62

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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