subnet.im

2a0c:b641:bd5::/48

Xero Networks LTDAS215527

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCBE

Allocated 15th May 2018

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2a0c:b641:bd5::/48 as seen from London, UK, read outward from the origin: AS215527 → AS20473 → AS8220 → AS15576 → AS51907. Each hop is listed with its network name beneath the graph.AS215527Xero Networks LTDOriginAS20473The Constant Comp…AS8220COLTAS15576NTS workspace AGAS51907Kanton Zug

Seen from London, UK

  1. 1AS215527Xero Networks LTDGBOrigin
    Peer of AS215527seen on 230 paths from 62 vantage points
  2. 2AS20473The Constant Company, LLCUS
    Peer of AS20473seen on 1,719 paths from 5 vantage points
  3. 3AS8220COLTGB
    Peer of AS8220seen on 93,898 paths from 4 vantage points
  4. 4AS15576NTS workspace AGCH
    Peer of AS15576seen on 442,038 paths from 2 vantage points
  5. 5AS51907Kanton ZugCHVantage 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. Amsterdam21552720473325734549213151This path
  2. London, UK2155272047382201557651907Shown above
  3. Sao Paulo2155272047329141295632590This path
  4. Singapore2155272047329146939132337This 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

98%

Seen by 61 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
Belgium
Allocated
15th May 2018
Allocation block
2a0c:b640::/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 2a0c:b641:bd5::/48
ROA prefixAuthorised originMax length
2a0c:b641:bd0::/44AS215527/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 2a0c:b641:bd5::/48
PrefixAddressesOriginVisibility
2a0c:b641:bd4::/4865.5k × /64AS215527Xero Networks LTD62/62

History

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