subnet.im

2a11:29c0:37::/48

Itay KarielAS218447

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

61 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 17th September 2021

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 2a11:29c0:37::/48 as seen from Amsterdam, read outward from the origin: AS218447 → AS214128 → AS49915 → AS6461 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS218447Itay KarielOriginAS214128Ofek U. HaviaAS49915Megaport Global A…AS6461Zayo BandwidthAS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. 1AS218447Itay KarielEUOrigin
    Peer of AS218447seen on 62 paths from 62 vantage points
  2. 2AS214128Ofek U. HaviaIL
    Peer of AS214128seen on 61 paths from 61 vantage points
  3. 3AS49915Megaport Global AccessGB
    Peer of AS49915seen on 2,115 paths from 106 vantage points
  4. 4AS6461Zayo BandwidthUS
    Peer of AS6461seen on 132,858 paths from 5 vantage points
  5. 5AS25091IP-Max SACH
    Peer of AS25091seen on 664,395 paths from 2 vantage points
  6. 6AS8298IPng Networks GmbHCHVantage 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. London, UK21844721412849915646135280This path
  2. Amsterdam218447214128499156461250918298Shown above
  3. Sao Paulo218447214128499156461645335280This path
  4. Singapore2184472141284991564616939132337This 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 61 of 63 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
United Kingdom
Allocated
17th September 2021
Allocation block
2a11:29c0::/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 2a11:29c0:37::/48
ROA prefixAuthorised originMax length
2a11:29c0:37::/48AS218447/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 2a11:29c0:37::/48
PrefixAddressesOriginVisibility
2a11:29c0:36::/4865.5k × /64AS205705JDL Enterprises Limited62/63

History

  1. AS21844716th October 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.