subnet.im

2a01:53c0:ffeb::/48

Meteverse LimitedAS54994

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCUS

Allocated 4th June 2012

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 2a01:53c0:ffeb::/48 as seen from London, UK, read outward from the origin: AS54994 → AS55410 → AS55836 → AS64049 → AS51907. Each hop is listed with its network name beneath the graph.AS54994Meteverse LimitedOriginAS55410Vodafone Idea LtdAS55836Reliance Jio Info…AS64049Reliance Jio Info…AS51907Kanton Zug

Seen from London, UK

  1. 1AS54994Meteverse LimitedCAOrigin
    Peer of AS54994seen on 98 paths from 47 vantage points
  2. 2AS55410Vodafone Idea LtdIN
    Peer of AS55410seen on 19,843 paths from 106 vantage points
  3. 3AS55836Reliance Jio Infocomm LimitedIN
    Peer of AS55836seen on 571,522 paths from 141 vantage points
  4. 4AS64049Reliance Jio Infocomm Pte. Ltd.SG
    Peer of AS64049seen on 9,431 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. Amsterdam54994554105583664049213151This path
  2. London, UK5499455410558366404951907Shown above
  3. Sao Paulo54994475564531295632590This path
  4. Singapore54994554105583664049132337This 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
United States
Allocated
4th June 2012
Allocation block
2a01:53c0::/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.

Covering announcements

No less specific announcement covers this prefix.

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. AS5499412th 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.