2001:678:53c::/48
At a glance
Subnets
/48 block
Visibility
62 of 62 vantage points
RPKI
Registry
CNAllocated 6th January 2026
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS154185seen on 62 paths from 62 vantage points
- Peer of AS215172seen on 62 paths from 62 vantage points
- Peer of AS151194seen on 62 paths from 62 vantage points
- Peer of AS198025seen on 62 paths from 62 vantage points
- Peer of AS204244seen on 62 paths from 62 vantage points
- Peer of AS204539seen on 62 paths from 62 vantage points
- Peer of AS214933seen on 62 paths from 62 vantage points
- Peer of AS207303seen on 62 paths from 62 vantage points
- Peer of AS153376seen on 62 paths from 62 vantage points
- Peer of AS214955seen on 62 paths from 62 vantage points
- Peer of AS205008seen on 62 paths from 62 vantage points
GBOne path, hop by hop, from the origin outward to the vantage point that saw it. The real path runs on past the last hop shown; only the hops nearest the origin are drawn. 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
- Amsterdam154185215172151194198025204244204539214933207303→ ⋯This path
- London, UK154185215172151194198025204244204539214933207303→ ⋯Shown above
- Sao Paulo154185215172151194198025204244204539214933207303→ ⋯This path
- Singapore154185215172151194198025204244204539214933207303→ ⋯This 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
100%
Seen by 62 of 62 full-feed vantage points
Globally propagatedObserved 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
- China
- Allocated
- 6th January 2026
- Allocation block
- 2001:678:53c::/48
- Status
- assigned
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2001:678:53c::/48 | AS154185 | /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
No prefix of the same length in the same parent block is announced.
History
- AS15418512th 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.